Missing Ticks with Patsystem connection

[tonchi]

Currently I connect to Patsystem 1st, and esignal second. This will cause the ES tick data to be distributed to the chart to come from Pats instead of esignal.

This must done in this order, or you will not get the full market depth on the superdom. Pats unfortunately misses a significant amount of ticks, especially in a fast market. I sometimes have the problem 2-3 times a day, where I know price has traded at a specific tick, but the Ninja chart does not show it, and it must be reloaded to get the correct chart solution.

Will there be anything in the NT7 version to allow the user to specify with data source powers the charts so that these type of data errors can be eliminated?

[NinjaTrader_Ray]

Currently I connect to Patsystem 1st, and esignal second. This will cause the ES tick data to be distributed to the chart to come from Pats instead of esignal.

This must done in this order, or you will not get the full market depth on the superdom. Pats unfortunately misses a significant amount of ticks, especially in a fast market. I sometimes have the problem 2-3 times a day, where I know price has traded at a specific tick, but the Ninja chart does not show it, and it must be reloaded to get the correct chart solution.

Will there be anything in the NT7 version to allow the user to specify with data source powers the charts so that these type of data errors can be eliminated?

Nothing will change in this regard in NT7. You would need to subscribe to market depth with your eSignal account and use eSignal as your primary connection for all data.