I blew up NinjaTrader7...

[TheDawn]

curious what exactly you can not do in nt8 that you could in nt7? We using dynamic array with no issues. This is not Ninja but c# function.

I cannot remember anymore. I haven't used Ninja Trader for almost 10 years. I will have to go through my codes to find it but there was a function that I used perfectly fine in NT7 but they changed the coding of it in NT8 and I had to recode everything. And then they got rid of some functions and I had to scramble to find alternative functions that would do the same thing. I remembered I had to recode a lot of my codes when they switched to NT8.

 

[Overnight]

I cannot remember anymore. I haven't used Ninja Trader for almost 10 years. I will have to go through my codes to find it but there was a function that I used perfectly fine in NT7 but they changed the coding of it in NT8 and I had to recode everything. And then they got rid of some functions and I had to scramble to find alternative functions that would do the same thing. I remembered I had to recode a lot of my codes when they switched to NT8.

Yes, this was a known problem. They totally reworked their language, which they call "NinjaScript", from 7 to 8. I recall our programmer complaining of the same thing. All the custom indicators he wrote for NT7 over the years broke when they went NT8, and he managed to only get a few of them re-coded before Roger Felton retired and the programmer moved on.

 

[TheDawn]

Yes, this was a known problem. They totally reworked their language, which they call "NinjaScript", from 7 to 8. I recall our programmer complaining of the same thing. All the custom indicators he wrote for NT7 over the years broke when they went NT8, and he managed to only get a few of them re-coded before Roger Felton retired and the programmer moved on.

And the thing is they didn't even notify us of the potential changes that you may see in your codes when using NT8. It's like all of sudden you log into NT8, your strategies don't work anymore and you don't even know why or how because you didn't change anything. And then you have to debug and then compile section by section of the codes before finally finding out where was the problem. And then you had to research and research their guide to find out why. It was really frustrating.

 

[RedDuke]

And the thing is they didn't even notify us of the potential changes that you may see in your codes when using NT8. It's like all of sudden you log into NT8, your strategies don't work anymore and you don't even know why or how because you didn't change anything. And then you have to debug and then compile section by section of the codes before finally finding out where was the problem. And then you had to research and research their guide to find out why. It was really frustrating.

nt8 beta was out for a very long time with plenty of time, and nt7 still works. We decided to bite the bullet and rewrite due to gain in speed for backtests and other very useful features.

 

[Overnight]

...And then you have to debug and then compile section by section of the codes before finally finding out where was the problem. And then you had to research and research their guide to find out why. It was really frustrating.

Yes, that is the complaint I heard from the programmer. I did not envy his task. Wonder if they will break that NinjaScript stuff again when they go from 8 to 9.

 

[TheDawn]

nt8 beta was out for a very long time with plenty of time, and nt7 still works. We decided to bite the bullet and rewrite due to gain in speed for backtests and other very useful features.

Yes with announcements for the features and functions of the platform itself but they made no mention of any code changes with the C# platform which is what a large part of the users use to code strategies for auto trading.

 

[ph1l]

Yes, this was a known problem. They totally reworked their language, which they call "NinjaScript", from 7 to 8. I recall our programmer complaining of the same thing. All the custom indicators he wrote for NT7 over the years broke when they went NT8, and he managed to only get a few of them re-coded before Roger Felton retired and the programmer moved on.

These might help.
https://forum.ninjatrader.com/forum...ow-to-convert-nt7-indicator-to-nt8#post791817

What we suggest is that you first use the NinjaTrader8 indicator wizard to create the correct framework for the indicator. When using the wizard you will want to have the NT7 indicators plots and public properties in sight so that you can have the wizard recreate those for you. Reference: http://ninjatrader.com/support/helpG...?ns_wizard.htm

Once the frame work is created you can then copy the code from the OnBarUpdate() in NT7 to NT8. Then go through the code line by line and convert to the NT8 properties and methods by referring to the code breaking changes here: http://ninjatrader.com/support/helpG...ng_changes.htm We recommend giving that link a good read as it discusses what has changed so that you can be prepared for the conversion.

Alternatively, you might wish to employ a 3rd party coder to create the indicator for you. If this is of interest please let us know and we can provide references.

 

[RedDuke]

Yes with announcements for the features and functions of the platform itself but they made no mention of any code changes with the C# platform which is what a large part of the users use to code strategies for auto trading.

not true. Their docs were very clear about all code inconsistencies. There was/is a page which covers each code breaking change.

 

[TheDawn]

not true. Their docs were very clear about all code inconsistencies. There was/is a page which covers each code breaking change.

Their docs to you perhaps because maybe you are a 3rd-party vendor to them but to us regular users, not a word. I have never received anything from them (they have my email address as I have contacted their support numerous times) or seen anything ever published on their website or anywhere about any code changes. I had to dig and dig and dig, first on their forums, and then through their help guides to finally find out the changes and that was after hours and hours and hours of debugging and recompiling.