Upvote
0
-
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.
The corrupted savegame is of little value in itself, as the truly valuable thing would be a savegame that goes virtual reproducably on preferably next autosave or manual save.
It's good to have screenie about it though. I never thought doing that myself.
It's good to have screenie about it though. I never thought doing that myself.
http://duuk.com/images/CK/oldautosave.eug
http://duuk.com/images/CK/Bourgogne.eug
The 2nd one has resulted in it twice now.
http://duuk.com/images/CK/Bourgogne.eug
The 2nd one has resulted in it twice now.
So the Bourgogne save will result in a VFC on next autosave?
EDIT: Please, use zip or rar next time, it's tedious to DL 10 megs when it would be just 1 meg archived.
EDIT2: I ran three test runs with the Bourgogne save into next jan, all autosaved correctly and the manual saving I did after jan with one run also worked correctly.
EDIT: Please, use zip or rar next time, it's tedious to DL 10 megs when it would be just 1 meg archived.
EDIT2: I ran three test runs with the Bourgogne save into next jan, all autosaved correctly and the manual saving I did after jan with one run also worked correctly.
Last edited:
Well, I can try running the save for a longer period of time than just to next autosave point when I'm back on my own comp.
I get this error when I go to save the game (or at autosave) about 50% - 66% of the time.
The .eug file is always 59Kb and ends right after the line:
province = { 0 1100 1100 3 4 5 6 7 1056 1056 10 11 12 1144 14 15 1119 (etc...)
This is right before the
globaldata = {
startdate = { year = 1121 month = april day = 22 }
enddate = { year = 1453 month = january day = 0 }
war = { (etc)
data should be. Has this bug been reported? It seems like something that should be easy enough to track down. It is really the only time the game crashes for me. (there are a few other rare CTD's) but not enough to really hinder the playing such as this one.
The .eug file is always 59Kb and ends right after the line:
province = { 0 1100 1100 3 4 5 6 7 1056 1056 10 11 12 1144 14 15 1119 (etc...)
This is right before the
globaldata = {
startdate = { year = 1121 month = april day = 22 }
enddate = { year = 1453 month = january day = 0 }
war = { (etc)
data should be. Has this bug been reported? It seems like something that should be easy enough to track down. It is really the only time the game crashes for me. (there are a few other rare CTD's) but not enough to really hinder the playing such as this one.
I get the same error message on manual save game. The problem is it's not happening every time, but when the error occurs, the save game is only around 65K, not the usual multi-mega. This save game obviously also can't be loaded. I'm using 1.04 patch + april 28 beta.
Well, naturally it's that short 
The saving routine itself crashes out during accumulation of the data to put into the save. That results in the application terminating prematurely. Windows will then close down the still open save game file, at the point where the save game data had already been committed to disk. Given the standard cutoff size of 59KB, that is presumably only the first commited data block.
In fact, having observed Windows behaviour when writing data to a large file, Windows usually only commits the very first data block, buffers additional multi megabyte data in RAM, which then only ends up in the disk file if either the program explicitly calls flush for the data stream or closes the file. So, the crash could have been near the end of the data stream, and you still end up with a 59 KB file.
Having said all that, I've seen the pure virtual function call crash during saving as well. But I was still on april 5 beta at the time, so it was not opportune to post a report for it. Having said that, at the time of the crash, like the thread starter, in my game a crusade was in effect. Secondly, I was at war with the tribe of Pommerania, and had confiscated all of their provinces. The last province of the tribe was under siege by a third party, and moments before the autosave point I had rejected a peace proposal that was triggered by some event, instead of the usual way (through a diplomat of the opposing party knocking on my doorstep).
Jan Peter
The saving routine itself crashes out during accumulation of the data to put into the save. That results in the application terminating prematurely. Windows will then close down the still open save game file, at the point where the save game data had already been committed to disk. Given the standard cutoff size of 59KB, that is presumably only the first commited data block.
In fact, having observed Windows behaviour when writing data to a large file, Windows usually only commits the very first data block, buffers additional multi megabyte data in RAM, which then only ends up in the disk file if either the program explicitly calls flush for the data stream or closes the file. So, the crash could have been near the end of the data stream, and you still end up with a 59 KB file.
Having said all that, I've seen the pure virtual function call crash during saving as well. But I was still on april 5 beta at the time, so it was not opportune to post a report for it. Having said that, at the time of the crash, like the thread starter, in my game a crusade was in effect. Secondly, I was at war with the tribe of Pommerania, and had confiscated all of their provinces. The last province of the tribe was under siege by a third party, and moments before the autosave point I had rejected a peace proposal that was triggered by some event, instead of the usual way (through a diplomat of the opposing party knocking on my doorstep).
Jan Peter
Still occurring in April 28th Beta. Save game is pretty useless as I wanted to run debug on it but it seems to have corrupted every save game I had of that particular game (when I tried to load one the computer just hung inderfinitely). Went for manual reinstall as it kept occuring every 2 or 3 years once it had occurred once.