|
Post by glob on Apr 23, 2019 0:33:23 GMT
For some reason my saves keep getting corrupted. I'm not using any other mods with a completely fresh install of ck2. The mod works great with no other crashes. However, it's been about 150-175 years since I started my game and it just crashes whenever I save. I have had to roll back to saves 5-10 years old which fixes the problem but it doesn't take long for it to start happening again. I've tried changing the duration in which the game auto saves and completely disabling autosaves resorting to manual saves but it hasn't help.
Anybody got any solutions? I can provide any additional information that might help
Edit: I have all major DLC installed and running. I have never had this problem with vanilla CK2
checksum: MVMD modversion: 1.9.1 ck2 version: 3.1.0
Win10 64bit i7-6770k Nvidia 1070 16gb ddr4
|
|
|
Post by MadaraTargaryen on Apr 24, 2019 8:35:30 GMT
Upload the uncompressed save file in which the game crashes and wait for one of the devs to have a look at it.
|
|
ulric
New Member
Posts: 7
|
Post by ulric on Apr 25, 2019 12:40:22 GMT
Some script or event firing on january 1 cause of that trouble. You can avoid it by saving on december 31, editing the save file and changing date to january 2 the next year. Saves will work fine until next january 1.
|
|
|
Post by zeuxippe on Apr 27, 2019 10:45:52 GMT
I'm having the same issue and it does NOT appear to be a memory usage problem, as I have 8GB RAM on Windows 10 64-bit and tried everything relating to that short of buying more RAM, even increased the paging memory file to double its original size. Plus I don't get a runtime error, the game just closes. I've just taken this mod up again (as I am compelled to do whenever a season starts) and I don't remember ever having this issue even though my old computers weren't as fast as the one I have now. Of course it has always grinded to a halt every month after a few decades of playing but the game never outright crashed on me just for trying to save. I've started new games to see if it would replicate and it did. As it is and considering my slow style of playing, I can't even make king before my saves are effectively disabled and it basically means it's unplayable, at least to me. Also I have NOT tried to see if it would happen in vanilla as I'm not as interested in playing it without the mod, but I will if needs be. Here's the most recent save I could make, playing the High Lord of Vaith : www.mediafire.com/file/q3z2rqym2p464bp/Vaith8188_11_13_2.ck2/file
|
|
|
Post by Buck on Apr 27, 2019 11:17:38 GMT
Can you actually load that save?
|
|
|
Post by zeuxippe on Apr 27, 2019 12:06:01 GMT
Yes. The game only crashes when it tries to save OR when I try to load a save before the checksum has fully loaded. Loading a save with the checksum apparent works fine.
|
|
|
Post by Azrael on Apr 27, 2019 21:25:47 GMT
Some script or event firing on january 1 cause of that trouble. You can avoid it by saving on december 31, editing the save file and changing date to january 2 the next year. Saves will work fine until next january 1. This is why I disable autosave myself.
|
|
|
Post by agyleon on Apr 27, 2019 22:22:06 GMT
what is the size of the save game, cause if it crash on trying to save it may be due to a sdave bloathing bug
|
|
|
Post by zeuxippe on Apr 27, 2019 23:32:01 GMT
what is the size of the save game, cause if it crash on trying to save it may be due to a sdave bloathing bug 74MB
|
|
ulric
New Member
Posts: 7
|
Post by ulric on Apr 28, 2019 6:04:17 GMT
This is why I disable autosave myself. Right. But this trouble isn't related to autosave at all. Something happening january 1st and game start crashing at every save, but as long as you avoid this date, you can autosave, quicksave, or regularsave game without any problem. And the fun part - bug may disappear at some point.
|
|
|
Post by zeuxippe on Apr 28, 2019 13:11:47 GMT
Do you know about how long it takes ? I've tried disabling autosave and playing for a couple years before attempting a save, because I have fond memories of CTDs when some event somewhere made even the vanilla game crash at specific dates in previous versions, but no dice. One thing I haven't tried is ironman. Would it be worth playing it to see whether the game just corrupts the automatic save file after 150-200 years ? Would it help pinpoint the problem if I provided said file ? No guarantees I can survive 200 years in ironman though
|
|
ulric
New Member
Posts: 7
|
Post by ulric on Apr 29, 2019 6:46:11 GMT
From my personal experience, it may disappear after 1 year or not disappear after 50. Some people said, it tooks more than 100 years, before saves start work again.
|
|
|
Post by kiffe on May 2, 2019 21:02:16 GMT
This bug haunts me in my sleep. It's been around since the dawn of this mod, and i've searched every forum on the seven kingdoms for a fix. It always happens eventually in a save. Makes the mod basically unplayable to me. If you're used to longer playthroughs, it'll happen to you, too. Disabling autosaves doesn't work either. It'll crash the moment you try to save after the date it was supposed to crash on auto. The only known fix is the one stated, editing the savefile to skip january 1st every year until it stops happening. But with the amount of time this game takes to boot up, you'll probably find you're wasting your time doing this.
|
|
ulric
New Member
Posts: 7
|
Post by ulric on May 7, 2019 11:48:35 GMT
But with the amount of time this game takes to boot up, you'll probably find you're wasting your time doing this. You don't need to restart the game. Just save, alt+tab, edit the save, and load edited save. Kind of annoying, but rather quick method.
|
|
icen
New Member
Posts: 7
|
Post by icen on Jun 10, 2019 12:28:27 GMT
as stated above the game doesn't have to do with anything with yearly autosave i believe it is just coincidental as if you set the yearly autosave to monthly or half a year it still only happens on a specific date for the playthrough i am in rn it happens in the first of january while in my other playthrough it happened on the 26 day of any month not a specific one
|
|