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)
NinjaTrader 7 Beta 20 - any news + experiences on this one yet ?
I've been using NT 20 since it came out and have found it to be very stable. No crashes yet knock on wood. I was compelled to make the switch since NT 6.5 was horribly slow during fast market conditions. I haven't really seen NT 20 work in a fast market yet but I'm encouraged thus far.
Running a Default Optimiztaion on a few parameters of a strategy: uptime 3days,10+hrs 65%-80+% 4 core cpu load (Intel 9650X) 95% frequency 2.5GB ram use(climbing). When I first ran the test it locked up on me because I wasnt using a pagefile: set the PF=10GB on a 8GB ram machine and now of course Win7 isnt using it, but NT7b20 is stable. I expect I will be aborting sometime tomorrow if its not done. sidebar: NT didnt die when I had 3 ISP interruptions (total 3 hours) during 2 days while this was working.
One, in overlaying indicators (I LOVE to overlay indicators). Whenever I change the DataSeries from one setting to another (say, switching from 8 range, to 12 range) any overlaid indicator I had set to SCALE JUSTIFICATION = "LEFT", seems to revert to "RIGHT" & I have to manually set it back to "LEFT". But, since I save all my various chart templates, simply re-loading the same chart template seems to fix it, but it is a bit inconvenient when changing DataSeries. I guess a way around that would be to simply create several charts (6 range, 12 Range, 24 Range, etc) instead of switching back & forth on the same chart.
Another one I noticed earlier this week: My ACCOUNT PERFORMANCE didn't seem to be including the latest trades. It was reflecting the totals UP TO, but NOT INCLUDING the last trade(s). Clicking through the various tabs at the top of the ACCOUNT PERFORMANCE TAB (Summary, Graphs, Executions, Trades, Periods, Orders, Journals), then clicking on the Summary tab once again, seemed to cause it to update the account performance totals properly.
After all, it's what you learn AFTER you know it all, that counts!
It is stable but I reported a few crashes and a bug in while trying to save an ATM strategy in the chart trader. The solution of the programmer that was bug fixing it was to create it in the DOM and then use it in the chart trader. He was keep telling me he couldn't reproduce the bug.
It's like every time they release a new beta to fix things they mess up other things.
I have sended them the last 3 months A LOT of crashes/bugs and up till now they told me they could not reproduce 1 of them !!!!!
I feel their programmers lack skill. But hey, we're 2010, and it's only a fairly simple $1000 software program to make money right ? We shouldn't expect something stable or state of the art do we ?
I have a feeling their code is bad from scratch up and they are always trying to fix the messy code. Why doesn't multicharts crashes ? Why doesn't multicharts releases a chart trader :-)
For me NT 7.20 is stable, but there is still a number of issues.
-> false data for rollover day with MergeBackadjusted
-> GetSessionDate() does not work correctly -> returns 2 Mondays per week
-> GetSessionBar() does not work correctly -> related to GetSessionDate()
-> Pivots in Dailybars mode cannot be called by other indicators, value returned is 0
-> Drawregion() creates speech bubble like or Baloo like areas
-> with Interactive Brokers false volume spikes are displayed
-> with Interactive Brokers opening price of a position is often displayed as 0, causing chart compression
But preferring NT 7.0 over NT 6.5, which is crashing on Interactive Brokers when loading historical data all the time.
