|
|
Post by kiffe on Mar 9, 2019 19:00:34 GMT
I'm currently going through a bug that's not listed under "unsolvable known issues" yet seems to be a very recurrent bug in this mod. After playing for some years, the game starts to crash during autosave on the first of january. If you google the issue multiple threads pop up reporting it, some recent and some dating back to 2014. Only known "fix" i found is saving before january and manually changing the date to the 2nd of january every year. But this is far from fun. Is there any other way to circumvent this? This is the error log i got last time it crashed. I have no way of confirming if i got the same log on the other times i tried fixing it, cause i've tried a lot, but this should be of some use. I'm not familiar with coding, but looking at it seems like the game is, at least this time, trying to run some game setup regardless of the fact the game started up years ago. That's my guess based on the fact that i see many provinces having too many entries and names that would be from the robert rebellion's start. This is further confirmed by the fact that this bug showed up in the end of 8291. Regardless of this, if i skip the year, it'll crash again on the next year. Hope this info helps! Thx. pastebin.com/ax4w7KfV |
|
|
|
Post by alannister on Mar 9, 2019 19:40:52 GMT
Yeah I noticed this bug too, I don’t get the save bloat but random crashes on first of month but it’s not a sure thing on my end like once every old how many years but it’ll just crash on the first
|
|
|
|
Post by ManicMayo on Mar 16, 2019 14:28:16 GMT
I've just had the same problem. No save bloat issue as of yet, but on the start of the 110th year into my game and it crashes on autosave. If I disable autosave and let it tick over the 1st and then try to save manually, it crashes. If I let the game run for another year and then save in 8111, it crashes. At first, I thought it was me accepting a call to arms from the Night's Watch against a King Beyond the Wall since that often causes crashing for me, but going back and refusing or console-killing the king to prevent the war from even triggering doesn't fix the issue. This was seemingly fixed (for me) in 1.7 but it has sadly returned with a vengeance, either that or I had just got incredibly lucky in that patch. Only known "fix" i found is saving before january and manually changing the date to the 2nd of january every year. One problem I had with this is that it'll cause issues where you'll find adult characters with child traits and no education trait since they 'came of age' on the 1st of January and you've skipped over their birthday. While the stars have to align just right for a child to be born on that exact day, if you're skipping it every single year, it does stack up eventually and the world will be full of characters with this issue. |
|
|
|
Post by didgeridoo on Mar 16, 2019 15:59:28 GMT
I've just had the same problem. No save bloat issue as of yet, but on the start of the 110th year into my game and it crashes on autosave. If I disable autosave and let it tick over the 1st and then try to save manually, it crashes. If I let the game run for another year and then save in 8111, it crashes. At first, I thought it was me accepting a call to arms from the Night's Watch against a King Beyond the Wall since that often causes crashing for me, but going back and refusing or console-killing the king to prevent the war from even triggering doesn't fix the issue. This was seemingly fixed (for me) in 1.7 but it has sadly returned with a vengeance, either that or I had just got incredibly lucky in that patch. Only known "fix" i found is saving before january and manually changing the date to the 2nd of january every year. One problem I had with this is that it'll cause issues where you'll find adult characters with child traits and no education trait since they 'came of age' on the 1st of January and you've skipped over their birthday. While the stars have to align just right for a child to be born on that exact day, if you're skipping it every single year, it does stack up eventually and the world will be full of characters with this issue. yes. I had the exact same bug in 1.7 and just abandoned the save. I believe the post with the fix that kiffe is citing is a vanilla bug called "corrupted save". |
|
|
|
Post by didgeridoo on Mar 16, 2019 16:28:18 GMT
Original thread containing the fix?https://www.reddit.com/r/CK2GameOfthrones/comments/4nay7s/can_no_longer_save_the_game/
|
|
