Hi Ztrade101, Yes I did a clean install, saw your post on clean install the other week. Uninstalled from add.remove programms, then deleted the NT7 file in My Docs, then did a search for NT7 to make sure i didnt miss anything before i installed.
Favorite Futures: CL & 6e, looking at ES, ZB and AU again.
Posts: 2,100 since Nov 2009
Thanks: 1,104 given,
Memory usage of NT7 & minimal startup suggestion
Here is a screen shot of the Utilization running 7 workspaces.
If you are having problems I suggest starting with no workspaces, just move then out of the NinjaTrader 7 folder. then connect to your data fees and open a time&sales window. Then add a chart at a time with as minimal template. - maybe EMA20. See what happens.
Worked for me after the computer & NT7 learned to play nice. Don't ask me why it just started working.
R.I.P. Andy Zektzer (ZTR), 1960-2010.
Please visit this thread for more information.
Favorite Futures: Gameplay KlownbineŽ Trading of Globex
Posts: 1,276 since Jul 2009
Thanks: 1,227 given,
NT7B10 stress test
I have 9 workspaces running concurrently. Each one has three or four charts, and one of those charts in each workspace has three different GomRecorders that are recording binary files. I am a little concerned about whether running 27 of these at the same time will cause a disk i/o bottleneck during fast markets. So far so good, no crashes.
Task Manager says that NT is using 238 MB or RAM. My system has 3.2 GB.
Generally a nostart is because of a corrupted chart or workspace. Whenever I had this problem I got rid of all the existing workspaces, restarted, and rebuilt them. See ZTrade101's recent previous post. Another thing to do that really helps is to make sure that the chart dataseries lookback period is about 200 to 300 BARS back. When I used DAYS back the charts would load very slowly.
NT came back to me with the findings on trace file, I did not have the PFG connection loaded for NT7!! Feel stupid now, such a simple over sight!. Anyway its loading, connecting etc, will play with it over the next few days and post findings.
The SessionPivots indicator above is based on the NT 7 pivots indicator. However the NT version still is flawed, because it uses GetSessionDate(), which currently does not work correctly. This will result in false values depending on SessionTemplate and TimeZone of PC clock.
Not use SessionPivots in DailyBars mode with Zenfire, as Zenfire does not supply daily data to NT. Select correct session for the instrument. Do not use DailyBars between session close and midnight local time, as NT does not correctly update the daily bars, again depending on the session template. SessionPivots indicator is more or less foolproof in CalcFromIntradayData mode, when correct session is chosen.
Otherwise I have found NT 7 to be very stable, I have had no crashes with NT 126.96.36.199 so far, much better compared to NT 6.5!