|
Berlin, Europe
Legendary Market Wizard
Experience: Advanced
Platform: NinjaTrader
Broker: Interactive Brokers
Trading: Futures & Stocks
Posts: 9,887 since Mar 2010
Thanks Given: 4,242
Thanks Received: 27,117
|
Hi TraderJesse,
I use charts with a dark background, so I am not getting white screens but blue screens, LOL. I know them from my earlier days in front of MS-DOS PCs. The only difference is that Microsoft's Blue was somewhat brighter than 's.
So there are two conditions that favour white or blue, let us say empty screens.
(1) The pivot indicator loads daily data, when set to DailyBars. This means that it accesses intraday data and daily data at the same time. This may create a deadlock within NinjaTrader. So if you use NT 6.5., simply set the Pivot indicator to "CalcFromIntradayData" mode and it will be more stable. If the Pivot indicator is not in DailyBars mode, it should not create any problems. The same applies to the SessionPivots indicator. Please note that both pivot indicators may display inaccurate pivots with "CalcFromIntradayData" , if the wrong session is chosen or if they are applied to range bars.
For initially the same problem occured, but if you check the code for the latest NT7 pivots indicator you will find that the loading of daily data is now done via a separate threading. So NT7 first will load intraday data, and only after loading of intraday data is complete, will proceed to load daily data. This causes the pivots indicator to be displayed with a delay of a few seconds but the process is stable and does not produce empty screens.
(2) You may also create deadlock in a similar way, if you change the symbol for connected charts. Since I started loading my charts one by one, I have reduced the number of NT 6.5 crashes on loading historical data from about 20 per day to 1 or nothing.
Again this does not occur on NT7. NT7 is quite stable on backfilling historical data. The only exception that I noticed with NT 7.0.0.10 is a red cross following data throttling of Interactive Brokers. This bug was addressed by NT development staff and should be removed with NT 7.0.0.11 So far I have not tested this.
|