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)
This example shows that with NT 7.0 most of the problems of NT 6.5 have been solved, but there are some minor issues remaining.
Trading CL via NT 6.5 / Interactive Brokers was impossible. This is history.
For NT 7.0 there is a workaround for all affected instruments (futures contracts with last trading date prior to the nominal contract month, such as CL, BC, SB ), which works well.
There is only one problem. You cannot rollover on Mondays for instruments which use the workaround. For some reasons the fact that there is no Sunday data causes NinjaTrader to trigger data requests for the old contract, which are refused by Interactive Brokers API.
Workaround: Enter Saturday as the rollover date. This will lead to the expected result, as NinjaTrader will then select Friday's close to calculate the offset.
Edit: Workaround does not always help. Do not select CL as default instrument for start up. Once NT is connected you can switch to the CL workspace without problems. Maybe I do not understand, why it does not load in the first place. It is just sure that it is related to rollovers in mode MergeBackAdjusted. Nothing really serious.
I also don't find it slow. It's typically as fast as compiled c# is on your machine. I've had full level 1 and 2 being processed with plenty of calculation in ten strats and hardly a dent in CPU usage.
I posted a thread on NT forums about issues causing rectangle objects to draw inconsistently across charts. The main issue is that if I manually draw a rectangle on 30min chart, and try to change the setting to have the End Time into the future, it throws an error. Yet if I draw the same rectangle on 405 min chart, it draws as expected, even if I extend the End Time into tomorrow's session. In both charts I use the "Use instrument settings". Quite annoying.
Unfortunately, NT's response was less than expected. They claim you cannot draw into the future using the "Use instrument settings" session template. Yet this is what I do all the time! Just place a horizontal line on a chart and see where it ends!
I see quite a few issues, and I wish NT gets a better grasp of the drawn objects. Hope the next iteration of NT7 does a better job.
I have similar issue with ellipses. When I mark up my charts, I draw red ellipses on losing trades. When you draw an ellipse on a chart, then change the chart periodicity, then change the period back to the original, sometimes the ellipses get elongated along the time axis, because they somehow they loose their original sizing data.
Not sure why these little discrepancies in NT7 objects cannot be resolved. I can only assume, maybe, just maybe, there is a disconnect/misunderstanding between their support team and developers. The drawing objects have been persistent in their inconsistencies and would like the NT rep on this forum to put more emphasis on it in the gathering, understanding and resolution of these matters in the next iteration. Its been sometime since the release of NT7, so it would only be fair if its users are granted a little more improvements on the drawing objects.