Did something happen to the chart rendering calculation between 8.0.26.1 and 8.1.1.7

[WHICKED]

and perhaps Quant key or the other vendors can chime in with their setup as well.. since they are a vendor.

[WHICKED]

Hello WHICKED,

Thank you for your reply.

At the moment, my focus is to get a reproducible scenario on my end. Since you are the original poster, I would like to get that information from you if possible. Then I will take into consideration what everyone else is reporting as well to try and narrow down the potential cause. I have tested (on version 8.1.1.7) both of the indicators you linked, and I am unable to get a flicker on the new panel that is created. I tested on the ES 09-23 on a 150-tick chart with 3 days to load. Please provide the exact steps to recreate this behavior:

• What instrument symbol (and expiry, if applicable) do you have selected?
• What interval are you using?
• How many days/bars to load do you have on the chart?
• Are you simply adding these indicators to the chart with the default settings, or do you modify any of the settings? If you modify the settings, what are you changing them to?

It would also be helpful if you are able to get a video that shows what happens when you follow these steps. That way I can actually see the behavior that I am looking for when following the steps to reproduce.

I look forward to your reply.

NQ
Range 1, 2, 3, pretty much any NON time based bars (Unirenko, etc)
3 days
Default settings

[NinjaTrader_Emily]

Hello WHICKED,

Thank you for your reply.

At the moment, my focus is to get a reproducible scenario on my end. Since you are the original poster, I would like to get that information from you if possible. Then I will take into consideration what everyone else is reporting as well to try and narrow down the potential cause. I have tested (on version 8.1.1.7) both of the indicators you linked, and I am unable to get a flicker on the new panel that is created. I tested on the ES 09-23 on a 150-tick chart with 3 days to load. Please provide the exact steps to recreate this behavior:

• What instrument symbol (and expiry, if applicable) do you have selected?
• What interval are you using?
• How many days/bars to load do you have on the chart?
• Are you simply adding these indicators to the chart with the default settings, or do you modify any of the settings? If you modify the settings, what are you changing them to?

It would also be helpful if you are able to get a video that shows what happens when you follow these steps. That way I can actually see the behavior that I am looking for when following the steps to reproduce.

I look forward to your reply.

[WHICKED]

Hello WHICKED,

Thank you for this description.

Have you only experienced this behavior when working with a draw object in the future? If possible, please provide a sample script that I may test on my end along with the exact steps to reproduce this behavior. I would be glad to test it on multiple versions. I am also curious; are you seeing exceptions thrown like EB Worx has mentioned? Do you only observe this behavior when volatility picks up, or are you able to consistently reproduce it?

I look forward to your reply.

I have experienced this issue regardless of future drawing or sliding a draw object.

As others have mentioned - I have seen the exceptions being thrown from time to time when using Instrument or TickSize. As well, others have mentioned that its when volatility picks up - that is not the case for me - it could be slow and the issues still arise.

It exacerbates if you use something such as TickRefresh on the charts as well.

As mentioned - if you use the https://ninjatraderecosystem.com/use...ulative-delta/

or using https://ninjatraderecosystem.com/use...ntum-for-nt-8/

On none time based charts - there is a scaling flicker.

I am not sure what your other two vendors are using to reproduce their issues - but they are having the same flicker issue. You MIGHT want to ask them as well.

[NinjaTrader_Emily]

If you create a indicator that updates or slides in the future a draw object and attach a indicator such as Cummulative delta or even CumDelta (https://ninjatraderecosystem.com/use...ulative-delta/) from your Ninjatrader Ecosystem website - what appears to happen is that the new panel that the indicator is displaying on (below the price chart) will 'flicker' but will resize the y axis and then will 'update' after the fact causing what looks like a flicker but it is just the chart having an issue with chartscale.

Hello WHICKED,

Thank you for this description.

Have you only experienced this behavior when working with a draw object in the future? If possible, please provide a sample script that I may test on my end along with the exact steps to reproduce this behavior. I would be glad to test it on multiple versions. I am also curious; are you seeing exceptions thrown like EB Worx has mentioned? Do you only observe this behavior when volatility picks up, or are you able to consistently reproduce it?

I look forward to your reply.

[WHICKED]

and..... ninjatrader

**crickets**

[WHICKED]

As well - i try catched all the methods calling Instrument or TickSize and it still does the scaling issue. So that did not resolve the issues

[WHICKED]

What do you mean using the cached version? You mean calling them and then storing that information in a variable?

And if they did cause this by some threading issue or a race condition --- that would not be shocking. They still have not updated their system to take full advantage of the amount of cores that CPUs now have and yet STILL have threading issues?

Personally - NinjaTrader 7 was THE BEST of NinjaTrader - stable and performant. Now.... its a mess

[QuantKey_Bruce]

The strange thing is that it's not producing errors all the time, it seems to only happen when volatility picks up and NinjaTrader gets a lot more to do?

That makes it sound like maybe a race condition or something they're done incorrectly with the threading.

[EB Worx]

Interesting. I don't see that in my case any of those are being used in OnRender. I do see a reference to TickSize in OnCalculateMinMax. I will try caching that - perhaps it is failing there in a way it did not fail before. But, I don't see any exceptions in the log, so I'm unsure and will just have to try it.

The strange thing is that it's not producing errors all the time, it seems to only happen when volatility picks up and NinjaTrader gets a lot more to do?

[QuantKey_Bruce]

I've seen the same, some of our indicators started showing flashing behavior with the latest 8.1.1.x versions
After debugging it it seems that with these new versions NinjaTrader sometimes throws an exception if you use TickSize or Instrument from within OnRender()
The solution for us was to cache these properties and use the cached versions

Interesting. I don't see that in my case any of those are being used in OnRender. I do see a reference to TickSize in OnCalculateMinMax. I will try caching that - perhaps it is failing there in a way it did not fail before. But, I don't see any exceptions in the log, so I'm unsure and will just have to try it.

It's worth noting that when the flashing behavior occurs in our case, it isn't during some early phase of OnStateChange - it's while it's been running in realtime for a while, so it's not the common case of "you can't use Instrument in State.Configure" or that sort of thing - it's something new that did not used to be broken.

[EB Worx]

I've seen the same, some of our indicators started showing flashing behavior with the latest 8.1.1.x versions
After debugging it it seems that with these new versions NinjaTrader sometimes throws an exception if you use TickSize or Instrument from within OnRender()
The solution for us was to cache these properties and use the cached versions

[WHICKED]

@NinjaTrader

So that is a vendor and myself that are able to replicate the behavior.... SOOOOOOO

What did you change?

[QuantKey_Bruce]

I am seeing some behavior involving a scale that compresses then snaps back a fraction of a second later, but this results in a perceived flicker. Unexplained so far.

[WHICKED]

When this happens, is this in the form of the scale becoming compressed and then returning to normal? And is it in a subgraph or on the price panel? In other words, do your plots DISAPPEAR than blink back, or is it that the scale becomes compressed and then returns?

I have seen both behaviors. Disappear and or compress and return. Subgraph