• 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.
Hello!

I was not able to reproduce the CTD on our current internal build (might be fixed there?).
Please attach the related CTD folder here so I can check on it in more detail.

CTD folders are usually found at:
C:\Users\[USERNAME]\Documents\Paradox Interactive\Victoria 3\crashes
 
I am experiencing the same issue. It seems to be related to the autonomous investment pool and it also occurs on the same (or similar, I recall the month being the same) date.
 

Attachments

  • game.log
    48,2 KB · Views: 0
  • error.log
    63,4 KB · Views: 0
  • debug.log
    265,6 KB · Views: 0
  • Lucca III.v3
    32,8 MB · Views: 0
  • 2Like
Reactions:
Hello!

I was not able to reproduce the CTD on our current internal build (might be fixed there?).
Please attach the related CTD folder here so I can check on it in more detail.

CTD folders are usually found at:
C:\Users\[USERNAME]\Documents\Paradox Interactive\Victoria 3\crashes
I could not find the original, but having a similar issue with this save around 3 November or a few days after save starts.
 

Attachments

  • debug.log
    237,1 KB · Views: 0
  • error.log
    17,2 KB · Views: 0
  • game.log
    44 KB · Views: 0
  • system.log
    920 bytes · Views: 0
  • autosave_1.v3
    29,4 MB · Views: 0
Without a minidump (found in DRIVE NAME/Users/YOUR USERNAME/Documents/Paradox Interactive/Victoria 3/crash) and your system specs we cannot troubleshoot the CTD, though I suspect you might not have sufficient virtual memory assigned with just 8GB of RAM available.
I'll move the thread to our Technical Support so they might assist you further.
 
Last edited:
Without a minidump (found in Documents/Paradox Interactive/Victoria 3/crashes) and a DxDiag log we cannot troubleshoot the CTD, though I suspect you might not have sufficient virtual memory assigned with just 8GB of RAM available.
I'll move the thread to our Technical Support so they might assist you further.
Unfortunately these are macOS machines - DxDiag obviously does not exist since that involves DirectX, a Windows - specific program. Minidumps also do not exist.

VRAM depends on the type of Mac as well. Apple Silicon devices do not have a set amount of VRAM since the GPU and the CPU are integrated, and macOS allows for sharing of the memory depending on the task at hand. I experienced CTDs on my 16GB RAM Macbook Pro M1, so my guess is that the VRAM is not the case - or maybe it is due to a failure of Victoria 3 recognizing the Apple Silicon device and attempting to call Windows - specific programs?

I do not work in the tech sector, so if I have this information wrong, I apologize. But most Mac users have been experiencing crashes, so it might be worth looking at the macOS - specific version to diagnose issues.