Home Trending Latest threads New posts Developer diaries

help-saves crashing

Jump to latest Follow Reply
  • 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.
Show only dev responses
unmerged(17829)

unmerged(17829)

Sergeant
Jun 25, 2003
81
0
Visit site
I had no problem loading my saved game earlier today. I played up until the autosave at the end of the year and it crashed during the autosave (something that hasn't happened since I installed 1.03b). Now here's the problem. I obviously can't run autosave, and when I restarted my previous save and ran it, I decided to save later, just before the autosave to make sure it was ok. Problem, it crashed during save. Now I can't run autosave or my save. So, I run oldautosave. Problem again. During the next autsave (at the end of the year) crash again. Now, I can't even--for some reason--get oldautosave to work. Can I have assistance, or is it futile???

Thanks!

EDIT: I get an error message every time. Something regarding a mismatch.
 
Last edited:
Upvote 0
I've had the same problem with my latest save, a Kingdom of Italy game. Though I applied the dyn = 0 fix (there are references to certain characters' dynasties as being 0 in 1.03/1.03a save files, which was causing CTDs and crashes upon saving) it doesn't stop the game from crashing every time I save.
 
You say you get a mismatch error, when does that error happen and what exactly does it say?
 
The error occurs during "Reading Scenario" portion of loading.

Under the heading, "Critical Error":

Database Mismatch
Do you still want to continue?
Abort Retry Ignore

"retry" - CTD
"ignore" - CTD
"abort" - "Runtime Error! Program: ...Files\PE\CK\Crusaders.exe abnormal program termination" - CTD
 
hans1001 said:
Thank you.

I am at work, so as soon as I get home I will. Which file? autosave, oldautosave, or my normal save?
Click to expand...
As I understand it your oldautosave can load, but then crash on save? If that's the case, send me that one and one of the crashed saves for comparison... :)
 
Havard said:
As I understand it your oldautosave can load, but then crash on save? If that's the case, send me that one and one of the crashed saves for comparison... :)
Click to expand...

Unfortunately it's worse than that. Neither autosave nor oldautosave will load. After the 1st crash during autosave, I loaded up oldautosave. It ran through the year up until the next autosave (December 30) and then crashed... I think the old, bad autosave (created the 1st run) then became oldautosave during the 2nd autosave attempt. Hence, none of my saves work. In fact, it seems (although not tested) that I'm having trouble saving. Dunno why.

My preference would be to be able to play oldautosave if my theory is correct since that is the farthest I've gotten. Either way, your help is appreciated. Again, I will email this to you ASAP.

EDIT:
Order of operation leading up to the current situation:

1. Load saved game to play.
2. Play game thru end of year.
3. Autosave attempt 1 failed - CTD
4. Attempt to load autosave fails.
5. Load saved game again.
6. Play game thru to October something.
7. Normal save operation attempt failed - CTD
8. Load of saved game fails.
9. Only option left, load oldautosave.
10. Play thru end of year.
11. Autosave attempt 2 failed - CTD
12. Attempt to load oldautosave fails.
13. Seek professional help :confused:

Hopefully this outline helps understand my problem.
 
Last edited:
If you start a brand new game, then save it, can you load the that game?
 
I have this same problem. Crashes on save after a certain point, with a Database Mismatch error.

I have a save in October 1234 I made last night. When I started to play today, it crashed on auto-save. It crashes on manual saves, too.

I went back to a save a few years ago (1231). Crash on auto-save, crash on manual save. I'm not sure how it managed to auto-save at least once last night (as this old save is a couple of years old).

If I go way back in time (1223), it saves fine. So it's something to do with the current 'environment' of the game.

Any ideas? I can ship off a copy of the save-game-that-will-load-but-crash-on-save if anyone would like it.
 
Sounds like this needs to be in the BUg forum.
*Moved
 
Shipped off. Thank you for taking a look at this.

When I went back in time to the 1223 game, and played to this point again, it's doing the same thing (crash on save). Weird.

So now I'm in Ironman mode, no saving/quitting until the end of this game. :)
 
Castellon said:
If you start a brand new game, then save it, can you load the that game?
Click to expand...

No problems, saving or loading. In fact I also had it perform an autosave without a problem too. So, it may be farther in the game that it has trouble saving due to too much information or such. I'm not an exper to I wouldn't know.
 
HawaiiFive-O said:
Shipped off. Thank you for taking a look at this.

When I went back in time to the 1223 game, and played to this point again, it's doing the same thing (crash on save). Weird.

So now I'm in Ironman mode, no saving/quitting until the end of this game. :)
Click to expand...
All I can say for now is that I can confirm the problem :p

Save shipped off to Paradox with a bug-report...
 
I've run into a repeating CTD in a multiplayer 1.03b game as well. We had no major problems through the first 70 years of the game, but around 1138 the host crashed. The second player saved the game but after loading this game it would crash every time we tried to save. Any game that crashed while saving would give a Database Mismatch error when trying to load. So we went back to an older save from 3 years back, but it continues to crash every time between 1137 and 1139.

I sent the save file to one of the beta testers who was able to help me with a game that was hung up by the dyn = 0 error (although this game later started repeatedly crashing for some other reason). It's getting quite frustrating...I've started over 20 multiplayer games since buying CK, under every patch from 1.00 through 1.03b, and every one without exception has ended with a repeating CTD that wouldn't allow us to continue playing.
 
You must log in or register to reply here.
Top Bottom
Back