DUPLICATE: It's Back! CTD on savegame

[unmerged(1054)]

It's Back! CTD on savegame

I am using 1.02. Things were going great in my Wales campaign. I loaded up a 1267 game and it crashed in 1269 during a manual save. Now I cannot save on ANY of my current save games... am I screwed? What causes this? How can I fix it?? Argh!

 

[Grosshaus]

Did you continue a game from 1.01?

 

[Jadelith]

hm

i just got the game, and downloaded 1.02 right away (never used 1.00 nor 1.01).

started as england, played for around 40 years, and then during an autosave, the game crashed.

and then i started as moskva, and the game crashed in 1069 (during an autosave).

so i cancelled autosaving, loaded the "oldautosave" for moskva, and the game went on smoothly, until i had to save the game on around 1100, when it crashed yet again. so now, all of the savegames are corrupted, and i only have the oldautosave from the 1069 moskva

i'm doing my best to stay calm, and i know you are working your asses off to correct the bugs but, this is pretty frustrating...

anyway, i opened the "autosave.eug" for my first moskva game, and all it had was this:

***name = "Hastings (1066)" *** (the starts aren't there )

so, this proves that the game crashes during saving
well, i guess you guys already know what the problem is, but this is just my 2 cents

thanks for all the effort you put in for debugging.

 

[unmerged(1054)]

Did you continue a game from 1.01?

No, it was a new gamepost-patch (1.02). I had the same problem in 1.01, but could not get past 1107. At least I got into the 1200's this time.

 

[unmerged(29049)]

I had the same problem (noted on an earlier poast). The only answer Ive heard is that "my kingdom ended" and the "you loose" sign wont show because of a problem with some grafic drivers. But I dont think this sounds corect. I'm sure its what you guys have, problems with saving.

 

[Cat Lord]

Duplicate of 395

Cat