[FIXED B483] CMANO fails to start repeatedly AFTER prereq install

[Phoenix100]

Though there's only a few of us posted about this, Sunburn, I think it might be a significant problem for a significant number of buyers. At over 1,300 hits this thread is the second most hit (after 'performance') in the forum, I think.

[Diver369]

I am having the same issue. This was not a problem with v. 1.01. Just occurred with the new update. I doubt it's the graphic card. Only happened to me after getting version 1.02.

[Phoenix100]

I skipped 1.01, Diver, but I had this exact same problem with the initial release (version 1). That's why I stopped trying with it. I wonder if it was fixed for version 1.01, but reappeared for 1.02? Whatever it is. The strangest thing - but the thing which I had thought might provide clues for anyone who knew about these things - is that, as everyone has remarked, it starts perhaps 1 out of 3, or 1 out of 5 times. With no apparent change in how you run it. Something must be going on.

[BeastieDog]

I'm having the same issue. It is PC specific. Both of my units have Win7. My cheaper laptop meets minimum requirements and has prereqs, but fails to complete loading CMANO about 50% of the time. Second laptop has more "muscle" and does not have this problem.

[Dimitris]

ORIGINAL: Diver369
I am having the same issue. This was not a problem with v. 1.01. Just occurred with the new update. I doubt it's the graphic card. Only happened to me after getting version 1.02.

You went straight from v1.01 to v1.02? You did not download _any_ of the public releases we did in the meantime?

[Diver369]

Correct. I just waited for your upgrade pack to 1.02. So it has to be a something with v1.02. Worked perfectly with v.1.01. As everyone states it happens once in three tries. Very random. I can restart and everything seems to play okay. Just annoying.

[Diver369]

You can see the error messages I get on the two posts I started.

[rochrist]

What does "refused to run" mean? Please be more specific. Does it hang at a specific step? If yes, which one? If you kill the process in Task Manager, wait a few seconds and run it again, does it load?

Also, can you try running the game by directly clicking on the Command.exe file in the Command folder (instead of clicking on "PLAY" button on the Matrix launcher)? We've had reports that this solves many such problems.

In my case, refused to run means that it gets as far as the splash screen loading and then hangs (as far as I can tell) indefinitely. I also (as reported above) sometimes get a windows opening and closing in a flash, far to quickly to see what, if anything it means. Killing the process does not fix the issue, it still refuses to run. I've also tried running command.exe directly with the same result.

I also have a bog standard Nvidia card (GTS 250) with up to date drivers and I have virtually no problems with modern games.

[MorningDew]

Using Windows 8 (and 8.1), I've found that when this happens, I need to load task manager and Kill Command.exe under Apps. However, a new task then appears under Background Processes also named command.exe. After I kill that, I can usually restart. Sometimes it takes more than 1 attempt at this.

[Dimitris]

Alright, can everyone having such a problem please give this a try:
https://drive.google.com/file/d/0B205vp ... sp=sharing

(Backup your current Command.exe first!)

And let us know if it works for you.

Thanks!

[Phoenix100]

Many thanks for that, Sunburn. It means a lot that you're trying to help!

After backing up the 2 files I replaced them in the Cmano folder with your new ones. Same result. I started it four times (clicking directly on the app in the CMANO folder) before it worked. Comes up as DX fix #1. What I don't understand is why sometimes it CAN work. What is it that changes between my different attempts to start it, when I change nothing?

So, for me at least, that fix doesn't work.

[rochrist]

It's worked once for me. I'll try launching it a few more times and report those results.

[rochrist]

Ok, the first time I tried it, it worked. I tried to launch the game three more times after than and it hung each time. Something seems to change after that initial run. I'm going to extract fresh copies of the two files now and try it again to see if the behavior repeats itself.

[rochrist]

I'm getting inconsistent results. But mostly it's still not running. Sometimes if I delete the executable and extract fresh copies, it works, sometimes not.

[rochrist]

Just and additional FYI, below is what was reported in Action Center the last time it hung (I think it's the same as previously)


Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: E:\Matrix Games\Command Modern Air Naval Operations\Command.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: Command.exe
Application Version: 1.0.0.0
Application Timestamp: 52bc911b
Hang Signature: a148
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Hang Signature 1: a148adaf29d3e1f0310f8e95641102f6
Additional Hang Signature 2: 4147
Additional Hang Signature 3: 4147bf6f7496b01691902019ac9fecba
Additional Hang Signature 4: a148
Additional Hang Signature 5: a148adaf29d3e1f0310f8e95641102f6
Additional Hang Signature 6: 4147
Additional Hang Signature 7: 4147bf6f7496b01691902019ac9fecba

[rochrist]

I've now installed it on my laptop (also with a bog standard Nvidia card) running Windows 8 and it wseems to run properly.

[BeastieDog]

I uninstalled CMANO and re-installed with my original setup program and updated to 1.02. That solved my fail to load problem.

Edit: I spoke too soon. The problem reoccurs but not as often since I re-installed.

[Phoenix100]

Didn't solve mine, Dog, sadly.

But at least I can still get it to work. It's like cranking an engine! I have to start it roughly five times, it seems, each failed time closing it manually, and then, fifth time - she's alive!

[kneecaps]

I've experienced this also. Same symptoms.

[kneecaps]

There is clearly something going on here. I have experienced issues exactly like what you guys are describing and it seems to particularly affect 1.02.

I have tried this on three different machines and a Virtual machine even and it sometimes works fine on them all (even the VM!) but mostly demonstrates the same behaviour.

The machines i've tested on range from an i7 8gb machine with a GTX 460, an AMD machine with an ATI card, An i7 laptop with a Nvidia Quatro Card and a Core 2 Duo machine with integrated GFX (below spec I know, but command actually runs but demonstrates the same symptoms as on all the other machines).