No historic data since friday!!!!!

[eDanny]

Thanks for the response. I would try 6.5 next week as there will be some changes coming regarding how real-time data is processed on the broker server side that will make it more efficient for NT to process in high volume times. The mini freezes you experience likely will go away.

Could you share a little more information about these changes Ray?

[trader1512]

how to upgrade

how do i upgrade? where do i find the license key?

[NinjaTrader_Ray]

No I can't however, once changes are made, I believe you will be able to get an official response from your broker.

[xenayoo]

I suppose, that it is a bug/issue of Ninjatrader. Here is the reason for my suggestion:

First i have to say, that i am coming from tradestation 8.6. Here i can chose if i wnt to use exchange time or local time. (Local time forces some issues caused of the different daylight savings between US and Europe). Further i can edit the session time for different symbol-types genarally or customize for one symbol. By editig this, i have to enter date AND time for session start and session end.

In Ninja i can't do that. I edit the time in the chart-window-properties (f.e. for the ES):
For Session begins (local time) from 00:00 to 22:30
For Session ends (local time) from 00:00 to 22:15

Edit: Now the session begin after end......

What happens?
This Chartwindow freezes - every time again. There is alwas the window "This request can' be aborted"

The ES session begins sunday 22:30 and ends monday 22:15. Or in CME-exchange-time: start sunday 3:30 pm and ends monday 3:15 pm. May be that's the main problem of accessing the historical data - where does NT know from, that the session starts the previous day? I need the correct sessionbreaks - and 0:00 isn't correct...

[xenayoo]

Oh! Seems like no one is interested in issues....

[eDanny]

No I can't however, once changes are made, I believe you will be able to get an official response from your broker.

Did the changes happen? I don't see a difference.

[NinjaTrader_Ray]

Users on older hardware or very loaded workspaces would see a difference in CPU load during volatile market activity which we have not see yet.