NT7 Release questions

[NinjaTrader_Dierk]

grid: infragistics
db: MS SQL Compact edition

[darckeen]

Will NT7 be able to use more memory then the 1.5Gb limit NT6.5 has?

[NinjaTrader_Ray]

Will NT7 be able to use more memory then the 1.5Gb limit NT6.5 has?

This is a windows limitation not a NinjaTrader limitation.

- The answer is no in 32-bit windows however, NT7 memory consumption is much better than 6.5 thus it will use less memory
- The answer is yes in 64-bit windows since NT7 will provide an optional native 64-bit version

[maxima]

could you please confirm that NT7 is going to provide spread charting.

I have looked on the page witn NT7 features list and can only see multiple TFs and instruments one under another on the same chart, but not spreads.

[NinjaTrader_Ray]

could you please confirm that NT7 is going to provide spread charting.

I have looked on the page witn NT7 features list and can only see multiple TFs and instruments one under another on the same chart, but not spreads.

NT7 will NOT support charting spreads as a chart style (OHLC, CandleStick) however, what can be done is to create a custom indicator that would plot the spread of two instruments.

[darckeen]

- The answer is yes in 64-bit windows since NT7 will provide an optional native 64-bit version

Whats the limit going to be on the 64-bit version?

[Speedie6]

grid: infragistics
db: MS SQL Compact edition

Thanks for the information. I've heard that DevExpress' grid is faster than Infragistics, but, I've never used Infragistics. But, I know that Infragistics is one of the market leaders.

I've never tried out MS SQL Compact, I guess I should have a look at it.

[Speedie6]

Whats the limit going to be on the 64-bit version?

If you got a 64 bit server OS, you'd have up to 2 terrabytes! Vista and Windows 7 home premium have 16 GB limits. the professional versions of vista 64 bit support up to 128 GB, while professional versions of Windows 7 64 bit will support 192 GB.

Perhaps NT7 won't be able to use all that, but, I don't see why not. But, it sounds like from their preliminary benchmarks, you won't need all that anyway.

The short answer is, although my guess is just that of an end user, but, it looks strongly like with 64 bit, you just won't have to worry about limits.

[cunparis]

What's the current release date now?? We've been waiting forever.

[BigDog008]

and still no update...

[JS999]

and still no update...

http://www.ninjatrader.com/webnew/NT7/NinjaTrader7.html

[TraderEyal]

The difference this time is...

- We are forecasting based on being nearly 100% complete with feature implementation so what is left is some more peformance profiling, testing and bug resolution
- The end of September is not a hard date, we hope to deliver prior to that but what I will do is provide updates every two weeks as to our status and adjust the target date if needed

Based on the latest update it looks like September is a no-go.

Also it will be a staggered release, as well as multiple "beta versions"........ ?

[richa61416]

As it stands today, our progress points to a beta release in aproximately 3 weeks times barring as usual, any onforseen circumstances. I will release more information on how we will rollout the fist beta versions... We for sure will release an initial version to our NinjaScript consultants and I hope we are able to do that in two weeks or so.


I hope this not another consultants and us regulars another 3 months like end of june. The updates on what is happening is not timely as hoped, and asking Ninja to promise something at the end of Sep would be silly.

3 weeks from now is the first week of October. I guess based on how these updates been coming we are looking at the 2nd week of October for a beta rollout to the public? Please prove me wrong.

[rt-trader]

With 13 days to go before the supposed NT7 beta release at the end of June, I asked some straightforward questions which started this thread. The answers provided released a torrent of frustration from NT users, exacerbated by an (initially) ongoing reluctance by Ninja staff to provide any details at all about NT7.

Later after clearly misjudging the mood of many users Ray released a comprehensive set of features which highlighted the extent of change and improvement contained within NT7.

Many (like me) were no doubt also encouraged to learn that

"The end of September is not a hard date, we hope to deliver prior to that but what I will do is provide updates every two weeks as to our status and adjust the target date if needed"

That several of the updates had to be 'pulled' by requests from this forum probably didnt trouble many but now, here we are yet again - 16 days before the end of the "not hard date" learning that 'not hard' looks likely to mean post the end of the quarter not before it.

Bearing in mind that a beta NT7 was originally slated for June 08, (or was it September 08, December 08, March 09, June 09?) we seem to be waiting for the unobtainable, undeliverable Nivana - perhaps Ninja should be renamed?

Anyway - after ranting - my question is this..

From the NT7 Features list it seems that there are some Indicator and/or Stragedy 'code breaking' changes that we will need to deal with -
.how many of those are there?
.will there be any automation for either detection or change?
.can we prepare for those changes ahead of time?

Thankyou

[NinjaTrader_Ray]

Anyway - after ranting - my question is this..

From the NT7 Features list it seems that there are some Indicator and/or Stragedy 'code breaking' changes that we will need to deal with -
.how many of those are there?
.will there be any automation for either detection or change?
.can we prepare for those changes ahead of time?

Thankyou

- We will publish a list of changes with the beta release
- Not automation is possible and detection will be the fact that your scripts would not compile thus providing relevant error codes
- Off the top of my head, here are a few changes

- volume changed from "int" to "long"
- Some or all Draw() methods have changes signature to accomodate new functionality
- DataSeries class default now only holds 256 values, you can get the 6.5 implementation of infinite values by using a different constructor