While I don't upgrade to the latest/greatest TWS release unless a specific bug I've experienced has been fixed or there is a new feature that I want to utilize, let me just state the MotiveWave v6.6.9 Standard Edition (i.e., my licensed edition) with TWS 981.3i has NO PROBLEMS WHATSOEVER bringing up the ZN, ZF, ZT or for that matter, the ZF futures charts from the Chicago Board of Trade. Currently, MotiveWave does have a problem with not listing the COMEX Exchange name that IB will require on the metal futures in the coming weeks. I sent them an e-mail last week so they'll simply add it to an Exchange drop-down list and that will be that. What's not been emphasized in any ET posts that I've read is that IB still supports client connections to their TWS version going way back to their very very old server protocols. You can see evidence of this in the open source code they publish for a client's interaction with receive and response messages. There's lot of if/then/else code to decide what data fields are available, depending upon what client version you've identified in the initial client-server protocol exchange to setup the connection. Some companies will play around with an auto-login feature to the TWS and to do this they usually search for the name of the login TWS Windows title in order to enter in the information. For example, I'm guessing that NinjaTrader is probably doing this and that's why older versions may suddenly stop working with a new TWS release because IB changed the Windows title name of its login window. Other companies, like Amibroker, have ALWAYS worked with connecting to the TWS for data interchange simply because the older client protocol still works to this day, no matter what additions IB makes to the TWS. A perfect example of this is Amibroker's IB.dll plugin. It's most definitely using a very old TWS client protocol vs today's.