GAME INFORMATION
- GAME BUILD #: 101.102.52940.0 (#118476) 15050943
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 10
ISSUE EXPERIENCED
Sometimes when enter/restart a campaign scenario, the main gameplay screen is a blank black screen, or freezes at the last moment of LAST GAME I played. However, everything except the screen (UI, audio, the actual gameplay part, etc) all function as usual. Then If click the gameplay screen, the game software will crash.
This is kind of hard to explain for me (sorry for poor english), so please see the screenshot below.
It can also happen when the game software is freshly booted with no game played; It can also happen when entering a different campaign scenario from the last game.
I only play the official campaign so I can’t tell if it happens in other modes as well.
FREQUENCY OF ISSUE
- Less than 25% of the time / matches I play (RARELY)
It happened more than 25% at some point, the situation improved after I reinstalled the game, verified the game file, and rebooted my PC, not sure which one helped the most.
REPRODUCTION STEPS
- Play any campaign
- Quit and enter a campaign scenario again / or restart
- Hope you’re lucky(or unlucky)
Again, since I only play the official campaign, I can’t tell if this happens in other modes
EXPECTED RESULT
The gameplay screen works as usual and clicking the screen should not cause the game software to crash.
IMAGE
So what happened is this picture:
- I was about to lose in a campaign scenario
- I restarted the game by clicking the restart button on the top right menu
- The new game started, but the gameplay screen freeze at the last moment of the last game.
- Everything except the gameplay screen is functioning: the minimap is live and showing units moving and sounds of unit fighting can be heard (proving the actual gameplay part is fine) but it does not match what happens in the main screen, Emperor’s dialogue is playing as usual, the timer works as intended, and the pop count is correct. All is fine except for the main screen is freezing.
This bug happens multiple times but this screenshot is all I got for now. I might update this post if I manage to get more.