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)
Yea i did. It mainly an update on the trace files so they can pinpoint problems better, from what i understand.
I don't have 3rd party indicators. So far im just testing the CQG feed, and trying the fix the DOM problem ive been having.
How do you know it works great, have you already tried to decompile it? I have posted an CLISecure obfuscated assembly yesterday in the Salamander thread.
this (attached pic) looks good. but ofcourse, everything can be decompiled. i myself has never put my hands on reverse engineering/hacking, nor qualified to do so, so cant say much how secure its truely is. the NT guys must have done their homework. maybe one should hire a hacker or post a protected assembly in a hackers forum to get a rough idea.
I have installed NinjaTrader 7.0.1000.6 on my PC and there is a new bug, which was introduced with this release, which prevents some of the indicators from working correctly.
Affected are indicators that load daily data for use with intraday charts. This includes
-> the SessionPivots indicators
-> the FibonacciZones indicator
-> indicators which add daily bars via the Add() method
The bug can be only observed with specific session templates, so not everybody will be affected. I have had problems with my default EUREX template, which prevented the loading of daily data.
NinjaTrader support has been very helpful to identify and confirm the bug. It should be fixed with the next release.
Nevertheless I will be downgrading to NT 7.0.1000.5, as the SessionPivots and FibonacciZones indicators are affected. Also I suggest not to upgrade to NT 7.0.1000.6, if you use these indicators.
I feel your pain. I felt so bad for you... I contacted NT Support about your issues. They said you were the only customer they had that claimed to have this problem and wanted to know what you had done that you weren't telling anyone and that you just liked to complain...
But V.06 does fix the bug that caused "Connection Lost" using Zenfire... even though it wasn't a bug in v.05 ... thank Gawd they fixed it anyway....
"Not intended to be a factual statement" John Kyle Senator Arizona
Disclaimer: This post does not represent the view point the owners, managers, or moderators of this web site and is not intended as a slam against any moderator, board member, any banned former members whose name we dare not say, any other living person, any recently living person or any person or persons whose status we are not sure of and especially not for any platform vendor with a questionable product and a pit bull lawyer. This post is meant purely for entertainment and should not be confused with a real thought. Nor should I be held responsible for feeble attempts at humor at your expense since everyone on the board adores you.
I'm just a simple man trading a simple plan.
My daddy always said, "Every day above ground is a good day!"
Would like to know why you contact NinjaTrader about my issues. I have contacted them, because I had detected a bug, which needs to be fixed.
You contacted them because you like to complain, effectively stealing their time?
I have done extensive tests and coded two custom indicators to detect the exact conditions under which the bug occurs. It is a triple session template, which I use for EUREX futures that interferes with the (synchronous or asynchronous) loading of daily data. There are only two indicators affected, if they are used on a specific template in DailyBars mode. Unfortunately I have coded these indicators, distributed them and use them personally.
Again, support has called me back and has been helpful, so don't worry.
