• 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.
smn said:
Thanks for the tip, looks like it fixed the game for me ..! And now my tip for other people doing this kind of recovery stuff:

Use an editor that supports replace with regular expressions! I used UltraEdit and aborted all the children in less than 15 seconds.
'impregnationdate *^p' and 'childs_father *^p' are your friends in UE :)

The problem with this approach, is that you remove all pregnant, and not only the ones that makes the game crash. There is a lot of pregnacy that goes well!
 
MrT said:
Got it, thanks (though not sure why you sent it 5 times... :eek: :confused: ) ...

I am SO sorry about that! My Outlook + Mcafee were freaking out, I wasn't sure if you even got it.

I'm glad you were able to track down the bug. I went back to a save about 3 years earlier and was able to continue the game.

I guess in this new reality the Antichrist was never conceived. :)
 
MrT said:
We think that we might have identified the source of the problem and are currently working on a fix...

Hope you find a solution, because this is quite annoing. I get the same problem some time later. So, now I am saving and deleteing pregnant women all the time. :wacko:

I have suspected a problem with inbreed in Royal families, but this is pushing it... :rofl:

Is there a workaround that is working now? Or, does everybody suffer from this problem?
 
kit001 said:
The problem with this approach, is that you remove all pregnant, and not only the ones that makes the game crash. There is a lot of pregnacy that goes well!

And, as tried & tested, the parents producing the 'faulty' children just end up making another one .. I ended up wiping the babies for about 5 years in a row before I gave up .. :(

Well, better to put the game aside and wait for an official fix I guess.
 
Try the following:

Search your save game for "dyn = 0 " and replace any instances you find with "dyn = 708 ". That will very likely solve your problem and allow you to continue. No promises, though, since we're not positive that this is the only cause.
 
Last edited: