Freezeups while playing

[Arentak]

I'm playing with 1.33. Occasionally, I get semi-repeatable "freezeups" where I have to close the game and re-open it and it often freezes again once it starts doing that. A new game will not freeze up.

Since the game isn't "crashing" I don't get any crash logs. I was really shooting for my "learn the game" achievement, but its hard to get through the 1900's with the freezeups. The mouse just won't respond in the application, and it stays like below, except if I click enough in the window it goes semi-white as windows apps sometimes do.

My task manager shows relatively normal CPU/Memory usage

It doesn't seem like a memory leak type thing since I'm doing fine on memory. Any thoughts on what to try?

 

[AndrewT]

Is this just in this one campaign? Or any one you play now?

Any mods involved?

Right click on Victoria3.exe , properties, compatibility. Tick "disable fullScreen optimisations" untick every other box in that dialog, Apply and exit.
Then in the launcher Game Settings menu, select fullScreen display mode, Vsync off, cap refresh rate at 60.


If those don't help:
DXDIAG is a program you run from the Windows search box on the task bar. After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here.

Please attach here your Documents/Paradox Interactive/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log , exceptions.log

 

[jpd]

A freeze like the one you describe indicates a coding problem of some kind.

A significant amount of CPU time spent, while task manager complains about the application not responding indicates the application is very busy with some sort of internal processing which doesn't terminate as it should. Therefore, the application doesn't get back to responding to mouse and keyboard input, and thus gives the impression of being frozen.

Another strong indicator is the fact that if you kill the application and restart it using (presumably) the most recent autosave, the same (or similar) trigger to enter the never ending loop in the code is encountered immediately, or shortly afterwards, and the game appears frozen again.

I would suggest that, if you have an autosave that demonstrates this problem, you file a bug report in the bug reporting subforum. A coding error of this type is beyond the capabilities of tech support to fix.