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)
After I made the switch from ZenFire to CQG and re-installed the upgraded version of 7.0.1000.2, NT began to freeze up when I right clicked on indicators. I was forced to exit NT via the task manager. The problem was rectified immediately after I deleted the jtEconNews indicator per Fat Tails' recommendation.
Actually that has nothing to do with it what so ever... simply doesn't work that way. I'd try to explain it but you need to be a programmer to understand so you'll have to trust me. The URL is just a string. The problem, based on what you are reporting, has more to do with the code actually trying to open a connection to the FF website. Again. can't tell you why it crashes your machine.
I did fire up a xpsp3 image and did a clean install of the the latest beta and can NOT reproduce this issue. If there are others running the same config as yours and not experiencing this problem then I would suggest that the issue lies on your machine.
p.s. - as of this time, the FF site is still not available.
I had started the NinjaTrader suport forum thread, before I knew that the jtEconNews2a indicator caused the crashes. Otherwise, I would have directly contacted you via this thread. By the way it took me over 2 hours to find the culprit. So please don't pretend now that your indicator is working correctly. This is not the case.
NinjaTrader Ryan Olson could also reproduce the freeze.
Both TigerTrader and Ryan did not use my machine. I also have a second install of NinjaTrader running on my notebook with a Vista OS. Same problem, so this is already four different machines that broke down.
I use .NET Framework 3.5 SP1 (KB2416473) with hotfixes KB953595, KB958484 and update KB963707.
I also have a Language Pack SP1 -DEU, but this should not cause the problem, as the two other machines that have confirmed the problem are both US machines.
Now this is no problem for me, I have TEMPORARILY BANNED the indicator. The hard bit was to find where the trouble came from that had corrupted my NT installation.
Typically not an issue. This is more of a warning that future versions of the runtime may not support it. As long as it compiles you should be okay.
I wish that I could recreate it but alas can not. If you have programming skills then I would suggest debugging with Visual Studio (Express is free). What I would do is remove the indicators completely. Then fire up NT... create a new indicator... copy the code from this indicator into the new indicator. Set the Debug option on and then compile it. Then from Visual Studio, debug the NinjaTrader process, open the indicator file, set a break point at each indicator method. Then load the indicator on the chart and step through the code until you identify the problem area.
(actually, why not just download the addin version and call it day?)
The hard bit was to find where the trouble came from that had corrupted my NT installation.