Don’t be surprised by NinjaTrader anymore given how unstable and laggy their platform is. A few days ago I ran into a issue. Right at entry, I got a price that was 80 points lower on Nasdaq. Luckily I recorded it, otherwise no one would believe it. I’m watching the chart move in my favor, yet the PnL shows -70, which made no sense. Later, when I reviewed the recording, I saw that the price in Chart Trader didn’t match the price on the chart at all. How can that even happen?
Naturally, I reached out to support. As usual, the response was absurd: “the problem is your charts.” So somehow it’s on me. The head of support, Luis, replied, clearly not someone suited for that position. I asked why there’s no warning if there’s a delay between the chart data and Chart Trader. He said they’re aware of the mismatch but don’t want to display any in platform notice because it would lead to too many support requests. I asked him if he was serious, what kind of logic is that? You’d rather users lose money than fix the issue or at least inform them properly? Then he tried to blame it on me, saying I must have installed something. I asked how that could possibly be related to price discrepancies and the lack of any warning, and after that, he just stopped responding.
And this has already happened to me three times this year. Don’t even start with explanations about internet issues, indicators, or anything like that. Also, I’ve never experienced anything like this on Lightspeed or eSignal, not once. The only reason I’m still stuck with this platform is because I’ve built a lot of custom code around it.
1 Like
OMG I am so happy to know it’s not just me!
I haven’t been able to trade for a a few weeks now due to this issue with the Ninjatrader platform. I made an appointment with Technical Support for a call back, for which I had to wait a full week! When you do get a live agent, you will only get 30 minutes, regardless if your issue is fixed or not. Mine was not, and I had to make another appointment - for which I have to wait yet another week!
I made a screen recording, too - and I showed the error to the live tech (Rogelio)
2 Likes
I’ve discovered that my SIm account shows trades properly - but the live account places those executions on the chart way far away from the actual entries every time showing under-water P&L right from the moment an entry is taken.
2 Likes
Where else could they take your money if not from a real account? A demo account always works perfectly. That’s the whole point. You relax, everything is going smoothly, and then problems arise with real money, and you get blamed for everything. Classic.
1 Like
I have been there, done that. Your data comes in slower, which gives those weird numbers. It is not NT, it is your computer or internet that just cannot apply all the data properly. I personally use an AWS server, so I am sure my internet is OK, but I ran into a CPU issue. (too many charts and indicators running at the same time, you can check for this as well).
But once I upgraded my server to a higher one, all issues were gone. I have MC and NT running on the same server, with 30 charts, my indicators, and more and my CPU does not even reach 40% at the high times…it is worth the money to have a big machine…
2 Likes
Support is correct. It’s your indicators (one or more) causing it. I’ve been fighting that for years. Whenever I see it, I don’t blame the platform, I look at what’s causing it. It could be way too many draw objects - render them instead. A lot happens during the render cycle and if you aren’t guarding every little thing, that could cause it. I’ve even created a nested class for my dx resources that keeps them from being created and destroyed repeatedly during every render cycle.
These nice fast computers have made us lazy. We used to have to consider how our code interacts with memory, disk space.. all that. With NT, old school isn’t so old school after all.
1 Like
Thanks for the advice, But you didn’t read my post carefully. — no indicators, 6 charts, strong machine. It happens maybe 3 times a year on live only, never on demo. Weak hardware would be constant, not random.
And the support is a joke — the head of support, Luis, personally told me he knows about the issue but they don’t want to add any kind of warning. Here is his exact response:
‘If your query is that there is no warning to tell users that data is not in sync, then we encourage you to submit a feature request. This hasn’t been done before due to the tailwind that comes with it when users that are not as savvy then write in about the issue immediately demanding remote support — this is not scalable and instead we have created self serving documentation so that users can learn.’
So they know about it, won’t fix it, and their solution is to hide behind documentation so they don’t get too many support calls. Just let that sink in