NT 7 is getting better, but there are still lots of issues:
Whenever I try to delete a day of tick data -> crash. Now, I am deleting data by directly accessing the folder of the data base, as the data manager is of little help.
Also MergeBackadjusted does not work during the first hours of rollover day. The offset is only calculated after 4 to 6 hours, probably because NinjaTrader confuses the session template, system time and US Eastern time, for calculating the offset.
There are some flaws in the way the concept of session times has been implemented.
I know some people are using ninja 7 and claim they don't have problems. That was me until beta 16+ came out, then i ran into some serious problems. I had a string of losers for one week, which i later found out it was because of Ninja, not my trading style. That seriously pissed me off because not only did i lose money, but i spend another week not trading and reviewing what the hell was going wrong. (There's a post i did a while back with volume bars and IQ feed if you want to know what im talking about). I would have much rather have someone else be the beta tester with their money, not me.
For those that are still using beta to trade live, eventually, your bound to run into a few bugs. I do have to admit that they're improving, and its snappier than their first release, but i doubt that beta 19 or 20 will be the final release version.
Nevertheless, don't use beta software to trade real money. I paid for it, so have others. I do have to say that I complain alot because i really like Ninja, and its just a huge disappointment when i run into problems because i expect it to perform a certain way. But you guys have to accept that its beta software. If Ninja had problems like this on their final release, that would be a different story.
The following user says Thank You to Michael.H for this post:
I trade live with NT17b18. I send them my bug reports and the log files but they always come back to me that they can't replicate it (at least they are looking at it, I think)
What are the alternatives ? I need a charttrader and my automated strategy runs on NT. I like Ninjatrader like we all do, but you got to be kidding me about all those crashes. Give me a break please, it's not nuclear science, it's a bloody simple software program and we're 2010.
6.5 Mostly, it is buggy and unstable even after several years, ... I did try 7 for a while in the hope that it would be more stable than 6.5, that was a big mistake and I have been on 6.5 ever since, but it has random crashes and bugs.
For example NT 6.5 has the famous CL bug, where it dosn't report your open CL position when used with IB. NT dosn't bother to inform any of their clients about this, you just have to discover it the hard way.
On their forum they claim to have a work around for NT7, but then you would need to run beta live.
That's just one example.
And no Luke, I don't like to loose money.
The following user says Thank You to webart for this post:
Yes I know the feeling regarding reporting bugs and them not being able to replicate it. Meanwhile, back at the ranch there are numerous people also reporting the same issues as ones that get reported.
Not only that, you can prove to them that the issue is not an issue with your hardware as other software or similar parts of software work successfully but because it does not happen on "their" system, it is not a bug. Not good and another reason why I will not splash out and buy it, unless their attitude towards having issues no matter how big or small are solved.
Overall, its a bitter sweet relationship really, lots of nice features and things about NT, yet so many stupid and unthoughtful ideas lack. They could easily get the polish out and shine that mother but for whatever reason, they just plod on with deaf ears at times.
In their defense, if they can't replicate the problem it is very hard to fix it. I have had that problem with an indicator where I had two testers report the same problem and I could not replicate on two machines and using both NT6.5 and NT7. Then after a week I saw the problem on one machine in NT7 and was able to nail down the problem area. Some things aren't always quite 'in-your-face' apparent.
The following user says Thank You to eDanny for this post: