"Soft" Freezing or Perma-Pause

[aWildYetti]

Hello! Recently I have been encountering a problem across a number of scenarios where my game suddenly acts as if it is "paused". When I hit resume (at any speed) the game time and activity remains paused but I can fully manipulate the map, utilize the menus and drop downs, click on units, etc.

This actually started happening before the 64 bit update. I rolled back my game to the 32 bit update and I am still having the issue. With most scenarios/saves that have the issue, I am able to simply exit the game and reload the save and it will run past the "pause point". However with the attached save file it pause-freezes every time in nearly the same spot (roughly 1349Z-1354Z, OCT 5 2008).

I have attached the ExceptionLog & DxDiag report. I attached the save file as .txt (I wasnt sure on how to attach the .SAVE file since it wouldnt accept the file to upload here as a .SAVE).

Edit: Added Fixed Exception Log

[Nikel]

Just in case is useful to the devs.

The exception logs provide more information if you check the box Log debug information to file in General options/General dialog window.

Do that, restart the game and then proceed to the pause you note, then go to the exception log created and post it.

[thewood1]

I got the same result from your save. But starting the scenario from scratch I was able to get 24 hours in with no issues until I stopped it.

[aWildYetti]

I added the corrected exception log.

I ran it testing different variables, such as deleting all the missions, restricted areas, RPs, etc.

I ran it by just now, not changing anything except running it at 2x Max and more zoomed out and it did *not* soft freeze.

Additionally, while it is soft frozen/perma-paused, if I attempt to save it simply hard freezes and refuses to end task through the task manager.

[blu3s]

Hi aWildYetti

Yes, running at in double flame speed doesnn't freeze the scen. On my computer the freezing times are totally random

Logged: 0015233

[aWildYetti]

Tried a second scenario, and the same thing is happening. Again, the times may be random but my freezing is occurring around 0628Z in this scenario. I attached the exception log and the save for the problem with the second scenario. Hopefully it gives some additional data points to investigate.

I'm pretty sure that these freezes (at first in frequent) occurred with the Aug 04 patch (v1.05.1307.19) and now with the Aug 08 update (both 64 and 32 bit versions) it seems to happen with every scenario.

Is it possible for me to rollback and play a version before the 04 August updates? At least until there is a fix for my particular issue.

Thanks again!

[blu3s]

Hi aWildYetti thank you for the update.

I'm afraid that via steam the two possible branchs are 1307.19 and 1328.8.

If you are using Matrix installation, you can install from the download page the Installer v1.05.1307 and then upload it to the 1307.18 version

[aWildYetti]

Unfortunately I just have it though steam. However I did just notice that this recent post is seemingly the exact same issue I am having myself.

I have tried a few other solutions (toggling some game options, using my laptop screen instead of a second monitor, etc) and my games keep freezing on most scenarios. Again, thanks!

[Geoffropi]

Fixed for the next build.

Also thank you for providing multiple exception logs from different occurrences of the bug, this is an excellent way of cross-checking an issue.

[aWildYetti]

Glad I could help! Just curious, as for the problem - until the next build is there a way to minimize the chance of this happening? If not I understand, thanks you!

[Dogmatiker82]

Hello,
it seems, I'm suffering from the same problem since a little bit longer and it still persists after the recent updates...after a while of playing (any scenario) the 'game-time' freezes and doesn't let it restart...
Tried to run the game as an Administrator (as I bought it on steam: ran the Steam-Application as Administrator...) and installed it on various drives...same result.
Would like to add an save-file, but the *.scen-extension isn't accepted...

Looking forward for support.

Thx.

[thewood1]

Just for future reference, you have to zip the file for it to be uploaded. jpgs can load directly.

[Dogmatiker82]

Zipped file...

Autosave.zip

(935.61 KiB) Downloaded 22 times

Zipped file...

[thewood1]

Just a data point...

I run your autosave and it never really runs. Its just like you, and others, have pointed out. If I run Op Brass Drum from the start, It runs all the way through fine.

[Geoffropi]

Glad I could help! Just curious, as for the problem - until the next build is there a way to minimize the chance of this happening? If not I understand, thanks you!

I would willingly, but I am afraid the issue is too intrinsically unpredictable to provide a way to trick the simulation.

Also to give some reference for further test, fixed for the next build would mean here fixed for 1328.8 +1, thus 1328.9

[Dogmatiker82]

Just a data point...

I run your autosave and it never really runs. Its just like you, and others, have pointed out. If I run Op Brass Drum from the start, It runs all the way through fine.

Very strange thing. What could that mean? I have no idea...
I reinstalled the game several times. Sometimes it works better for a time (with older save-files from the cloud), sometimes the game in the save-files stays 'frozen'...looks like for me as the 'save-files' got 'damaged' in some way, but no idea how this may happen or I could avoid - I'm no programmer or something like that.

[thewood1]

The newer DX11 support is going to make the GPU and its drivers much important to pay attention to. The old DX9 base was much more forgiving of older cards. So I suspect something in in the directx is causing the issue. Seems like the devs have worked it out.

[Dogmatiker82]

The newer DX11 support is going to make the GPU and its drivers much important to pay attention to. The old DX9 base was much more forgiving of older cards. So I suspect something in in the directx is causing the issue. Seems like the devs have worked it out.

Recently nothing changes. I had big hopes in that 64-bit-update, but nope. As you mention this, I changed to a new GPU in first half of the year (GTX 1060 --> RTX 3060), but can't say for sure if the problems started with the new GPU.

[aWildYetti]

Glad I could help! Just curious, as for the problem - until the next build is there a way to minimize the chance of this happening? If not I understand, thanks you!

I would willingly, but I am afraid the issue is too intrinsically unpredictable to provide a way to trick the simulation.

Also to give some reference for further test, fixed for the next build would mean here fixed for 1328.8 +1, thus 1328.9

Is the 1328.9 Build going to be the one associated with the upcoming Operation Desert Falcon beta?