i've searched, yet maybe not enough, for a thread that discusses issues with NT8 tick replay and software that uses the feature.
back in June of 17 i exposed myself to order flow software and now feel like i can't live without it as an overlay to my volume chart based system that i've been developing for some time.
i purchased a very simple order flow package that offers only bar mode, buy/sell imbalances, bar delta and buy/sell imbalance ratio. the software was quite inexpensive - baiting a hook comes to mind.
since then i've had nothing but crash problems on whichever platform of two that i run this order flow software that requires tick replay.
i've moved all of my other custom assemblies to the non tick replay platform except for Lizard Trader's Opening Range premium indicator.
i did have one custom assembly that seemed like it contributed to a greater number of crashes and may have unfairly blamed it on the issue but the issue still persists even after multiple complete uninstalls and re-installs of NT8 - deleting the NT8 documents folder - then rebuilding the workspace from chart templates...
the most recent discovery i've come across in trying to discern what is causing the crash issues is that i can make changes to any indicator parameter while live data is off without having a crash. if i turn on live data i can only make so many changes to the chart that's running tick replay before i get a crash or something happens that causes a later crash while nothing is happening on the chart other than plotting live data. this really leads me to believe that there's a fundamental problem with NT8 tick replay or the fact that i'm on Windows 7 or something fundamental like this.
Windows 7 Pro SP1 with all updates
NinjaTrader 8 v13.1
NOFT order flow visualizer v6.1
Lizard Trader Opening Range v1.3
all else default NT8 indicators and 2 simple indicators i modified from NT8 default indicators
the NT8 log always gives the same error message: Error on calling 'OnRender' method on bar ___: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
i'll try to add screenshots of the Window App log entries.....
thanks in advance for your time and any input /
wes