Custom Indicator isn't working on some financial instruments

[jamestrader21x]

I have a custom indicator that uses 2 public domain indicators. For some strange reason, it won't work on CL, 6E, AND 6B. It WILL work on ES, NQ, YM, and RTY. I thought it could be Average True Range because I have a volatility parameter coded in to the indicator. I tried redoing it, but with a "0.00" minimum allowance. When that didn't work, I tried removing all of the ATR code. Still not working properly. I really don't get it. If possible, someone please help me out. If possible, I'd rather NOT post the code publicly.

[NinjaTrader_Jesse]

Hello jamestrader21x,

Thanks for the post.

The given details really don't provide enough details to provide any type of answer but I can give some suggestions so that you can debug the situation further.

If the indicator does not work on certain instruments the first step is to check the output window and log to make sure its not just an error. If there are not any errors you will likely need to use some Prints to further address the question.

Prints can be added into OnBarUpdate to output what the script does when it processes. A Print in OnBarUpdate will show the script is working in general which would be step 1:

protected override void OnBarUpdate()
{
   Print(CurrentBar);

That would just let you know the script ran and will tell you that you need to check your later logic. If you don't see a print that would be the issue and that would need to be addressed. You could start by checking the data it uses or try reducing the added series/logic until it starts working.

Once you have this type of simple test information to know what state the script is in and where it starts to break down that would be beneficial information to provide on the forum. Without code anything we provide is just going to be a guess so if you can provide more specifics like "I added an extra series and it now doesn't work on X instrument, OnBarUpdate is not called using this print: " that would be much more informative and we can likely provide more options for troubleshooting.


I look forward to being of further assistance.