Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
It also includes the reply from NinjaTrader_AlanS. The fact that I got the reply 'The development team is aware of this behavior and is working on implementing a fix in the next release of NinjaTrader 8.' made me think your colleagues were aware of the global cursor problems.
I have been on the phone with Patrick yesterday for over two hours, due to the number of issues (mainly freezing and crashing) I kept having with NT8 v8.0.12.0.
I also had issues with the Order Flow Cumulative Delta indicator not loading correctly …
) mentioned that 8.0.13.0 was very stable so I didn't bother reporting my current freezing/crashing issues with 8.0.12.0; I've already wasted enough time with this issue I don't have access to 8.0.13.0 (I assume as I am not on the beta programme), so I can't comment on his experiences.
Can you help answer these questions from other members on NexusFi?
The confusion comes from the fact that the underlying issue you referenced had to do with scale justification and not the cross hair which is why we were were unable to locate it. Thanks for pointing me in the right direction.
The second issue with the crashing you reported today is likely unrelated to the first and is something we would want to investigate.
Disclosure: This communication is sent to you by NinjaTrader, LLC, a software development company which owns and supports all proprietary technology relating to and including the NinjaTrader trading platform.
I took a look at the linked post and read the thread, and it looks to me like NinjaTrader_AlanS understood you to have a problem with the justification of the two indicators, VOL and ATR, when they were dragged onto the same pane. He didn't seem to pick up on the issue being also about the global cursor, although you did mention it in the beginning.
I think there were two bugs there (cursor and scale justification), and he glommed onto the scale thing and missed the cursor issue, which is probably why @NinjaTrader couldn't find the post when he looked for one on the global cursor.
This might not be right, but I suspect that your global cursor issue got overlooked due to a misunderstanding by NT support, and he was possibly referring to the issue of the two indicator scales:
I can't tell myself if the crosshair issue was just a symptom of the scale justification or really two separate issues. In any case, I have asked my team to re-review the original post.
Disclosure: This communication is sent to you by NinjaTrader, LLC, a software development company which owns and supports all proprietary technology relating to and including the NinjaTrader trading platform.
I came by here earlier when I was having laggy local cross hairs issues (didn't try global).
Thought I would feed back some positive info FWIW.....
To cut to the quick, it was an NT8 coding problem, which in the build provided to me has been fixed.
Doesn't mean it will be a fix for others' issues here - a silver bullet for any and all - and as far as I understand it was related to use of multiple data series in the same chart which may or may not be relevant to others' problems, whatever their cause, but here's hope....
I think 3 things are worth noting - my Workspace was and is 100% free of any third-party anything, the problem was a Ninja 'stock-Ninja platform/indicators' coding problem, and it has now been resolved. Along the way, I was informed there's a known (but not publicised) issue with Ninja's OHL indicator hogging resources if use 'only plot latest'.
I have been using my setup daily for approx. 1 month running multiple Workspaces, circa 30 chart Windows @ 3 chart tabs each with 3 data series on each chart, fastest 5 sec sometimes down to 1 sec on fast instruments such as NQ, FDAX and data-rich such as ES, multiple DOMs i.e. a truckload. Medium spec cpu & gpu and 3 x 4k screens so lots of pixels and fair throughput of data stream. CPU typically <15% and even Fed news doesn't make it wheeze - I do not perceive any lag - cross hair, chart, DOM, order entry etc.
On the other hand I don't have much else to trouble the setup - no footprints, order flow or the like. But I can say that I did have local cross hair lag, the cause was 'within Ninja' - absolutely indisputably so - and they have resolved it.
Getting to the point of Ninja accepting it was a product problem was painful and time-consuming, and, being well-versed in the usual mantra of 'we always find it is someone else's fault' and knowing this was not possible, I went 'squeaky gate' and posted on the NT Support Forum to which their fearless leader responded.
It still irks me that just the other day I got a notification to a thread I must have subscribed to here under the NinjaTrader handle spouting the 'I've never seen a problem that isn't third party'. Yeah right. I hope said individual enjoys their second day working at Ninja as much as they were on what obviously must have been their first day with the company. For the avoidance of doubt lest it be misconstrued, this is meant in a light-hearted manner, I'm not here to troll and staff are always polite and constructive, but my experience is 'mea culpa' are not part of the company culture
I've encountered 5 separate 'issues' in moving to NT8, which has taken a large amount of time to investigate (embarked on this before Christmas and was close to aborting for the second time), and every single one of them has been a failure, shortcoming or unexpected behaviour with the 'stock product'.
I haven't finished migrating yet, but am now enjoying using 8 daily and haven't seen an error in my log for a good while
Now on to my next 'Project' - Rays don't accurately transpose to smaller timeframes, known about since 7, not fixed in 8 and no plans to do so....
If that was on FIO, then that was me and it definitely was not my first day of employment considering I am the Founder and CEO
First, I am glad your crosshair issue has been resolved with the custom install we provided you. I personally got involved in your case and determined that how you used the OHL indicator in part, created the crosshair lag you experienced and led to us optimizing the indicator for performance. Additionally, the workspace you provided allowed us to magnify the crosshair lag you experienced which led to the improvements that will be released with R13.
That being said, it is not uncommon for our users to report distinctly different experiences under the same generic terms like “lag” which leads to the public conflating issues. A crosshair lag for example, is a very different issue than a data lag. Our experience is that the overwhelming majority of performance issues are caused by custom user or 3rd party code and if memory serves me correctly, my comment was directed at data lag. The crosshair lag is definitely on us. My point simply is that in diagnosing any reported issue, we have to isolate out custom code and strip the workspace down to native NinjaTrader code only. When a user reports an issue we absolutely want to understand what it is and if its in our code, we want to fix it.
Disclosure: This communication is sent to you by NinjaTrader, LLC, a software development company which owns and supports all proprietary technology relating to and including the NinjaTrader trading platform.
I will await the next release, I believe 8.0.13.0, to see if they've fixed the cursor issue that I'm having.
I run almost no time charts -- almost all are volume. I find that time charts have (relatively) little lag, but volume have plenty. The less that is going on in terms of indicators, non-minimized charts, etc. the better off the cursor lag is. Why the cursor would be so severely affected by CPU use is hard to understand, but it is.
I know they always advise cutting everything that uses CPU back to a minimum, but that is not necessary in their competitors, so I think they just have some fixing to do.
In NT's defense, very often the culprit is actually some poorly-written indicator, but it is not always.
So I am waiting with some eagerness at this point for the next release. We'll see how it goes....
Bob.
---------------
Edit: I didn't see @NinjaTrader's last post before I posted this, so I did want to say that his points make sense, and it is not a simple thing to debug and resolve a user issue, especially when the user's report of the issue may not always provide all that is needed (or even be comprehensible ).
So, I don't mean to be critical. I'm just waiting for the fix, basically. But thanks to @NinjaTrader for being responsive here.
Many moons ago I was certainly an NT8 'basher', on FIO and on the NT forum. I had many issues. I had many crashes. But I was invested in NT with a lifetime license and I felt I could only work through the issues with NT support, which I did. I didn’t want to switch platforms as I was moving my stuff over to NT8, and, well I had to tough it out.
NinjaTrader knew that by releasing NT8 when they did, they were opening themselves up for a flood of negativity. In hindsight I feel bad because I was quite harsh at the time, but from memory, the crashes happened during open trades and there is nothing more frustrating than your platform failing you during that time.
With subsequent releases, NT8 has got better, much better. I have been running a trading room for the last 7 months and NinjaTrader has seldom crashed. In fact I can’t recall when it last crashed during RTH.
That isn’t to say it is perfect, I still get the occasional memory leak and if I try to move quicker or click quicker than NT8 will let me, sometimes it hangs and falls over, but it is much more stable and the worry in the back of my head of an imminent crash has more or less evaporated.
During my ‘bad time’ using NinjaTrader I was using a Volume Profile indicator from a vendor, whom will remain nameless. The vendor chastised me for going to NT support about my NT8 issues and was pissed off that I did, because I was calling his indicator out as the culprit. He blamed NinjaTrader and NinjaTrader questioned the 3rd party vendor. They can’t see inside his code because he won’t let them and it just turned into a vicious circle of blame. I don’t want to state that NinjaTrader actually blamed the 3rd party indictor, but after exhaustive troubleshooting there was actually only one culprit left!
After being treated like a kid from the vendor, I dropped them like a stone. I moved on to a much better product and the crashes became more infrequent. So in the end, was it the 3rd party vendors code? More than likely…
If NinjaTrader can take the frontal assault on the chin and come up with fixes, then that is all we can ask them to do. Be vocal, send in your support requests and talk to them. They spend a lot of effort trying to support their product.
I just wish they would spend the same amount in draining the swamp of the EcoSystem.
--------------------------------------------------------
- Trade what you see. Invest in what you believe -
--------------------------------------------------------
quote from @NinjaTrader "We have some reports of users that have crosshair performance issues. We had made improvements a release or two ago which helped many of these users but not all. R13 is coming out within a week which includes additional performance improvements for the crosshair."
Hi @NinjaTrader when is R13 being released to everyone? Just ckd your website and still on 12
TIA
I don't have access to 8.0.13.0 (I assume as I am not on the 
).
