Resolved Corrupt Save?

[RainbowWarrior]

Thanks, Taleworlds! That's some amazing job you have done there! Keep it this way and we will be able to save up to 100 times in another 8 years

No, seriously, how hard can it be? Everyone understands it's early access, but the game must be playable, at least for the majority. Was it so hard to make it work at least in all that time you had? Shame

 

[krzkkrzk]

I can confirm that, just tested on new campaign, new save got corrupted on #55 cycle.

Thanks for your effort. Seems like it is now confirmed by couple guys - creating new game gives you 54-55 save/load cycles.

BTW It is crazy - what, devs dind't tested new patch? It took people about 1 hour to test it and find out that patch is not working. I'm starting to think that it is some serious problem and we have to wait couple days for the real fix.

 

[abowman3d]

I'm requesting a refund, 2 hours be damned. This game simply does not work.

 

[Waffenbaum]

I'm requesting a refund, 2 hours be damned. This game simply does not work.

Thanks for telling us.
You can always buy it at full price when it's finished.

 

[Roach23]

Confirming getting up around 55, last save no longer working on 1.03, new campaign, paused after tutorial, not fixed.

 

[Ainth]

Im curious what type of bug causing crashes like this? It doesnt depends on file size, and surely not on progressing (quest, etc).
The only solution is that the game does something wrong with the saving. Maybe a slow filling buffer or memory leak, written into the save, causing the crash (like you always multiply the nr of the AIs on the map, sooner or later it will crash)
Its a bad news then, because if they fix the bug, the currupt save will remains in the same state.

 

[Bob Gnarly]

Looks like I won't be starting a new campaign this weekend.

I wouldn't get attached to your old saves guys, I doubt they'll be recoverable at this point.

 

[Arcano30]

Looks like I won't be starting a new campaign this weekend.

I wouldn't get attached to your old saves guys, I doubt they'll be recoverable at this point.

I wont mind starting all over I accept that as part of EA, but a bug that prevents you from saving your game, now that is a game breaking bug that should have been address inmediately.

 

[krzkkrzk]

I thought that Bannerlord saved me form coronavirus situation, but I guess, it was to beautiful to be true (an it was beautiful - my first 23 hours were charming and amazing ). Ok, waiting for the fix.

 

[Basileuss]

Looks like I won't be starting a new campaign this weekend.

I wouldn't get attached to your old saves guys, I doubt they'll be recoverable at this point.

Honestly I don't care too much about my old saves, even if I lose my 40 hours of progression (2 runs) I guess it's fine as long as they fix it in a reasonable time, if they could also fix old saves it would be great ofc but yeah, just hoping it get fixed really quickly.

 

[AlexShep]

Im curious what type of bug causing crashes like this? It doesnt depends on file size, and surely not on progressing (quest, etc).
The only solution is that the game does something wrong with the saving. Maybe a slow filling buffer or memory leak, written into the save, causing the crash (like you always multiply the nr of the AIs on the map, sooner or later it will crash)
Its a bad news then, because if they fix the bug, the currupt save will remains in the same state.

I guess, SaveFunction just write smth to every new file (growing size, even when you are standing) so just like LoadFunction, and after a few cycles - written info give paradox to LoadFunction, because me and other guys found out - u can make a lot of new savefiles or rewrite save file also just loading a lot of times, but only LoadFunction and further save put bad seed to savefile, but who is the main troublemaker - that's the real question. And I hope, programmers will find it out asap, cause 1.0.3 patch made nothing, people with saves from 1.0.2 (majority will resume their campaign) still got 45(or may be 46) save/load cycles.

 

[Roach23]

I guess, SaveFunction just write smth to every new file (growing size, even when you are standing) so just like LoadFunction, and after a few cycles - written info give paradox to LoadFunction, because me and other guys found out - u can make a lot of new savefiles or rewrite save file also just loading a lot of times, but only LoadFunction and further save put bad seed to savefile, but who is the main troublemaker - that's the real question. And I hope, programmers will find it out asap, cause 1.0.3 patch made nothing, people with saves from 1.0.2 (majority will resume their campaign) still got 45(or may be 46) save/load cycles.

As well as starting a new campaign on 1.03 will have the same fate, only 10 or so more saveloads than the previous versions.

 

[Ayaka]

my problem solved, i can load my save and play, thank you!

 

[Roach23]

my problem solved, i can load my save and play, thank you!

Have you saved and loaded after the update?

 

[D-12]

Waiting patiently for the fix, hopefully tomorrow. Seems like a big issue to tackle.

 

[Uhtred3712]

After the update I was able to load my save twice, after that it gets corrupted again.

 

[StatusBlain]

Guys, a campaign save started in 1.0.2 who wasn't corrupted (almost 20 saves/loads before 1.0.3), i did stress test, 35 saves and loads after 1.0.3, and dont crashed or save corrupted.

 

[Roach23]

Guys, a campaign save started in 1.0.2 who wasn't corrupted (almost 20 saves/loads before 1.0.3), i did stress test, 35 saves and loads after 1.0.3, and dont crashed or save corrupted.

Let us know after you saveload around 55 times, make it to 65. Good luck!

 

[Ayaka]

gaddem, try to load my save after two saves, and crash

 

[StatusBlain]

Let us know after you saveload around 55 times, make it to 65. Good luck!