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

[llanqui]

for me it is like a one second or less hickup, the chart distorts then comes back to normal

in the new version

in the past this happened when I had a lot of swing plots on the chart, but otherwise the panel was stable

[QuantKey_Bruce]

Yes, I agree, they changed something in a bad way here.

[WHICKED]

Yes it is an oscillator that I wrote, not a part of NT's inbuilt indicator set.

Which confirms. The code between 8.0.27 and their updated versions of 8.0.28 and 8.1.1 BROKE something.

so…. Here we wait. Until SOMEONE at NT takes a look.

[QuantKey_Bruce]

Yes it is an oscillator that I wrote, not a part of NT's inbuilt indicator set.

[WHICKED]

I was seeing this issue with an indicator running in a subgraph - a type of oscillator. It started at some point in some recent version, but I am not certain exactly when it started. The way it manifests is that sometimes, the scale becomes distorted/compressed then flashes back to the correct scale a split second later, resulting in the perception of "flicker" on the part of the end users. It doesn't happen during OnStateChange (as far as I can tell) but randomly during a realtime run. I checked the code for any references to Bars or Instrument etc. in OnRender and did not find anything, but there is a reference to TickSize in OnCalculateMinMax. I've replace that with a cached double tickSize that's a field variable in case TickSize is becoming inaccessible but it's too soon to know if that fixed it because the error is intermittent.

An oscillator? We are trying to figure this problem out and you can’t say which? Or is it some proprietary thing? If that’s the case then you could always go through vendor support. Seems you might have more luck than I will.

[WHICKED]

Hello All,

Thank you for your patience.

Pitro and koop1975 - as QuantKey_Bruce mentioned, the value displayed on your charts seems to be Double.MinValue. This is described on the following publicly available page from the Microsoft C# documentation:
https://learn.microsoft.com/en-us/do...tframework-4.8
His suggestion to recognize that value and show N/A or Unavailable is helpful.

WHICKED I have tested the two indicators that you mentioned from the ecosystem on a 4 Range chart for NQ 09-23. I created the following video:

https://www.screencast.com/t/cUleuv7Gmu

Is the flashing behavior present in this video? If so, I am not sure that I am seeing what you are referring to so please let me know. Otherwise, I still have not been able to produce this behavior. Is there something I should do differently than in the video? Do I need to wait longer or test at a different time of day? My understanding is that this only occurs when first loading the indicator on a chart; is that correct, or can the flashing happen after an indicator has been added and just occur intermittently throughout the day?

I sincerely appreciate your patience and look forward to your reply.

No, the problem is not present in your video clip. But like all of us even your vendors have said it is intermittent and I have pointed out multiple times that the issue was after the update of 8.0.28 any version after that experiences this issue including your latest 8.1.1.7. If you go to 8.0.27. The issue is not there

Do you get it yet? The only thing that changed was not the code on my side, or your vendors side, but the version number on your side.

So code did not change on our side. But your version number changed. And that points directly to an update that you did on the Ninjatrader platform.

As your vendors have also pointed out the old version did not do this. It is the new version that is doing this, so why is there a hesitation from your end to have a developer look at the problem between those versions and figure it out?

File a "bug report," "incident report," or simply an "issue." Assign it to a developer. Or to the triage team, compare the two code versions.

TA DA!

[NinjaTrader_Emily]

Hello All,

Thank you for your patience.

Pitro and koop1975 - as QuantKey_Bruce mentioned, the value displayed on your charts seems to be Double.MinValue. This is described on the following publicly available page from the Microsoft C# documentation:

https://learn.microsoft.com/en-us/dotnet/api/system.double.minvalue?view=netframework-4.8

His suggestion to recognize that value and show N/A or Unavailable is helpful.

WHICKED I have tested the two indicators that you mentioned from the ecosystem on a 4 Range chart for NQ 09-23. I created the following video:

https://www.screencast.com/t/cUleuv7Gmu

Is the flashing behavior present in this video? If so, I am not sure that I am seeing what you are referring to so please let me know. Otherwise, I still have not been able to produce this behavior. Is there something I should do differently than in the video? Do I need to wait longer or test at a different time of day? My understanding is that this only occurs when first loading the indicator on a chart; is that correct, or can the flashing happen after an indicator has been added and just occur intermittently throughout the day?

I sincerely appreciate your patience and look forward to your reply.

[QuantKey_Bruce]

Would you chime in here and tell NinjaTrader your environment that you are reproducing this issue with?

I was seeing this issue with an indicator running in a subgraph - a type of oscillator. It started at some point in some recent version, but I am not certain exactly when it started. The way it manifests is that sometimes, the scale becomes distorted/compressed then flashes back to the correct scale a split second later, resulting in the perception of "flicker" on the part of the end users. It doesn't happen during OnStateChange (as far as I can tell) but randomly during a realtime run. I checked the code for any references to Bars or Instrument etc. in OnRender and did not find anything, but there is a reference to TickSize in OnCalculateMinMax. I've replace that with a cached double tickSize that's a field variable in case TickSize is becoming inaccessible but it's too soon to know if that fixed it because the error is intermittent.

[WHICKED]

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.

Would you chime in here and tell NinjaTrader your environment that you are reproducing this issue with?

[QuantKey_Bruce]

That large negative number you're seeing displayed is double.MinValue - an indication that ask and bid are not available. Whatever is displaying that needs to be updated to recognize double.MinValue and show N/A or -- or "Unavailable" etc.

[atindriyadas]

Hi there, im having the same error as WHICKED and koop, can you fixed pls?

[Pitro]

Same thing here, with indicators loaded or with blank chart

[koop1975]

I forgot to mention the decimal issue that Pitro just brought up. What would cause the bid/ask data to have this negative repeating decimal in the new version of ninja that was not there before. Maybe this is related to the flashing issue.

[Pitro]

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.

Same Issue here too

ANY instrument, when there is speed its more apparent but appears also when its slow (NQ, ES, RTY, YM)
ANY non time based bare
It doesnt matter how many days I pick
Stock settings and modified

I have been on the emails with NT tech support for days now showing the negative decimals along with the chart flickering but it bears no fruit.

I hope this gets the attention it requires.

[koop1975]

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.

I'm having the same exact issue as well.

ANY instrument when there is speed. (NQ, ES, RTY, YM)
ANY non time-based charts.
I've tried 1 day, 2 days, 3 days, 5 days, etc.
Default settings, and every other setting.

It seems to be easily reproducible and I personally know that several others have emailed NT support regarding the issue, and even provided video of it happening. Clearly SOMEONE at NT has to know what changed!