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)
I have unfortunately started to have quite a few stability issues with the latest release.
NT8 seems to just randomly crash when I load up a new symbol which I do many times a day because I trade equities.
I’ve tried the cache clearing file and it doesn’t seem to help much
I even discovered a bug in this version where global cursor tracking doesn’t work correctly if you have multiple chart windows with overlaid indicators. Obviously I reported the issue to Ninjatrader who said they knew about it but this doesn’t inspire confidence in the software.
Hi iTrader... here is the file. Drop it into your MyDocuments>NinjaTrader8 directory. This is a .txt file. You will have to rename it to .bat file. You can have it start NT 8 in High Priority if you like by removing the "rem" in front of the last line... If you have issues, please send me a PM.
There is more maintenance that I do... I delete and rebuild the _Workspace and the Chart Templates. You can look at an earlier post with jTrade to see how.
I've noticed this same problem and I thought it was me. I use three charts per instrument simultaneously - a 5min, Volume and Unirenko chart. The 5 min and Volume track the time correctly but the Unirenko chart is way off. I use the same type of directory cleanup when starting ninjatrader but between removing the log file and starting ninja, I remove the _Workspace.xml and copy a clean one to the same filename so my charts all open up in the background correctly.
Our life is our own today. Tomorrow you will be dust, a shade, a tale that is told. Live mindful of death, the hour flies.
Does anyone have a problem with the crosshair pointer (just the regular one, not global)?
With very minimal charts (a total of 3 active volume charts, and with a very few totally basic NT-supplied indicators), it noticeably lags the mouse, and often jumps and skips, or stops moving briefly. It's almost OK with this minimal setup during non-busy periods, but when the market is busy, such as right after the RTH open in ES, it is essentially unusable. The regular arrow pointer is completely smooth.
I saw a few posts on the NT support site on this issue, but the NT replies seemed to be that it had been fixed with the previous release.
After I do some more testing, I'll put up a post on their site as well, but I thought I'd ask if anyone else is having this problem first.
After more than two weeks of using NT8, this is the main issue that I have had. It is much worse with more charts up. I'm not doing any of the tricks involving deleting files or clearing cache (yet), as I didn't have anything else go too wrong (yet ). I'm on version 8.0.12.0.
We have some reports of users that have crosshair performance issues. We had made improvements a release or two ago which helped many of these users but not all. R13 is coming out within a week which includes additional performance improvements for the crosshair.
Disclosure: This communication is sent to you by NinjaTrader, LLC, a software development company which owns and supports all proprietary technology relating to and including the NinjaTrader trading platform.
Thanks for the info. I should say that my charts are all volume charts, so they would naturally be busier during high-volume periods (as would tick charts). I haven't tested time-based charts since I don't use them, but I should do that too. (Since time charts only update at the same interval no matter how busy the market is.) Are you using time or tick/volume charts? It could matter.
I am glad to know that someone else is not seeing the problem, although I wish that I were that person.
Thanks for this reply. I'll be eager to see if there's a change in my situation with the new release.
I have been on the phone with Patrick yesterday for over two hours, due to the number of issues (mainly freezing and crashing) I kept having with NT8 v8.0.12.0.
I also had issues with the Order Flow Cumulative Delta indicator not loading correctly prior to the rollover.
It looks like some of the issues I was having are not appearing anymore in V8.0.13.0 (no crashes or freezing so far), but CD is still not sorted. Please below the email I have sent back to support.
I think this should be sorted before the official R13 release.
"I did not experience crashing or freezing yet, but Cumulative Delta is far from being sorted. Despite that fact that it apparently loads correctly, it sometimes just does not look right and I discovered that the CD bars are not painted correctly.
I found that changing the Auto Scale from enabled to disabled makes the CD appear and sometimes they will keep printing correctly, other times they will load up to the point I changed the Auto scale setting, then stop printing again.
Basically, it looks like it is something wrong with the Auto scaling of the indicator.
Please see attached video that shows the issue on different data types.
I would be grateful if that would be sorted (in any case before the official release of the 13 version), as this is an indicator I use a lot in my trading and I know I am not the only one who does.
This all the worse, as my other CD third party indicator, as you could see yourself, makes all my price bars look grey and it only shows the last bar, so I have now no CD indicator that I can use.
Also, if the issue can be fixed, may I make a suggestion regarding that indicator: I would like to have the option of it to not reset at the start of a new session, but accumulate continuously from session to session - that will probably help with the scaling as well, as it would not finish at say 10k one session and start again from 0 on the next session."