Cao Cao 5 - crash loading save at some point

:play_button: GAME INFORMATION

  • GAME BUILD #: 143421
  • GAME PLATFORM: Microsoft Store
  • OPERATING SYSTEM: Windows 10

:play_button: ISSUE EXPERIENCED

Playing the last scenario of Cao Cao campaign, at some point, loading a game saved from this scenario cause the game to crash.
I have been able to reload the scenario from a previous state up to a certain point. After that point trying to loading cause the game to become unresponsive and crash (music and sound effects goes on, the fireflies on the loading screen are freezed and the game won’t load).
I don’t know if the point at which loading starts to cause crash is related to a certain amount of time or to an event occuring during the scenario In this case, it seems that the corrupted saves all occured during the 10 min when you have to hold fortifications to break the alliance.
Manual save and autosave are corrupted the same way.

:play_button: FREQUENCY OF ISSUE

  • 100% of the time I play (ALWAYS) this scenario

:play_button: REPRODUCTION STEPS

Here’s the steps to reproduce the issue:

  1. Play Cao Cao fifth scenario
  2. Save the game during The 10 minutes timer to break the alliance
  3. Try to load the previously saved game

:play_button: GAME FILES (SAVE / RECORDING)

-AUTOSAVE-.aoe2spgame (1.7 MB)

1 Like

same issue, made a bug report too:

Cacao? 20 characters

So I can for sure say that there has to be a trigger point or something which corrupts the scenario onward. I’ve cleared the entire map except for 1 Liu Bei’s castle (not really hard), and damaged that castle so that 1 treb volley would destroy it. Then I took my time and I researched every tech, deleted some units so that I could make the 8 transports, then sent them to my ally and waited for him to appear - In other words, I made sure I “waited” long enough, then saved the game, and then finished the volley. Loading that specific save file still made the game crash.

The last time I could load a save was from about 15 minutes 55 seconds gametime, and a save from 69 minutes (nice) is corrupted