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

[llanqui]

it is possible it is related to the number of draw objects on the chart, the type and where they are on the time/price ... possibly off visible chart panel draw objects still consume resources?

[Leeroy_Jenkins]

Pretty rare bug. I see it maybe once a month.

[Leeroy_Jenkins]

I also use one NQ range chart, and for me, it occurs right at RTH open. I don't have a very powerful PC (Intel graphics), so I don't think this issue is related to the GPU. Before 8.0.28 I have been using 8.0.26.1 since its release and haven't experienced any problems whatsoever.

[llanqui]

When I monitor the GPU with Task Manager, it never gets anywhere near a max out...so maybe it is not a GPU overload (in my case with a business class computer)

still happens occasionally on a 2 range NQ chart

seems to happen primarily during trades (orders, executions)

with the Ninja ATM it is worse

[Leeroy_Jenkins]

8.0.28 can confirm blinking.

[llanqui]

ok, thanks, yes good suggestion....before I was on a gaming laptop and didn't have this problem....now I have a Dell business desktop...it has a gpu but probably not a very good one

[QuantKey_Bruce]

It seems to me that NT8 with WPF is much less stable on the graphics than NT7, and slower (in the graphics). Probably heavier on the graphics processor.

Regarding this statement specifically, NT7 relied solely on the CPU and rendered in software while NT8 offloads rendering tasks to the GPU via DirectX. Ergo, if you have a slow or no graphics card such as an inbuilt Intel graphics chip in a laptop, NT8 doesn't have anything to offload the tasks to and most of it falls back on the CPU, while if you have a great graphics card with high speed 2D performance, almost all of it gets offloaded to the GPU. So, you'll see much more difference in performance between NT7 and NT8 (with NT8 being tremendously faster) if you have a good graphics card.

[llanqui]

I develop just for myself, and have the same problem on a NQ 2 Range or Renko chart, loaded just one day back.

(does not happen on ES/CL/UB/HG 2 Range or Renko, just NQ)

I have several indicators that draw various objects on the chart, arrows, dots, horizontal lines, vertical lines....some persistent and others only one at a time (i.e. same label)

I don't do any custom Rendering, just use Ninja Standard Draw methods

The problem seems worse when I have an active position. The chart can jump around and is not stable.

This only happens on the 2 Range or Renko charts. If I have a 10+ Range, with many more drawn objects, it does not do this. (but I don't trade on that chart). It doesn't do it on any other chart except the 2 Range/Renko NQ. Only the NQ.

I've stopped using Ninja's ATM as it is not good for scalping NQ in fast markets.

Wrote my own using virtual stops/break even/trail.

This is new so at least that should help a little.

It seems the problem may be related to the speed of the price action, perhaps something underlying having to do with messy sub bar price movements that Ninja has a hard time keeping up with.

and then perhaps the number of drawn objects

It seems to me that NT8 with WPF is much less stable on the graphics than NT7, and slower (in the graphics). Probably heavier on the graphics processor.

It could also be related to the type of draw object. And perhaps how far off the current chart panel it is.

If Ninja would look at these parameters, then probably they can find it.

[NinjaTrader_Emily]

Hello Emily,
until previous versions everything worked perfectly; since NT did the last update things have started not worked properly just exactly like WHICKED wrote. By the way, the developer didn't changed or modified anything so the problem is from NT side.

Best regards

Alex

Hello Alex,

Thank you for your reply.

If you are able to reproduce this on a script that comes with NinjaTrader by default, I would be glad to research the steps to reproduce the behavior and identify the cause. Since this is happening with a 3rd party script, you will have to reach out to the developer and they may need to debug their script to identify which part of the code is causing the unexpected behavior. I understand that this may have been working prior to the last update, though there is likely something happening programmatically within the script that could be causing this behavior. This needs to be addressed through the developer directly.

Thank you for your patience.

[Alex Al23]

Hello Emily,
until previous versions everything worked perfectly; since NT did the last update things have started not working properly just exactly like WHICKED wrote. By the way, the developer didn't changed or modified anything so the problem is from NT side.

Best regards

Alex

[NinjaTrader_Emily]

Hello Emily,
thanks for your fast reply; this is happening on a 3rd party and it's affecting the whole chart and indicators.

Hello Alex Al23,

Thank you for that info.

Since this is happening on a 3rd party script and not one that you wrote, please reach out to the developer directly for assistance with any unexpected behavior from the script.

Thank you for using NinjaTrader.

[Alex Al23]

Hello Emily,
thanks for your fast reply; this is happening on a 3rd party and it's affecting the whole chart and indicators.

[NinjaTrader_Emily]

Hello Emily,
I read the whole topic, I can confirm that I also encounter exactly all the problems exposed with the same dynamics of other users on any graph, exactly the same problem. I hope you can solve this because at some point it becomes almost impossible to be able to observe the chart especially in times of high volatility.

Hello Alex Al23,

Thank you for your note.

Is this happening on a script that you wrote or a script that was imported from a third party?

I look forward to your reply.

[Alex Al23]

Hello Emily,
I read the whole topic, I can confirm that I also encounter exactly all the problems exposed with the same dynamics of other users on any graph, exactly the same problem. I hope you can solve this because at some point it becomes almost impossible to be able to observe the chart especially in times of high volatility.

[NinjaTrader_Emily]

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!

Hello WHICKED,

Thank you for your reply.

No, I have not gotten it yet. I will gladly report this to the development team for investigation once I am able to reproduce the behavior. I will need to provide them with exact steps on how to reproduce, including a script that results in the behavior, to investigate. So far, I do not have that information locked down so I am not able to report it. That is the only hesitation I have at the moment; if I am not able to reproduce the behavior or come up with consistent steps to cause the behavior, I am not able to report it to development.

I understand that the behavior is intermittent and that it is only being observed on versions 8.0.28.0 and 8.1.1.7. Although it is intermittent, many people have chimed in that it is simple to reproduce yet I have not been able to reproduce it yet. Is there a more simplified script other than the two that you previously shared that also results in this behavior? If not, is someone able to provide a reduced sample and describe the exact environment that resulted in this behavior? My colleague previously asked you for your Log and Trace files; I understand that the diagnostic information might not fully point to the cause of this behavior, but that information would also be useful to gather in this scenario. Some folks have also reported an exception being thrown, and if that is the case that should show up in the files. We could also compare the OS and graphics card being used to see if there are any consistencies there or to determine if that information is irrelevant.

WHICKED please send me your log and trace files as well as the last time (or a few different times) when you observed the flickering/flashing behavior. I would like to investigate and see if there is any information in your files that is relevant to this behavior. You can send us your files by going to the Control Center-> Help-> Email Support. Ensuring 'Log and Trace Files' is checked will include these files. This is checked by default. Please include "ATTN Emily C" in the subject line along with a link to this forum thread in the body of the email.

I look forward to further investigating this item.