Random Crashing [1.33, nomods, Mac OS]

[Ferdinand_Bardamu]

Guys thank you for your continued work to try and resolve this. It's really frustrating that my game keeps crashing. Hopefully we can come to a solution.

 

[grotaclas]

Guys thank you for your continued work to try and resolve this. It's really frustrating that my game keeps crashing. Hopefully we can come to a solution.

Can you test the save from the comment above yours? Does it crash if you load it as Great Britain, wait for the next month tick and click on one of the manpower options in the english civil war event?

 

[Ferdinand_Bardamu]

Can you test the save from the comment above yours? Does it crash if you load it as Great Britain, wait for the next month tick and click on one of the manpower options in the english civil war event?

Yes, it crashes for me.

 

[Kvin1917]

Hi, faced such an error in my game as Georgia. But if at first there was just a crash and I could start again with autosave, now there is a constant crash on March 1, 1678. I can’t get around it at all. There is also an error with the manpower in the log
MacOS BigSur - 11.5.2

Thanks, will be glad for any help

 

[grotaclas]

Hi, faced such an error in my game as Georgia. But if at first there was just a crash and I could start again with autosave, now there is a constant crash on March 1, 1678. I can’t get around it at all. There is also an error with the manpower in the log
MacOS BigSur - 11.5.2

Thanks, will be glad for any help

As you can see in the game.log file, England got the english civil war event on that date. If you are not on ironman, you can avoid the crash by giving England enough manpower to pay for it(e.g. "tag ENG", "manpower" and then tag back to your original tag)

 

[Kvin1917]

As you can see in the game.log file, England got the english civil war event on that date. If you are not on ironman, you can avoid the crash by giving England enough manpower to pay for it(e.g. "tag ENG", "manpower" and then tag back to your original tag)

Hmm ok, i figured out the problem. Bad, because it was Ironman, maybe better be wait fix this problem from Paradox
Thanks for the help!
Last resort, I will be back to backup save 60 years ago)

 

[Ferdinand_Bardamu]

I've basically given up with 1.33 and switched back to 1.32. Absolutely zero crashing. This is clearly a 1.33 problem. Would be really nice if the issue could be addressed for 1.34.