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)
I upgraded to Beta 22 today, after receiving notification from MirusFutures that I MUST upgrade to beta 22 AND perform an Instrument RESET before attempting to trade, after Sunday, October 3, 2010, and had a few problems.
1. Ninja would not load, saying I had indicators with "problems" that would not compile.
2. After careful investigation, it seems there is a problem (now) in beta 22 that did not exist in beta 20 with:
a.) DailyATR (specifically, this line of code: if (currentDate != Bars.GetSessionDate(Time[0])))
b.) futures.io (formerly BMT)EnvelopeExpansion (specifically, this line of code: double _100 = DailyATR(DailyATRLength)[0] / 2; )
I moved these 2 indicators to my desktop, forced a recompile of all remaining indicators and now it's working fine.
Just thought I'd post this in case anyone else has DailyATR or futures.io (formerly BMT)EnvelopeExpansion in their indicator library.
3. IMPORTANT TO ANYONE USING MEDIANRENKO.
Upon installing MedianRenko, it puts the "bar type" into the "Indicator" folder. To remedy them NOT showing up in the dataseries list of bar types in beta 22, you MUST drag MedianRenko OUT of your INDICATOR folder & drop it into the TYPE folder. (NinjaTrader7/bin/custom/type)
Restart NinjaTrader and then the bar type shows up in the DataSeries list of bar types, as before.
I'll re-post if anything else odd shows up.
After all, it's what you learn AFTER you know it all, that counts!
Code breaking changes were introduced with NT 7.0.0.21, because the prior methods were flawed. See NT release notes for NT 7.0.0.21 or this post from September 13:
GetSessionBar -> should not be used any longer, returns false values for some templates, confuses session and day
GetSessionDate -> cannot be used any longer, returned …
My fault, because I had detected the bug that the old methods produced false dates under various circumstances.
For the time being I try to avoid the old methods (not working for NT 7.0.0.21 and later) and the new methods (not working for NT 7.0.0.19 and prior) as well.
Yea, that's pretty ambiguous. Do you understand it? I just overwrote my build 22 and I seem to be able to log in without any problems. Maybe I don't have an unfiltered bid/ask data provider (Mirus) ?
My understanding from what has been posted here on futures.io (formerly BMT) is that NT was connecting to certain Zen servers that were filtering data, unbeknownst to them. They've now corrected that, so Zen Fire data is no longer going to be filtered.
But, my understanding was this applies only to the historical data they collected, and not what was actually transmitted Live to a client. However, I don't use NT or Zen any more, so really didn't dig deeper. My assumption would seem to be wrong -- and the filtered data was being sent to the clients, just based on them stating you have to re-create your account for the new server to take effect.
Just reading the thread on NT and Ray has posted that they have changed the connect point to unfiltered. Reading between the lines, NT didn't know data was being filtered and someone at Zenfire just got yelled out.
+10 brownie points to NT folk if I have that right.
Edit : and I am glad to see the RC1 designation finally. I got told recently November "should" be the NT7 release month so seeing RC1 gives me hope.
