Resolved Save Failed! Cannot create save data

[Schlitzer]

Summary: I run through the campaign map. After a short time, I cant save anymore.. I loaded the past saves and always after the same amount of time, I cant save anymore. Before that, I can normally save. So I observed the events and invested that after the first event that occurs as message the save engine crashes and the error appears when trying to save.
How to Reproduce: ?
Quest/Settlement Name (if related):
Media (Screenshots & Video):

Version: e1.2.0 Beta
Computer Specs:
OS: Windows 10
GPU: Nvidia GTX 1050 TI
CPU: Intel Core I7 3770k
RAM: 16 Gb Ram
Motherboard: Dell 0GY6Y8
Storage Device (HDD/SSD): 512 GB SSD

 

[uçanbiblo]

Hello, sorry for the inconvenience. I have informed the devs about the issue and i am sure it will be fixed as soon as possible.

 

[Tsewe]

Hello, sorry for the inconvenience. I have informed the devs about the issue and i am sure it will be fixed as soon as possible.

Thank you! Many people are having this problem, including myself.
It started a few days ago and I've tried different solutions, but nothing worked out for me.

 

[ManicDoodle]

I have also been having this problem, and I wanted to add in some of the troubleshooting I've done. I should also mention that I have the game on my D: drive while the save files, while the save games are on the C: files. I've had this issue with the v1.2 beta and the one before the most recent hotfix. After the hotfix, I had several hours of play with saves from the game where I first noticed this issue, before I started getting the error again. I also started a new game before the hotfix, and was able to play for an hour or two before starting to get save game errors again. Now, neither character can save games, no matter what method I use.

Things I've tried, inspired by other forum posts, mostly:
- made sure my OS, virus protection, game, and drivers were up-to-date
- deleting all mods and verifying game files through steam
- opened game as administrator via bannerlord.exe and talworlds.mountandblade.launcher.exe
- allowed all .exe applications in the "Mount and Blade II Bannerlord/bin/Win64_Shipping_Client" directory through firewall and virus protection (windows defender), as was suggested on a number of other forum threads
- turned off all firewall and virus protection that I could
- turned off protected folders/allowed the Bannerlord .exe files as exceptions to edit protected folders
- right clicked on all Bannerlord files on my C: (where the .sav files are) and D: (where the .exe files are), and manually allowed write access to my account, even though I'm the only account on my computer.
- Removing all but one .sav file from the folder
- trying to create a "D:/Users/{username}/Documents/Mount and Blade II Bannerlord/Game Saves/Native/" directory tree to see if i could get the game to save there (I could not)
- Changing from beta branch to stable release

Non of these worked. Thanks for your support, and I know that you'd prefer to be doing other things than troubleshooting bugs, but this is a game-breaking and very frustrating issue to have.

Version: e1.2.0 Beta
Computer Specs:
OS: Windows 10 Home 10.0.18363 Build 18363
GPU: Nvidia GeForce GTX 1060
CPU: Intel Core I7 i7-8750H
RAM: 16 Gb Ram
Motherboard: HP 84DB-93.17
Storage Device (HDD/SSD): 1 TB HDD/256 GB SSD

 

[TheFief]

Same here

I was able to save just fine until e1.2.

Not sure.

 

[TheFief]

I just uninstalled all mods, deleted all saves and started a new campaign. I was able to save then.

 

[greggho]

May I add - same here, happened after 1.2 left "beta".

I can load from my previous auto-save (which was 1.2 beta), can quick save once or twice, but apparently if I do anything in-game and THEN save, the bug happens.

Also, after the error window pops up if I try to LOAD any save, the game crashes - with no debug/message at all.

I stored a copy of the "1.2 beta" save in my Drive, if any dev wanna have a look, just PM me.

 

[YcleptNano]

I found that I get this issue if I replace a native troop tree with my own, and don't name the ID's the same as the native tree. Renaming the new tree with the old ID's solves this (Everything else in the troop description can change). Just mentioning this in case anyone has done the same.

 

[greggho]

Hello, sorry for the inconvenience. I have informed the devs about the issue and i am sure it will be fixed as soon as possible.

No updates from the devs on this?
After my post above, I started a brand new playthrough (on beta 1.3.0) and at day 360 I get both this "save failed" issue and "Daily Gold Change Crashes Me".

Looks like the save failed issue starts happening when the save files become "bloated"
Mine skipped from 40Mb to 80Mb, some of these 80Mb files do allow saving and don't crash

On a separate note: these two issues that have been circling for almost a month.
The game has become literally unplayable and absurdly obnoxious to bear with...

 

[TheFief]

I think mine was mod related as I haven't had any issues since removing them (the mods) and validating game files, then being more mindful of which mods I install.

However, if I was in your position @greggho , I would probably feel the same. Sorry bud, hopefully they find and fix soon for you.

 

[Baki667]

I had this issue yesterday. Pretty sure it happened after I accepted a Family Feud quest. I had to load a very old save (somehow I could save from that one). After a while I took the same Family Feud quest from the same quest giver again (at least iirc) and the save issue reoccured.

Edit: Did the quest again with an older safe and can still save. Probably has nothing to do with that quest.

 

[greggho]

Pretty sure it happened after I accepted a Family Feud quest.

I'm actually considering that QUESTS in general are causing the save file bloat/long run issue that causes the "daily gold crash"...
Have you noticed as well that the Family Feud "one name only" NPCs are not deleted from the game? And they act somewhat erratically, moving from city to city but apparently doing nothing?
I wonder if this causes a snowball effect in the game on later stages, and even if other quests could be culprits...

I've tested the issue with save failed and seems like something, somewhere, triggers this snowball effect and, after an unset amount of days, the game will crash/not save anymore.
It doesn't matter if I fallback to previous saves, at some point the game will start crashing and at that same point it stops saving as well.

 

[greggho]

I think mine was mod related as I haven't had any issues since removing them (the mods) and validating game files, then being more mindful of which mods I install.

However, if I was in your position @greggho , I would probably feel the same. Sorry bud, hopefully they find and fix soon for you.

Worst part is, I've played my latest game from the start with no mods - and it was a slog, because the game is obnoxious/missing so much features/broken without them.
I'm pretty certain these issues I've been experiencing are related to the core game, maybe it's even the way I play it, I dunno... I just give up on being a free Q&A asset for TW... they got their money's worth from Early Access sales.

Once the 'real world' gets back to some semblance of normalcy I expect TW to start doing professional and proper Q&A (I mean, they SHOULD'VE DONE some Q&A all these years, they're not indie devs on a budget, but let's not even get into that particular can of worms)

 

[umutcan.kaya]

I am having this problem too and nearly tried everything. Is there not a fix yet?

 

[Magnusnyg]

Same problem (or very similar) for me it started with Patch 1.42 - I'm went back to 1.41 and I could create save files again.

 

[uçanbiblo]

Hello, sorry for the late reply. We have fixed a considerable amount of the problems we have encountered so far and improved the game performance with the multiple patches we have released. Please make sure that your game, your drivers, and OS are up to date and the game has necessary permissions over your security software. Please let us know if the problem persists on a new campaign after completing these steps and verifying the integrity of the game files through Steam.

 

[uçanbiblo]

As the asked information was not provided within 2 weeks, this thread is marked as solved. If the issue still continues, please update this thread.