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)
Who is running NT7b10? Thread for tips, problems, successes, etc.
Yes, all the time. NinjaTrader's handling of exceptions is completely embarrassing, or should be, by any of their programming staff.
As for ignoring the "NinjaTrader's encountered a problem" messages, it is usually very unwise. Many things just break after that message, like strategies won't re-init, or indicators won't re-init, or in-memory corruption occurs of bar data, historical data not saved to disk, etc etc... any number of things.
Running NT7 v10 64bit with 12 charts open in one work space. No crashes to date but never had any non-indicator related crashes in the last 3 beta versions either. Using IB data
PC running Win 7 64 bit/ Q9300/ 8gb ram/ 250 GT video card.
I've been running up to 2 weeks of replay at anywhere from 50 to 500 times and I always get that message. Then it seems to run fine as I can sim trade without issue. Never happens with a live stream and executions are working well enough to actually trade, but with my phone loaded with the trade desk number just one click away.
With 9 the X was a regular occurrence, but this is the 1st time I saw it with 7b10 & it has been running 23.75 hours a day. It was only when I added a strat running replay for more than one session that it started having problems. Did it when I went out as was curious if it would run 2 weeks @ 50 times. Did not even think about using an output window. Sent the Log & Trace to NT support, see if they get back to me. Haven't bothered to check the NT Beta thread as I am sure this is not unique - from the futures.io (formerly BMT) feedback I've seen.
Hope they can fix this as it is such an important feature.
R.I.P. Andy Zektzer (ZTR), 1960-2010.
Please visit this thread for more information.
The Red X points to an exception related to ChartControl. If you want to know the details you need to look at your trace file.
I am currently getting a Red Cross, when I am loading up too much historical data at once and my data supplier stops sending historical data. In this case NT - it is version 7.0.0.10 - throws an exception, and I need to close the chart. I can then reopen a new chart and continue without any problem. I have communicated this to support, they have confirmed the bug and it should go away with the next release.
But don't be too critical: NT 7.0.0.10 is not a product that is sold, it is not yet a public Beta, but it is a half-public pre-Beta. So if you participate in a test to evaluate it, do not expect that everything works and be ready to take the pain to endure some setbacks. I am much more critical, if I look at NT 6.5., because I paid for it.
Learned the hard way that the recording indicators from Gomi & Zondor sometimes have gaps and for what ever reason fail when in binary mode. They also get super fragmented (150+ fragments at the end of some days).
Eventually will have to bit the bullet and figure why these recording failures happen. Maybe once 7 is finally released - cause NT has no interest in persistent indicators. As well as other data issues voiced by RJay.
Until then, the quick and dirty fix is to run two versions of each: 1 binary and 1 flat.
(Zondor says he will post his newest indicators and a recorder later this week.)
If you F5 and it does not refresh switch to flat and the data is displayed. Takes up a lot more space, but I only need this info for a week or two at a time,
So, delete the recording files on a regular basis and run replay with all 4 versions (see below) if you need them rebuilt.
If things go really bad I do this on a laptop running 7 with just the chart shown below.
Then stop NT and move the file to your main computer & restart NT. Can be done really fast @ 500X replay, even during market sessions.
R.I.P. Andy Zektzer (ZTR), 1960-2010.
Please visit this thread for more information.
Here is the error when starting replay with lots of stuff going on:
2010-03-07 07:28:01:079 in OnUnhandledThreadException
2010-03-07 07:28:01:126 ********* exception trapped *********
2010-03-07 07:28:01:126 Index was outside the bounds of the array.
I ran replay in a way suggested by Jason Hilling of NT support:
His explaination is longer, here is the essence:
Start replay with a bare bones workspace.
No charts, just the Control Center.
No errors.
Then open a full workspace. No errors.
Also ran a strat with a live zenfire data feed in Global Sim mode without problem, starting the same way.
R.I.P. Andy Zektzer (ZTR), 1960-2010.
Please visit this thread for more information.
I agree with fat tails, NT7 is not for sale, and the fact that we are testing it is only to our advantage, so any bugs we may come across for our type of trading can be fixed before general release, Since I have got B10 up and running, which i am doing out of session hours as using 6.5 for live trading, I am happy a lot of bugs have been fixed and it is not crashing nearly as much, and is a lot faster. i have also noted it is not using as much CPU as 6.5 (but i have yet to load up loads of charts etc so will come back with that). I have noticed a few things, I am trying to get the indis I use to work on NT7. But all in all as i did not load B9 I can see a lot of fixes have been carried out in 2 versions, thats not to say there are still a lot left to fix, but it is a step in the right direction. Sunday is B10 day in my house so I hope to able to report back.
I am really unhappy with NT 7.0.0.10 because there is quite a number of data and session related bugs that the guys from NinjaTrader do not understand. So I will post some of those here for further discussion. I am even afraid that they will never make it. You can certainly not tradwe on that!
So first post is a chart of ES 06-10 today (rollover date) with Globex session template. Merge backadjusted clearly does not work.
If you look at the chart you will discover 5 errors.
Josh answered this. They are working on these issues, but they do not make any progress since a couple of weeks. For example see this (NT 7.0.0.10):
If you use GetSessionDate(), NT7 takes the date of the beginning of the session. But this is not the session date! The session date should always be the trade date, i.e. the date of the end of the session.
Now if you take ES, the Monday session is shorter than the other sessions. The Monday session starts at 6 PM EST Sunday, the next session at 4:30 PM EST Monday. Now convert this to CET, so you will get
- one session starting at 0:00 AM CET Monday
- the next session starting at 10:30 PM CET Monday
2 Monday sessions...... the NT pivots indicator uses this, and guess what, Tuesday's pivots are calculated from Friday. LOL
I feel that they are not really understanding the problem ....