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

[Phoenix100]

I have had this problem since the beginning too. Hangs on the splash screen, sometimes works, but less and less so. Works fine if I re-install it from scratch, but only once. So something happens after i first run it, I think. Once I had a momentary warning box about something going wrong with DX. But just once, so that might have been something else. It's updated to 1.02 now, same result. I can't play it at the moment because I can't get it to start (and have tried all these fixes listed above). As someone else said, it's the only game I've ever had this issue with. It's a modern spec computer, only a couple of years old, i5, 2.7, 8GB Ram, stacks of spare hdd, NVidia card. Very odd. Willing to send/post anything that may help resolve it.

[Dimitris]

Okay this is really wierd. Reproducible bugs are bad enough, but this is simply not happening here on multiple boxes.

Guys can you please check the event viewer to see if there is a crash log there when this happens? Thanks.

[RoryAndersonCDT]

MAybe try reinstalling videocard drivers?
I have an nvidia card too and I overclocked it too hard a couple of months ago and I (sometimes) get the same issue, where Command hangs on startup. I don't get it often, but I do still get it. I've always attributed issues like this to me just working my hardware too hard.

[Phoenix100]

Thanks for that suggestion, Baloogan, but I'm not overclocking anything. The card drivers are up to date. All other games working fine.

Sorry, Sunburn, but where do I find the event viewer?

[rochrist]

I'm having the same problems. Win7 64bit, pre-reqs installed manually, running as admin, tried deleting the ini file, it basically won't run at all now. It ran a couple of times at first, interspersed with failures, but now it seems that it won't run at all.

[mb4329]

I was having the same issues running Win7 64bit (also was unable to read the scenario descriptions when the game did load) and found it was my firewall software (COMODO). Once I added the Command folder as trusted folder the game ran fine. I am sure I could do a more nuanced approach, but didn't want to spend a lot of time trying to run the specific files and folders to ground.

Regards,
Merrick

[rochrist]

This is what shows in the action center log:

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: 52aec201
Hang Signature: 004e
Hang Type: 6144
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 004e32447ff3335430018dbe34cbfa9d
Additional Hang Signature 2: 38e6
Additional Hang Signature 3: 38e6e617cc9c25c76e89f6f998effc8c
Additional Hang Signature 4: 004e
Additional Hang Signature 5: 004e32447ff3335430018dbe34cbfa9d
Additional Hang Signature 6: 38e6
Additional Hang Signature 7: 38e6e617cc9c25c76e89f6f998effc8c

[rochrist]

So, I did a complete system scan, repaired some errors, installed the latest Nvidia drivers, rebooted the system, and it would then start. Twice. It then refused to run.

[Dimitris]

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.

[Phoenix100]

Tried running it like that, Sunburn. No difference. I have noticed that the process runs for quite some time after you close it (of course, I have to close it manually, in tasks, because it's hung at the flash screen) and so I also close the process. Start again. Or, even, reboot the machine, start again. Same thing. Gets as far as the little blue 'Command' screen and then something opens and immediately closes, just flashes up briefly, like it was about to open but couldn't (it takes usually 18 seconds for this to happen). Then we're stuck on the little blue Command box screen. Forever. I have to close it manually then.

[Phoenix100]

This is what happens, according to the event log:



I am updated to 1.02, by the way, despite the version info given in the event log.

[Phoenix100]

This is as far as I can get:

[Phoenix100]

So this time I got it to start. I ran it as admnin direct from the folder, using the application itself, no shortcut, as suggested. Great. I closed it. Tried again, exactly the same. Got this:



Something to do with direct 3d, obviously. But what? I have installed the prereqs manually.

[Phoenix100]

Back to square 1 now. I repeat the start up process as above and it just hangs at the blue box (as in 2 posts above) without any error messages.

It's very strange. I have no problems with any other games. Win 7, 64 bit.

Expensive failure, for me. A £90 game I can't even run consistently.

[Phoenix100]

This is my system:

[Phoenix100]

And the card:

[Dimitris]

Well, it looks like Command's map engine really doesn't like your graphics card.

Please get in touch with MG's customer services and request a refund, since obviously the software is not working satisfactory on your system.

Please accept our sincerest apologies for your troubles.

[Phoenix100]

Mmm. Thanks for that offer. But I wonder if your diagnosis is correct? Why would it not like a bog standard Nvidia card? Plus, how come it does work some of the time? Running it as above I got it to start this morning, approx. 50% of the time. What's annoying and frustrating is that I can't detect a pattern. Sometimes it starts, sometimes it doesn't. When it starts it loads no probs in about 4 seconds flat. Only once have I had the diagnostic suggesting a problem with the card. If there was a card problem then surely it just wouldn't work, full stop?

[Phoenix100]

Here it is running perfectly, for example. I had to launch it four times to get it to work, but it works;



With respect, Sunburn, but I don't think it can be a graphics card issue, no?

Is there not some way that something can be interrogated to say what exactly is hanging it, when it hangs on start?

[zacklaws]

I'm in exactly the same situation as Phoenix and cannot add anymore to what he states as his problem is 100% exactly what I am getting. My graphics card is an ATI Radeon HD 4800 and with up to date drivers. Deleting the Command.ini does not make a difference, it still wont start on most occasions, and on one occasion, reinstalled the Command.ini after the programe would not start, after copying it in a seperate location, and then deleting the original and on doing so, the programme started correctly.

I have checked my event viewer, but I notice it never gets logged. All I know is that if I cannot get past 15500k mark in task manager, it will not start, so I close it down and try again, and after about 3 attempts it will start.