I've always been loyal to Ninja, but this is unacceptable

[sledge]

It looks like we were all moved to mirus zf feed which supports new zf.
Rithmic was left behind.

Sierra charts isn't even dealing with it.

Judging by the number of posts / threads in the forum I think it is safe to say that V.18 is unusable at this point. So, the only logical conclusion is the following: do whatever it takes to make V.17 available again ASAP, as most (all) Ninja & Zen users are currently being held hostage.

This is an extremely frustrating way to end the year and not very reassuring going forward.
How can such a mess even happen?

[RL8093]

For me the big issue here is that the non-functional upgrade was mandatory. The second major issue is that Ninja rolls out something like this without availability of support staff. I'm not sure how Ninja management thought this approach was acceptable.

I am not a beta tester and for mission-critical applications, I typically wait for some time and review comments/threads to ensure the upgrade performs as expected. Obviously this was not an option here.

For over 5 years, I have run both eSignal as well as Ninja. This past year, I decided that this level of redundancy was unnecessary - I killed my eSig account & purchased a Ninja lifetime license. Sadly, even if I go back to eSignal, since I have the lifetime license, they will not see me as a customer who left due to their negligence.

[bce111]

I have no complaints about the support staff, they do an incredible job and are always patient and helpful.

But someone higher up should take the rap for this. Version 18 has more holes than a golf course.

Agree. This is really bad. But I know the reps here are working hard to deal with all of this and I appreciate their efforts. What a mess though. I'm a computer guy and software development should provide the ability to use the working version until the "new" version is verified to be working. Especially where there is money involved, like in this case. This isn't like some browser bug.

[bce111]

For me the big issue here is that the non-functional upgrade was mandatory. The second major issue is that Ninja rolls out something like this without availability of support staff. I'm not sure how Ninja management thought this approach was acceptable.

I am not a beta tester and for mission-critical applications, I typically wait for some time and review comments/threads to ensure the upgrade performs as expected. Obviously this was not an option here.

For over 5 years, I have run both eSignal as well as Ninja. This past year, I decided that this level of redundancy was unnecessary - I killed my eSig account & purchased a Ninja lifetime license. Sadly, even if I go back to eSignal, since I have the lifetime license, they will not see me as a customer who left due to their negligence.

Agree. It's not our gig to be beta testers. But it seems we've been thrust into that role.

[laocoon]

So, my trading (or rather non-trading) day is over, but the question is: what will happen tomorrow?
Will V.18 be working tomorrow? (Assuming that I'll be able to connect to my account which still isn't the case?)

[simonkloot]

Infuriating

ATM strategies broken (out of bounds error), constant disconnects and downtime.

Totally unacceptable to force a mandatory software release on customers and treat them as beta testers with real money.

Ninjatrader are going to have to do a lot to repair customer relations. Seeing as I don't trust my platform to trade live any more, may as well check out some other platforms.

[Trader_55]

ATM strategies broken (out of bounds error), constant disconnects and downtime.

Totally unacceptable to force a mandatory software release on customers and treat them as beta testers with real money.

Ninjatrader are going to have to do a lot to repair customer relations. Seeing as I don't trust my platform to trade live any more, may as well check out some other platforms.

I may have to switch brokers / platforms as well, if this isn't solved quickly. The blame here appears to be threefold: Ninja, Mirus, and Zen-Fire. It is ridiculous that customers were not even informed of this mandatory switch until a few days before it happened, and during the holidays no less. This must have been in the works for months, and yet we were given no notice by anybody. And then we're all forced to instantly upgrade to a buggy piece of software with no option to roll-back. Whether the fault lies in the new Zen-Fire feed or in NT's version 18 software is irrelevant... it is obvious that not enough integration testing was done. This is starting to remind me of the Obamacare website debacle - some business executive idiot at a higher level clearly made a decision to go live no matter what by a certain date, despite what the technical guys were probably telling him/her, and this is the result. This is completely unprofessional and unacceptable on multiple levels, and just about the biggest fiasco one could imagine. If this isn't resolved very soon, this is going to hurt all Zen-Fire brokers in a serious way, and to some extent NT as well, certainly in the reputation department if nothing else.

[Maxwell]

I'm at NT 8 years and I always recommend NinjaTrader. Today I got lost in the market due to technical problems more than worth purchasing a full license NT .... Big disappointment ... Tomorrow is necessary to make it work. Historical data on servers TF, FDAX, DX, etc. are incomplete and obviously wrong ....

[VPTrader]

I also have ATMs that don't work in v18. I was just told by NT support to contact my broker. Mirus support is so overwhelmed, they are not answering the phone and the voice inbox is full. My response to NT support was "This is an issue others have experienced. These are existing ATMs that still work in the Sim. Assuming NT, Zen-fire and Mirus worked together and coordinated this upgrade and release, shouldn’t the three of you figure this issue out instead of each customer having to do the work? "

[ranger64]

Connection Problems

Same here, first several disconnects, where NT/Zenfire reconnected again by itself, now I can´t connect at all. Same as a couple of days ago, no error message, only the notice at the bottom of the control center: "Connecting - Zen-Fire", but nothing happens...

[glennts]

If you use Mirus this would be a good time to become familiar with Mirus Trader, their Zen_Fire web based platform. The charting is primitive but the DOM is better than NT's. No problem logging in today to Mirus Trader during the NT connect issues. Kinetick to drive NT's charting and Mirus Trader for the Zen-Fire feed and trade execution seems to be a good workaround until ver 18 gets ironed out. And your orders are all server side.

[willehm]

Good advice by @glennts for Mirus clients - it's the only safe way to trade today. However, I'm still having problems with rejected orders for UB and TF even in MirusTrader, which tells me there is an underlying problem with the Zen-Fire "upgrade".

[Trader_55]

If you use Mirus this would be a good time to become familiar with Mirus Trader, their Zen_Fire web based platform. The charting is primitive but the DOM is better than NT's. No problem logging in today to Mirus Trader during the NT connect issues. Kinetick to drive NT's charting and Mirus Trader for the Zen-Fire feed and trade execution seems to be a good workaround until ver 18 gets ironed out. I miss that chart trader.

What do you use to login to MirusTrader? I tried my Zen-fire credentials and that doesn't work, nor does the login I use for Dorman's web platform.

[laocoon]

If you use Mirus this would be a good time to become familiar with Mirus Trader, their Zen_Fire web based platform. The charting is primitive but the DOM is better than NT's. No problem logging in today to Mirus Trader during the NT connect issues. Kinetick to drive NT's charting and Mirus Trader for the Zen-Fire feed and trade execution seems to be a good workaround until ver 18 gets ironed out. And your orders are all server side.

Not a bad idea, but I guess you need to pay extra for a Kinetick RT Data subscription.

[willehm]

@Trader_55:
There is a third set of credentials that was created when your account was set up. The username is structured as [your_email_address].[FCM].