Okay, this sounds peculiar.
I've been having CTD issues since I got back to Vic3 in 1.5. They happen on autosaving in wartime, autosaving in peacetime, when I zoom in or out too quick (that goddamn mapmode transition), when I change the construction queue order by the end of the week, sometimes even when the game is just merrily running. It's gotten to the point I dread CTDs while playing Rimworld or lol Pokemon Go, because I grown accustomed to it in Vic3.
Just a couple hours ago, my Roman Republic game crashed in peacetime, as usual. But now the game crashes whenever I try to load the savefile. I can't even send a report on Paradox Crash Reporter, it says "the upload failed for an unknown reason".
So I deleted shadercache, turned VSync off, yadda yadda. I tried loading it again, and this time it worked! But then I unpaused and it crashed after two days. Note, it crashed in less than half a week. There literally was no time for anything to happen, it was peacetime, even.
So I deleted shadercache etc etc again and did a clean install. The only thing I preserved was an old save file from a couple years prior, which I had kept saved elsewhere in my computer (I make a backup whenever I try out a risky diploplay). All reinstalled, I tried again with this old save.
It crashed on load. Again.
I mean. Literally how. It's a different save file, it's a clean install, there's no cache lying around.
Also, if it matters, I play on speed 5 90% of the time, but I've had the rare CTD on speed 4 too. I've also been playing with VTM mod this week, which weirdly enough reduced the number of CTDs I had until this save-breaking one.
Specs:
Windows 10 64-bit
No Windows Defender antivirus
NVIDIA GTX 1060 3GB
AMD Ryzen 5 1600 Six-Core Processor 3.20 GHz
16.0 GB RAM
Files:
papal_states_ironman, from my backup
pdx_settings.json, from Documents\Paradox Interactive\Victoria3\
system.log and error.log, from Documents\Paradox Interactive\Victoria3\logs\
exception.txt, from Documents\Paradox Interactive\Victoria 3\crashes\victoria3_20240206_022223\
DxDiag log, from literally three minutes ago.
I've been having CTD issues since I got back to Vic3 in 1.5. They happen on autosaving in wartime, autosaving in peacetime, when I zoom in or out too quick (that goddamn mapmode transition), when I change the construction queue order by the end of the week, sometimes even when the game is just merrily running. It's gotten to the point I dread CTDs while playing Rimworld or lol Pokemon Go, because I grown accustomed to it in Vic3.
Just a couple hours ago, my Roman Republic game crashed in peacetime, as usual. But now the game crashes whenever I try to load the savefile. I can't even send a report on Paradox Crash Reporter, it says "the upload failed for an unknown reason".
So I deleted shadercache, turned VSync off, yadda yadda. I tried loading it again, and this time it worked! But then I unpaused and it crashed after two days. Note, it crashed in less than half a week. There literally was no time for anything to happen, it was peacetime, even.
So I deleted shadercache etc etc again and did a clean install. The only thing I preserved was an old save file from a couple years prior, which I had kept saved elsewhere in my computer (I make a backup whenever I try out a risky diploplay). All reinstalled, I tried again with this old save.
It crashed on load. Again.
I mean. Literally how. It's a different save file, it's a clean install, there's no cache lying around.
Also, if it matters, I play on speed 5 90% of the time, but I've had the rare CTD on speed 4 too. I've also been playing with VTM mod this week, which weirdly enough reduced the number of CTDs I had until this save-breaking one.
Specs:
Windows 10 64-bit
No Windows Defender antivirus
NVIDIA GTX 1060 3GB
AMD Ryzen 5 1600 Six-Core Processor 3.20 GHz
16.0 GB RAM
Files:
papal_states_ironman, from my backup
pdx_settings.json, from Documents\Paradox Interactive\Victoria3\
system.log and error.log, from Documents\Paradox Interactive\Victoria3\logs\
exception.txt, from Documents\Paradox Interactive\Victoria 3\crashes\victoria3_20240206_022223\
DxDiag log, from literally three minutes ago.