Matrix Games Forums

Save file and exception log attached. This is the Last Stand scenario from the Steam Workshop. Playing from the save file on 1x speed for about 10-20 seconds consistently crashes my game, version 1.04.114734. I started this scenario on an older version of CMO, then I resumed it today after Steam updated the game automatically.

I loaded your file directly because I wasn't sure where to put the autosave.

That works without problems here.

regards

Hmmm... that's weird. You're running the same version, I'm assuming? That scenario crashes every single time after about 15 seconds for me. There is no visible error reported- the game just kills itself.

I haven't tried reinstalling the game yet but that's probably next on my list of troubleshooting steps.

That zip file includes the exception log which might have some hints.

Actually, I don't think the exception log includes the fatal problem that actually killed the game. There are a lot of errors contained in the log but they all seem to happen prior to the crash.

When I load the scen file in the editor, I see the datbase is a v480. The current DB seems to be v491. Have you tried updgrading to v491?

I am running game version 1147.34.

And, when upgrading, lots of loadouts are missing from the new DB:

[font="Courier New"]Scenario Last Stand 2022: WARNING - ONE OR MORE AIRCRAFT FEATURED IN THIS SCENARIO CARRY A LOADOUT THAT IS NOT IN THE AIRCRAFT'S LOADOUT LIST.
PLATFORMS ARE AS FOLLOWS:
Aircraft: MiG-29 Fulcrum A, Callsign: Hornet #12, DBID: 842, Loadout: A/A: AA-10 Alamo A [R-27R], DBID: 26809 (Parked on Single-Unit Airfield (3x 3201-4000m Runways))...[/font]

This perhaps causes a problem with the new green signatures highlighting in 1147.34:

A further DB-viewer improvement: The RCS signatures of aircraft are now shown per-loadout in addition to their “clean” ones. This makes it easier to understand how external stores on an aircraft are affecting RCS and the subsequent effect in detection range by different threat radars.

Oh yeah, I forgot about the DB update. I was indeed on v480, and also experienced those errors you mentioned trying to upgrade. I guess the scenario owner needs to update it properly...but even so I would still consider it a bug that CMO crashes without warning or error when it encounters a DB problem- if that is indeed what is causing the crash.

Strange that I cannot reproduce the issue. Perhaps its a setting/game option thing. Maybe post a screenshot of your config and Game settings.

But the scneario designer definitely needs to update.

Now that's indeed a rarity. There is an error alright, but it can only happen if an aircraft is using an onboard terminal-SARH seeker.... which never happens _except_ in this version of the DB3K by mistake.

Fixed in-code for the next update, and as temporary workaround please update the scenario to a more recent DB.