Matrix Games Forums

CMO Crash on The Silent Service:

#5 Lone Wolf crashes badly when trying to establish any of the comms under 'Special Action' in the 'Game' drop-down.

It is interesting that all seems well before the clock is started. After the sim is running, these comms attempts are met with the game screen just leaving, sometimes with a bit of a pause, putting you back at the desktop as if the game never started.

Launch CMO again and the same things repeat.

The Silent Service folder used was there with the install.

CMANO is flawless on this scenario.

Chicken Kiev was properly playable for a bit then a few minutes in real time the crash happened again...

Yep had the exact same crash on the same scenario, the game just dumps you back to Windows...

Hey guys,

Sorry this is happening. My bet is it's due to how sides and contact sharing are handled in C:MO versus C:MANO.

We're still narrowing down the issue so a save file and description of what specefic steps preceded the crash would really help.

The ExceptionLog.txt file shows an index out of range...I'd send it but, as a 'Matrix Recruit' I'm not seeing how to attach a file...the file is in the logs directory.

Hi, I have ran the Lone Wolf scenario to try and get the CTD, for me it only happens the first time I go to periscope depth and raise the antenna...

If I reload the game from a save I made just before the crash it works normally after that.. weird eh?

Here is the save anyway, but I couldn't get the game to crash again after I reloaded...

All I had to do to get the crash is start the scenario, go to periscope depth and try to raise the antenna...

EDIT

Yep confirmed... After starting the scenario from fresh several times, it only happens (for me at least) when you raise the antenna for the 1st time...

I ran into the same crash with Lone Wolf when I streamed the VLF.

The first run was a CTD though the error did show up in the Windows event log

The second time I turned on debugging and repeated my previous step and got this in the Exception log. This time it didn't CTD, I guess the debugging is catching the exceptions.