Resolved Corrupt Save?

正在查看此主题的用户

Made an account just for this. I've sent back multiple sets of logs from the debugger.

Most of my saves are corrupted, except for a few that are all 6+ hours old (I had about 18hrs play time when it happened).

I know there are a lot of different corruption points at the moment, so hopefully the following reproduction steps help you guys out.

Reproduction Steps:

1. A city was being sieged so I had to decide whether I wanted to help relief it. Saved a few times while buying supplies, etc.
2. Decided to provide help, but the invading host broke the siege to chase me (lol).
3. Saved the game before starting the battle.
4. Left for dinner so I exited the game before starting the battle
5. Came back after a while and tried loading my latest save.
6. Game failed to load, essentially any save near the city that was getting sieged or the location of the battle is corrupted

Additional Info:
Invading host had a size of >500
My party was about ~70
Nearby allies totaled about ~600


Edit: Today's patch (1.0.2) did not fix it.
 
In my case i was raiding a village from western empire (or southern), and a Lord party from this faction intercepted me raiding the village, so i exit and load the auto save, crash. After this, everytime entering in resume game, crash. I solve the crash deleting all 3 saves who i had and starting a new campaign :/ !!
 
In my case i was raiding a village from western empire (or southern), and a Lord party from this faction intercepted me raiding the village, so i exit and load the auto save, crash. After this, everytime entering in resume game, crash. I solve the crash deleting all 3 saves who i had and starting a new campaign :/ !!
That not the solution :/
 
This has to stop, lost all my day of playing again, yesterday, same thing. Its like none of them fired up the game before EA. Saving function is clearly, thrashy.
 
I hope the fix will retroactively repair save games or at at the very least prevent in progress saves from being totally lost. If not that's terribly embarrassing. I understand the game is early access but this is truly one of the few things that's entirely unacceptable for anything charging you money to use.
 
Can further confirm that 1.0.2 doesn't fix broken saves. They seriously need to put this bug on the highest priority and drop everything else for the time being.
 
Can further confirm that 1.0.2 doesn't fix broken saves. They seriously need to put this bug on the highest priority and drop everything else for the time being.
I hope the fix will retroactively repair save games or at at the very least prevent in progress saves from being totally lost. If not that's terribly embarrassing. I understand the game is early access but this is truly one of the few things that's entirely unacceptable for anything charging you money to use.
It does suck, but I find it very unlikely for them to be able to fix current saves with a patch, just new ones. I think thats because the problem with corruption is some sort of memory leak over time to the 45th save and load, and the last working saves are probably in bad condition even right before that.
 
It does suck, but I find it very unlikely for them to be able to fix current saves with a patch, just new ones. I think thats because the problem with corruption is some sort of memory leak over time to the 45th save and load, and the last working saves are probably in bad condition even right before that.
I’m assuming that they won’t be able to save the completely corrupted saves. Though the ones prior to complete failure should probably be somewhat salvageable hopefully.
 
Please prioritize this and fix asap!!

FYI - If still not clear, it's the act of loading and then saving a progress which corrupts it.

- Loading it multiple times without saving in between still counts as "1 corrupt".
- Saving it multiple times without loading in between still counts as "1 corrupt".
- After "45 corrupts", it just crashes.

This means if you go back to a save which only had 40 corrupts at the time, you will have 5 more load+save actions before the crash. It doesn't matter how many save files you have - it's still the same progress.
 
So I started getting this problem today after 1.0.2 - Saves from ages ago still work, but any of my recent saves from today are corrupted and wont load.

Does anyone know, is this play-through lost? I've read a bit about the 45 save bug and I'm wondering if anyone has seen the developer address this? Is it possible these corrupted saves can be salvaged or should I be looking at starting a new game once the save bug has been resolved?
 
Made an account just for this. I've sent back multiple sets of logs from the debugger.

Most of my saves are corrupted, except for a few that are all 6+ hours old (I had about 18hrs play time when it happened).

I know there are a lot of different corruption points at the moment, so hopefully the following reproduction steps help you guys out.

Reproduction Steps:

1. A city was being sieged so I had to decide whether I wanted to help relief it. Saved a few times while buying supplies, etc.
2. Decided to provide help, but the invading host broke the siege to chase me (lol).
3. Saved the game before starting the battle.
4. Left for dinner so I exited the game before starting the battle
5. Came back after a while and tried loading my latest save.
6. Game failed to load, essentially any save near the city that was getting sieged or the location of the battle is corrupted

Additional Info:
Invading host had a size of >500
My party was about ~70
Nearby allies totaled about ~600


Edit: Today's patch (1.0.2) did not fix it.
As mentioned earlier in this thread, you get this crash becouse your old 1.0.0 save file has loaded a bug that since later have been patched,this creates a paradox which the computer can't compute with and you crash, hench why you crashed after you re saved it to a 1.0.1 save or even later.
Ssadly, as far as I know there is no way to recover this. I had the same issue with a 35+hour save but had to start over.

However there is nothing to say this won't happen in the future with similar bugs that do get patched, we caan only hope and not get to attacched to our saves.
 
Please prioritize this and fix asap!!

FYI - If still not clear, it's the act of loading and then saving a progress which corrupts it.

- Loading it multiple times without saving in between still counts as "1 corrupt".
- Saving it multiple times without loading in between still counts as "1 corrupt".
- After "45 corrupts", it just crashes.

This means if you go back to a save which only had 40 corrupts at the time, you will have 5 more load+save actions before the crash. It doesn't matter how many save files you have - it's still the same progress.
Are you sure about that? I think it didnt work like that, more like the saving and loading is connected - just saving ur game 500 times does work, but saving, loading and continuing this will make it corrupt.

Basic simple example : Start game, Save on exit, then next day you load ur game. There is now "1 corrupt"

I am not certain, but I say this because I saved my game hundreds of times before this happened to me, but indeed I might have loaded those saves around the 45 limit.
So I started getting this problem today after 1.0.2 - Saves from ages ago still work, but any of my recent saves from today are corrupted and wont load.

Does anyone know, is this play-through lost? I've read a bit about the 45 save bug and I'm wondering if anyone has seen the developer address this? Is it possible these corrupted saves can be salvaged or should I be looking at starting a new game once the save bug has been resolved?
Unknown at this point, I hope more people will help get this to the devs attention.
 
If someone has an early (right after tutorial preferably) save file that's working, would they mind uploading it somewhere so that we can try and use it?
I think I might have a different problem to a lot of people in this thread? (Loading just doesn't work at all.)

Also as a side note, I tried to roll back to 1.0.0 and change my system time back to the morning of 31/03. Doesn't seem to be related to the date of the save :xf-tongue:
 
I created a new character under 1.0.1 and played under 1.0.2. I saved more than 45 times— maybe 70, not sure about the number of loadings. The saves don't grow constantly— sometimes the later save is smaller than the previous one. The game started crashing when saves' size reached 50k— after some time. The save before the first broken works fine
 
后退
顶部 底部