Cannot load saved game

[unmerged(3843)]

I've been playing a game for more than a week now and I've been able to save and reload it normally until now.

Now when I try to load my saved game I can get as far as "initialising script" before everything just freezes up. I've waited around for 15 minutes but nothing happens.

The same thing happened when I tried to load my autosaved game.

I can load new games normally.

I'm using version 1.04a.

Can anyone help please?

 

[Castellon]

What about "oldautosave" ?

 

[unmerged(3843)]

What about "oldautosave" ?

I just tried it. No luck. It also stopped loading at "initializing script."

I started a new game and saved it. I was then able to reload the new game normally. But I can't reload my original game (72 years as ruler of Castile ... apparently lost).

 

[Castellon]

That is very suprising that both autosave would become corupt, you have no manual saves from earlier that you could salvage?

 

[unmerged(3843)]

That is very suprising that both autosave would become corupt, you have no manual saves from earlier that you could salvage?

It is indeed surprising that both autosaves and my manual save could have become corrupted. I've never had problems with any other saved Paradox game ... or any other saved game for that matter.

When I searched the CK forums using the term "initializing script" I found that other people have experienced the same problem. They also had saved games which froze up at the initializing script stage of loading.

One such example can be found here: http://forum.paradoxplaza.com/forum/showthread.php?t=178932

Unfortunately I do not have any earlier manual saves that I can salvage.

 

[Castellon]

Are you using any of the beta patches?

 

[unmerged(3843)]

Are you using any of the beta patches?

No beta patches. No mods.

 

[Castellon]

Get the latest beta, it apears to help significantly with this problem.

 

[unmerged(3843)]

Get the latest beta, it apears to help significantly with this problem.

Thanks Castellon. I will try out the latest beta.

 

[Castellon]

Great.

 

[Grosshaus]

Thanks Castellon. I will try out the latest beta.

Actually I think the changes will be in the next beta patch instead of the current one from February 3rd. Better to check in the beta forum in the future as well.

 

[Castellon]

My advice was based on the same problem reported and fixewd by installing an even earlier beta, so unless you are telling me the current beta broke the earlier fix, I think my advice still holds.

 

[unmerged(3843)]

My advice was based on the same problem reported and fixewd by installing an even earlier beta, so unless you are telling me the current beta broke the earlier fix, I think my advice still holds.

I tried playing a game with the latest beta. It was even less successful than my first game with 1.04a. After playing five years the game froze up when it was autosaving. When I tried to reload the game it completely froze up when I tried to load the 'autosave' and 'oldautosave' files. I won't be playing CK again. It's not a patch on EU II.

 

[Castellon]

That save issue is a seperate one, and I think is what Grosshaus was thinking of when he said it is fixed in the next patch.

 

[Third Angel]

Maybe try this:

http://forum.paradoxplaza.com/forum/showthread.php?t=171346&page=1&pp=25


I don't know if this was fixed in March 21st beta...

 

[Castellon]

Interesting

 

[Third Angel]

Interesting

Well, everyone seems to have forgotten about this nasty bug which makes you lose games you might have been greatly enjoying. Most of the times, autosaves are useless since, once U019 phantom-country has been created, it will be in every next save you make, until you manually remove it.
The easiest way to know if your savefile is unable to load because of the U019 bug is to look at the counties picking list. There should be a black shield with no name if it is so. To remove it, just follow the above thread’s last post’s instructions.
Now it would be nice to know if this was fixed in latest beta and if not, if it might be later or is too hard to fix.

 

[Castellon]

That would be a bug forum issue not a support issue.

 

[Third Angel]

That would be a bug forum issue not a support issue.

Sure but you're the one who can move threads.
I'm pretty sure the original poster's problem was the bug I am referring to. So I just gave a link towards the bug forum thread where this issue was discussed; and then I just asked if we could hope for a fix or not.

 

[Castellon]

And I was telling you that if you want info on bugs then ask in the Bug forum, as I have nothing to do with bugs. And I don't want it moved because here it serves as a reference for others that may look here and not the bug forum and provides a link to the BF thread, and since as you say there is already a thread in the BF about it, it would serve no purpose to have this one moved there.