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)
There is no perfect software package. All of them have bugs. The most efficient and the most offensive way to deal with bugs is to admit that they exist, create a ticket and try to fix them. If I look at the Release Notes for Release 7, there are 36 bugs that were fixed. I think that - with the exception of 3 - all of them were minor bugs, which affected only a small number of users. I had identified some of them.
The NinjaTrader support team is very helpful in general, and most of the problems are treated in a way that I expect. However, I also have a few problems, for which a solution has been postponed. Let us name some here (non-exhaustive):
-> The heuristics used for (multi-session) session templates will not always identify the first session of the trading day correctly.
-> If your primary series uses such a session template, daily data will not always be inserted at the right position
-> The NinjaScript method GetMedian() is flawed (Help file has been adapted to show how to correctly use it).
Why do these things not get fixed immediately?
The first two points are linked to the architecture of NinjaTrader. To fix this, you would need to redesign the session manager, the data base for master data and others. Very few users actually have ever tried to put on a session template that runs into the problem. I am one of those few. The second point is linked to the first, it is also a question of design.
The third point would require a code breaking change, as GetMedian() would work in a different way after the fix. This is not possible, as some third party developers may have relied on that method as it works. A code breaking change would produce false results with older indicators or strategies.
Could you please specify, which bug you have reported. Is it something very important that can be easily fixed?
I agree they learnt the lessons from that (although I've seen no signs that the level of testing lesson has been learnt)
I think my worry is just that the focus will be on new clients, charts, kinetick, new brokers and third parties for a long time before some of the professional enhancements get a chance.
-> it relates to the formatting of the date on the cross-hair
-> it only occurs on daily charts (as intraday charts do not display the date)
-> it only affects a few non-US customers ( I am located in Europe and it is correctly displayed on my 2 machines)
I could not have invented something of a lesser importance.The problem of this problem can be its reproducability, as it may depend on some specific country settings of your PC installation, it may even depend on your operating system. So it is precisely the bug that would have lowest priority of all. Difficult to reproduce, only affecting few customers using NinjaTrader for daily charting (most of those customers are non-paying customers), not really important, only occuring for specific country settings in combination with a specific Windows/.Net install.
Not something that I would qualify as very annoying, but rather as neglectable for my daily trading. Nevertheless, I would have reported the problem.
All very fair points, and I did point out it wasn't crucial and may be not that important to people. I would also point out for balance that 1) it doesn't just occur on daily charts, 2) I have no indication from Ninja that it's not reproducable, 3) as far as I knew it affects all non-US locales, 4) being a low priority easy fix, I would probably have given it to a new developer, or someone changing that bit of code anyway - but hey, I agree it's very low priority, 5) you may not find it annoying, but I do, and a small part of that is there are previous more serious bugs where it was also easy to get the impression that Ninja consider non-US users as somewhat lower priority
You're comment (no freezing) is on latest version NT 7.0.1000.7 ?
What sort of load do you put on NT ?
ie: I have only 4 workspaces with 4 charts per workspace.
I've reduced all charts down to 1 day and all indiators (except Gom) to calculate on bar close "true".
Have, one by one, taken off each indicator.
Non of this is helping.
Gets even worse (if that's possible) with "chart trader" open.
Yes I've been through all the usual "cleaning" things and everything (.NET) is up to date thx.
'll upgrade to latest NTV 7.0.1000.7 but it's getting very frustrating having these issues and having to go through these upgrades so regularly.
thx
PS: my pc cpu seldom goes much above 30 % , and is mostly around the 10 to 20 %, so it's not my pc (I presume?) .
Internet my end seems to all be fine and running well.
NT support said there was an upgrade to CQG adapter in latest 7 release, so perhaps that was the/an issue,
although I'm waiting to do the NT upgrade until AH.
I noticed your posts elsewhere on this, many thanks, and have since taken your advice and made sure display update is set at 0.5.
This may well be the issue. I've only ever made some colour additions to a few indicators.
Trouble, is, not being knowledgeable with NT scripting, I can only presume I've done things correct if the indicator complies ok. I'm sure this isn't always the case, but I have no other way of knowing.
Not withstanding that those were on charts and everything was running fine. The freezing seems to kick in add hock,
but always in fast markets. (which is where you'll be effected by this I guess).
Last time, as a solution, I deleted the Workspace.xml. There was an immediate improvement. Like new.
Seemed NT was opening multiply copies of the workspaces NT originally opened up with.
Gomi mentioned somewhere that he had got his code down to the longest line being that to draw the NT candle.
I guess that means it's about as well written as he could make it.
Just to add, seems the problem is at it's severest in fast markets, so I have to wait for those times to see if I cured the problem.
It's not easy to get to the bottom of the issue, in other words.
Very much appreciate the suggestions you made.
Thanks
