Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
In NT 6.5 you could set display update interval to 0 ms - result was you could sometimes get a feeling to be realtime in the market.
I donīt know really why, in NT 7.0 this interval is set 0,1 ms - no big delay but enough NOT longer to see when prices were knocking again and again a resistance or bottom.
Is there any chance or trick - e.g. by coding - to "patch" this interval to 0 ms again in NT 7, too.
Iīm aware that this produces CPU usage but I think this further problem could be solved by using less indicators or higher class machine.
Iīm just testing a simple setup e.g. if one of two correlating underlyings is just falling much deeper than the other to buy the quicker (much deeper moved) when I see the pullback is beginning. That would be much easier with multiple chart with NT 7 but without latency (update interval 0.0) too.
If there are other Data Feeds / Trading package competing against Ninja which allow displaying the feed in real time I would appreciate any tip, too.
Thank you for your description where update interval can be geared, exactly that menu I described in previous post.
Please test yourself, scale ist unfortunately limited and ends at 0,1s; 0,0s is not longer possible (as it is in NT 6.5).
How to tune it again to 0,0s ????!!!!!
The trick is to force NT to replot when you get a tick. This is a dangerous item if you don't know what you are doing, as you could start using way more CPU to do this. This trick only needs to be in ONE indcator. At the end of the OnBarUpdate() method, add the following:
This code will force the chart to refresh on each tick, so user beware. Your initial comment, that CPU will be fine if you manage the number of charts/indicators is spot on. To be sure you only do this in one indicator, you could have an indicator, that just refreshes the screen, but I have not tried that.
Note: This will do nothing for the DOM update interval.
Well documented in forums. This is one of the performance improvements in NT7. Of course the improvement comes from restricting updates, not actually doing anything better. That said, I think it was the right choice for NT, as many people don't understand the implications and get themselves in trouble with too many charts/indicators. The only issue is they do not provide a way for those that do know what they are doing to change it to a lower value.
They have the same feature/issue with the DOM and Time & Sales.