[Logged] Game crashes after running Special Actions

[kk6pr]

I noticed this problem several times running the Silent Service: Lone Wolf scenario - and now it happens every time in the Creeping Death scenario.

After running the Game Special Action (VLF comms) the game suddenly exits upon continuing the simulation.

I am unable to use the scenarios Special Actions due to this problem.

[kk6pr]

It also happens for the Game Changer scenario when selecting the Special Action for picking which sub to play.

The 'exception log' lists 4 'invalid data type' and 2 'Nullable object must have a value' errors.

[Dragnaath]

Also happens in North Atlantic Shootout when performing downed pilot extraction.

[michaelm75au]

Can someone please supply a save where pressing the special action as the next step will crash it? This make tracking the issue quicker in case there is some other underlying issue before the SA.

Thanks

[kk6pr]

This message board doesn't allow me to post links, but if you send me an email I have a .zip file containing The Silent Service: Creeping Death scenario along will all of the log files.

After saving this file, I ran the Game/Special Operations/Raise The Satellite Antenna Mast function - and the game immediately shut down. After loading the game from this saved version however, it doesn't always crash immediately. Sometimes, you have to resume game play, run the Special Operation again (or the other one: Stream The VLF Antenna) - but it usually crashes eventually.

[pclaurent]

I myself am confronted with many, many CTDs, all occurring while executing LUA scripts. These crashes are difficult to reproduce systematically, and they seem to occur more or less randomly depending on the load of the system. The error occurs sometimes with a Special Command, sometimes with a script triggered on a time basis (every 5 seconds, for example).

I run CMO on a relatively slow PC, but this same PC was running CMANO without any problem. By dint of doing tests, I thought I detected some clues that could advance the resolution of the problem:

1. Some LUA functions seem more "vulnerable", eg. ScenEdit_GetUnit ({side = "x", unitname = "y"})
2. Crashes are more common when the scene contains many units and / or in "God's view" mode.
3. Clock synchronization seems to be problematic. The Time trigger sometimes works ... sometimes not (on the same machine, and depending on the complexity of the scenario). In some cases nothing happens when the time comes.
4. Temporal acceleration seems to make things worse.