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

[NinjaTrader_ChelseaB]

Hello diegocml,

Yes, this would be what I am referring to.

If the issue can only be reproduced with 3rd party or custom scripts, we need reduced open source scripts that can reproduce the issue.

Without these, our development team does not have a way to determine what specifically is causing the behavior.


If you want to verify it is the 3rd party scripts causing the behavior:

Close all open workspaces and save a new blank workspace and restart NinjaTrader.

Then in the new blank workspace open a new chart with no template applied to a Renko chart. This would be the renko bar type included with NinjaTrader.

Add a few system indicators that ship with NinjaTrader, do not add any imported scripts or custom scripts.
A few users noted drawing objects may need to be added to the chart. Add some drawing objects if you would like, but only ones that ship with ninjatrader.

See if you are able to reproduce.

If you can reproduce using all system scripts with no 3rd party scripts, I can schedule a meet up where we can go through the steps to reproduce and I can make a report with that.

[diegocml]

Hi Chelsea,

Thank you for replying to me.

By 3rd party or custom scripts I'm assuming those are indicators from other vendors, so not the native NT indicators.

The answer is yes.

I have however noticed that the issue only occurs when I use the ninZaRenko add-on. When I use the same template/layout with all the same indicator; however, with a different Renko chart from a different vendor, the issue does not happen.

Since I am a beginner NT user - is there anything I could provide from my workspace that would help the dev team?

Thank you.

[NinjaTrader_ChelseaB]

Hello diegocml,

Welcome to the NinjaTrader forums!

Unfortunately, this flickering behavior appears to only affect a very small amount of users and at this time our team has not been provided with exact steps or a reduced script that is able to reproduce the behavior.

Our development team has been made aware of the behavior, and are currently waiting for a user willing to provide minimal exact steps and / or reduced script that can reproduce the behavior so we may open a formal bug report.

When you were able to reproduce, may I confirm you are not using any 3rd party or custom scripts and that you are using all default system indicators installed with NinjaTrader?
What specific indicator was added to the chart when the behavior began occurring?

[diegocml]

Has there been any fix on this issue? I'm experiencing the same issue. I have tried creating a new workspace from scratch but it did not solve the issue. I did save the template for each indicator and then just loaded the indicators manually and loaded their individual settings, though. Maybe I can't use this "short cut" to speed up the cloning process and really have to dial in each indicator as I go?

[WHICKED]

I’m experiencing the same issue—screens with split-second flickers. I noticed the problem started after updating to the new version released in December 2024. While I do use third-party addons, even after removing all instruments from my personal workspace and leaving the charts on default, the flickering issue persists. However, it’s much less noticeable and lasts for a shorter time when there are no instruments slowing down the charts. The way I confirmed the issue still happens was by enabling the global cursor across all charts.

The problem does not occur with new workspaces. It seems that when an update happens, the workspaces somehow get corrupted and end up with this issue.

In case you’re wondering, I also tried updating drivers, downgrading NinjaTrader, and importing backups, but none of these worked.

The solution for now? I think the issue simply requires creating a new workspace and setting up your personal charts from scratch. It’s a hassle, but it really seems to be the only viable fix at the moment.

and yet.... reports keep coming that this is happening. but yet NT will state nothing changed. even though it has been pointed out it started to happen on version 8.0.27.x+.

something changed with the chart refresh/scaling, and doing a code comparison between 8.0.26.x and 8.0.27.x would show a developer the mistake.

[juanp3110]

I’m experiencing the same issue—screens with split-second flickers. I noticed the problem started after updating to the new version released in December 2024. While I do use third-party addons, even after removing all instruments from my personal workspace and leaving the charts on default, the flickering issue persists. However, it’s much less noticeable and lasts for a shorter time when there are no instruments slowing down the charts. The way I confirmed the issue still happens was by enabling the global cursor across all charts.

The problem does not occur with new workspaces. It seems that when an update happens, the workspaces somehow get corrupted and end up with this issue.

In case you’re wondering, I also tried updating drivers, downgrading NinjaTrader, and importing backups, but none of these worked.

The solution for now? I think the issue simply requires creating a new workspace and setting up your personal charts from scratch. It’s a hassle, but it really seems to be the only viable fix at the moment.

[llanqui]

if you can reproduce it on demand then they can fix it

[WHICKED]

why don't those who have this problem get together and see how to reproduce it consistently, especially those who are software engineers?

that would help Ninja debug it

if they can't reproduce it they can't fix it

for myself, when I reduced the large number of draw objects, my particular problems with the rendering went away (cpu thread overloaded)

reducing the number of draw objects is not a solution. there is an issue with NT platform. in 8.0.26.x, this flashing/rescale issue was not present and the code did not change from the vendors or the other programmers. As soon as 8.0.27.x and future versions became available the flashing issue started. AGAIN no code was changed from the vendors or the programmers. the only thing that changed was the version of NinjaTrader, which means SOMETHING WAS changed on the NT platform.

Again, to clarify 8.0.26.x no flashing issue no changes to code

8.0.27.x+ flashing/rescale issues and no change to code

8.1.x.x flashing/rescale issues and no change to code

something between 8.0.26.x and 8.0.27.x broke something with rendering, rescaling, etc. especially when dealing with non-time based charts (range, etc.)

[llanqui]

why don't those who have this problem get together and see how to reproduce it consistently, especially those who are software engineers?

that would help Ninja debug it

if they can't reproduce it they can't fix it

for myself, when I reduced the large number of draw objects, my particular problems with the rendering went away (cpu thread overloaded)

[NinjaTrader_ChelseaB]

Hello WHICKED,

There is not a tracking ID for this. I've just let one of the developers know that a forum user is stating there is flashing behavior that I am not able to reproduce and to keep a look out for.

They have let me know they will keep an eye out and if I am able to determine the issue is not a performance related issue and am able to provide reproducible steps to submit a bug report with those steps.

[WHICKED]

Hello WHICKED,

I understand. I've let our development know to be on the look out for flashing charts.

Note, I won't be able to report a performance issue in a bug report.

Is there a tracking/ticket number associated with this?

[NinjaTrader_ChelseaB]

Hello WHICKED,

I understand. I've let our development know to be on the look out for flashing charts.

Note, I won't be able to report a performance issue in a bug report.

[WHICKED]

Hello WHICKED,

I can confirm I have supported users with performance issues with 8.0.26 and previous.
It has been common problem even back in much earlier versions.
The forum page on performance I've linked was posted in 2019 while 8.0.26.0 was released in 2022.
Yes, even the fastest computers will eventually overload the single logical processor all of the indicators are running on once enough scripts are demanding CPU resources.
Note, that all indicators running on the same instrument are running from the same instrument thread and will all be utilizing a single logical processor of the CPU.

"Yes - the chart can be moved freely left and right - they are not lagging behind."
Just to confirm, the chart can be scrolled smoothly while the flashing is occurring at the same time?
Are you able to reproduce without the multitude of indicators added?
Can you reproduce using the earlier steps you have directed me to take with just the unirenko and a single drawing object on each chart?
Or is there a specific indicator that when added once to a chart, with no other workspaces open or other charts in the workspace, can reproduce?

We need to verify the issue is not a performance issue and we don't need a large amount of running indicators to reproduce so that we know we are looking at a bug with the platform.
Then we will need minimum steps so that I can reproduce so that I make a bug report.

If don't have these to make a bug report, I've noted our development about a possible issue with no steps to reproduce, so they can investigate.

the ticket should be opened - multiple people have replicated the issue and appears to not be with a lot of drawing objects. QuantKey_Bruce, Leeroy_Jenkins, all of these that have wrote in have seen the issue on their platforms.

This may be an old issue - but the rescale/flicker - that was not apparent prior to 8.0.27.x.

[NinjaTrader_ChelseaB]

Hello WHICKED,

I can confirm I have supported users with performance issues with 8.0.26 and previous.
It has been common problem even back in much earlier versions.
The forum page on performance I've linked was posted in 2019 while 8.0.26.0 was released in 2022.
Yes, even the fastest computers will eventually overload the single logical processor all of the indicators are running on once enough scripts are demanding CPU resources.
Note, that all indicators running on the same instrument are running from the same instrument thread and will all be utilizing a single logical processor of the CPU.

"Yes - the chart can be moved freely left and right - they are not lagging behind."
Just to confirm, the chart can be scrolled smoothly while the flashing is occurring at the same time?
Are you able to reproduce without the multitude of indicators added?
Can you reproduce using the earlier steps you have directed me to take with just the unirenko and a single drawing object on each chart?
Or is there a specific indicator that when added once to a chart, with no other workspaces open or other charts in the workspace, can reproduce?

We need to verify the issue is not a performance issue and we don't need a large amount of running indicators to reproduce so that we know we are looking at a bug with the platform.
Then we will need minimum steps so that I can reproduce so that I make a bug report.

If don't have these to make a bug report, I've noted our development about a possible issue with no steps to reproduce, so they can investigate.

[WHICKED]

Hello WHICKED,

I the template you have provided in post # 72 causes errors as there are indicators I don't have.

To confirm, the behavior absolutely cannot be reproduced without the template?
(If so, we would need to rule out the template being the cause of the behavior.)

Also, the amount of indicators could be causing a performance issue.
When the flashing occurs are you able to smoothly scroll the chart? (If not, the CPU is overloaded and the number of indicators needs to be reduced)
Is this not possible to reproduce without the massive amount of indicators? (This would also indicate an overloaded CPU)

Yes - the chart can be moved freely left and right - they are not lagging behind.

Regardless of number of indicators etc. - this rescale issue happens as others have stated. The template that was given is an example and makes the issue producible - even with some of the indicators not attached you would still see the issue.

Weird how the statement of 8.0.26.x did not have this issue seems to be overlooked. Why would it all the sudden start having issues after 8.0.26.x ?

unless - there were changes on NT's side...

mentioning of performance issues - top of the line machine - fastest CPU available single threaded and still its a CPU issue?

If its a CPU issue then why after 8.0.26.x did this issue start happening? That statement would not make sense.