I couldn't play the 1.5 beta and I still can't play the 1.5 release. A crash occurs when trying to launch the game.
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
You probably have this issue:
forum.paradoxplaza.com
Let us know if setting Victoria3.exe to only run on your pCores with Affinity helps you, thanks.
Inconsistent in-game crash on gametime resume
Hi everybody, I've got a weird behavior with Imperator: Rome after upgrading my computer to Windows 11. I have updated all drivers & firmware, performed a clean re-install of the game (discarding my old imperator profile, verifying game files...
Let us know if setting Victoria3.exe to only run on your pCores with Affinity helps you, thanks.
I have set affinity via the shortcut properties. I tried to run on one core - the boot screen lasted longer than usual, but then there was a crash anyway. I tried all the cores, it crashes anyway. Maybe I'm doing something wrong?
Hard to tell, but 1 core is definitely too few! restricting it to 6 - the FIRST 6! - ought to do it okay.
My game has started! I don’t know if this will help anyone or not, but a completely different method helped me. I deleted all folders and files associated with Paradox Launcher. I also deleted the savedgames and shadercache folder in the My Documents folder. Checked the integrity of the game files. Steam automatically installed Paradox Launcher, and to my surprise the game started.
No manipulation of affinity was useful. But thanks for your help, without your motivation I still would not have played Victoria 3.
I see the devs are saying the CPU issue was fixed in the 1.5 patches
forum.paradoxplaza.com
So it looks like I'll have to take a different approach henceforth!
Victoria 3 | 12th/13th/14th Generation Intel Processors
Hello all! An update, 12th and 13th Generation Intel Processors are related to a Crash to Desktop (CTD) happening frequently, this is related to architecture changes by Intel and specifically E-cores. We are working with Intel to address these...
So it looks like I'll have to take a different approach henceforth!