Hello,
I just opened NT account. For now I’m using the Demo only. And from day one basically I can see that the chart is lagging behind the Super DOM. How to trade if I see different and confusing data? Impoossible. Why and how to fix it please? I have decent i7 computer with 32GB memory. I see the similar problems reporting in 2012 and 2024. Is there a way to fix this? Thank you, Art
For people here to help you you’ll need to provide more information/context regarding your NinjaTrader set up alongside looking back through the many many threads on chart lag in the archives looking for situations that look similar to yours.
But, I think it’s fair to say the latest builds of Ninja are generally stable and don’t suffer lag (although there were problems with Ninja’s Order Flow tools introduced in v .6 (don’t know if you’re using)
Simplest first troubleshooting step is run Ninja in Safe Mode (hold down Ctrl when double-clicking launch icon). This will launch NT with all third-party add-ons disabled. If no lag, it suggests a third-party add-on is causing lag and you can add them one by one to identify the culprit
If Safe Mode doesn’t fix lag, look elsewhere. Things like MS OneDrive are known suspects
Good luck
1 Like
I believe the Dom is always a bit faster than charts because it doesn’t have the throttling that chart updates have.
1 Like
Chart Lag (as reported) and Chart/Dom Refresh rates are different things. The DOM Refreshes more frequently than Charts which are limited to a very pedestrian and quite ridiculous 250ms/4x per sec (which can be overcome using add-on ‘Tick Refresh’ available on Ecosystem). (Co-incidentally, I notice Release .17 purportedly allows the PriceLine Label Price Value to refresh at DOM speed (NT acknowledging the requirement) but doesn’t say this applies to chart refresh. Remember that NT SEVEN didn’t have the not-fit-for-purpose 250ms throttle)
Chat Lag is a different issue - when displayed price is delayed, lagging real time prices at the Exchange and on the DOM (and making a mockery of trading from a lagging chart), and can be shown using add-on ‘ChartLagMeasurement’ available on the Ecosystem
If the #OP is simply observing the difference in Refresh rate then yes its ’baked In’ but can be overcome with TickRefresh add-on, if it’s Lag, ChartLagMeasurement will display it
Hope this helps
Best,
1 Like