Need More Info Cannot Create Save Data

[Mama Luke]

I've already posted in another thread but this is so frustrating.

This only happens with my latest campaign that I started with 1.3 version of the game.
Disabled all the mods, loaded the game just fine. No crashes or anything, just can't save the game.
Previous campaign that started with 1.2 and has the same mods that I'm using with my latest campaign got no problems whatsoever.
Starting a new campaign, I can save also.

But with this latest campaign I can't save. I have 2 seperate save games from this playthru, 5 hours apart from each other. None of them can save the game. If I hadn't closed the game, there would be no problems it seems. Should I run the game 24/7? I don't understand.

 

[greggho]

submit your latest (unmodded) save file in any playthru for the devs, please?

 

[Mama Luke]

Well it's modded from the start. But I don't believe it's because of the mods, because my other campaign with same mods loads and saves just fine.

 

[greggho]

I know what you're saying - but we need to provide a non-modded save file for the devs.

I have been experiencing this issue for a long while now; it happened even with an unmodded save file, which I just nuked and moved to the (then) beta 1.3 update - I didn't realize that "Save Failed" message would haunt me so many more times, LOL... otherwise I'd be quick to document it and send a save file for debug.

What I can safely say is that mods DO make this issue more prevalent - and nary impossible for the devs to figure out what's wrong with THEIR code and not modders' code :\
You can take a look at some of my other posts on this matter if you will, but, so far, all I know is your save file is doomed and likely any other recent saves will also snag on this issue down the road :\\\\\

 

[Kadath]

It seems (emphasis on *seems*) a save bug perhaps related to save bloating. As the size of the save file increases, so does the risk of encountering the save bug, and this would be why the frequency of this bug increases with the number of mods you are running. It happens in unmodded games too, just more rarely (and usually, on average, much later in the campaign). In my case, it always - always - begins to appear after a week or two, but I do indeed play (I honestly couldn't otherwise, given the state the game is in) with quite a high number of mods.

Apparently though, the Community Patch guys have identified it and are working on a fix (at least this has been reported by the Tournament Xpanded mod author, whose work has for quite a while been wrongly blamed for the issue), so IF they manage to solve it we'll both have a solution and TW will be informed of what they have to fix on their side as well. Of course, if someone encounters it in a vanilla game without mods (and it's not any silly antivirus issue blocking the save folder), yes, please send it to the devs so they can work on it.

For the time being we can only wait.

 

[Mama Luke]

Yeah that seems to be the case. Both of my "broken" saves are around 70mb while the other saves that have no issues are under 60mb.
I have no idea why these saves are blotated that much. I'm only 80 days in. On my other campaign I'm around 1400 days in, running the same mods, but it's size is 57mb and it runs without any issues.

 

[greggho]

latest post by the Devs on the future of SP/Engine mentioned "cleaning up saves" etc., so I'd wager they're onto something already...

 

[Kadath]

Yup, my saves start giving that problem at around 65mb+ too. I also had the feeling (but it could be just a coincidence) that savescumming might be a part of what causes the bloat (and would further explain why several people first linked the issue to the tournament mod): in the first weeks of the game I usually go on a tournament spree to quickly make some cash, which implies quite a bit of reloads when the matches don't go my way. Perhaps reloading the game without going back to the menu/quitting the game altogether (or, again, saving and loading a game inside a city instead than on the general map) fails to clean everything it should from the "cache", which gets incrementally added to the next saves. That could explain why I tend to get to those sizes so quickly in a fresh campaign.

It's just speculation though, but judging by the very different feedback from people there could be a playstyle variable like this one in play (and "cleaning up saves" does indeed sound possibly related). I seriously hope a fix isn't too far, 'cause as it stands now I've just shelved the game waiting for when I can finally invest in a long running campaign.

 

[Mama Luke]

Curious thing is, like I said I was able to save before I quit the game. The save file was already around 70mb at that point and I was able to create a new save when I was still in game. But something got ****ed up after I quit and I'm now unable to save with the same file that I've originally created another save from .
I hope this gets fixed soon.

 

[Ehanoc]

Just as a note. Saves take a lot of space and... if you configured in Steam a different installation drive rather than C: , the game will go into that drive but the game saves will ALWAYS go into C: . It seems to be hardcoded ....

This happened to me as well because the C: folder was full

 

[Kadath]

Just as a note. Saves take a lot of space and... if you configured in Steam a different installation drive rather than C: , the game will go into that drive but the game saves will ALWAYS go into C: . It seems to be hardcoded ....

This happened to me as well because the C: folder was full

There's a lot of silly possible oversights like that that can happen, but what we're talking about is another thing that's inherently part of how the save system works, it just gives the same message as when a save can't be created because of disk space, folder authorizations, antivirus softwares etc. We can freely load and save other or new campaigns, which completely rules out any of these system related issues, it's that specific playthrough and its latest saves that get borked.

BTW, @Mama Luke, now that I think of it, quitting the game might really have a part in this. As stated my playstyle involves quite a bit of reloads, and I've noticed that (just like in Warband... come on, TW!) reloading saves seems to cause what looks like a pretty serious memory leak. By the 8-10th reload (more or less, at least with my specs, I guess mileage may vary), performance begins to get noticeably worse (up to the point of garbling the music on the loading screen), and that's when I quit and restart the game. I've had the bug happen with no restarts whatsoever (suddenly it starts popping out when an autosave begins to fail, and that's when there's no turning back), so it can't be the *only* cause, but indeed the last time I had it the game saved fine (or at least apparently so, quite obviously something got corrupted), then I immediately quit because the game needed a restart, and since then that game cannot be saved anymore, even if immediately after having been loaded, without moving or doing anything else.

In any case, the new version of the Community Patch just came out a few hours ago, and no news in the save system department. So heh, still waiting for some good news ¯\_(ツ)_/¯

 

[Mama Luke]

Something odd happened today.
Started a new game (used Character Export/Import and Editlord to fast forward me to broken save's progression ) , everything was going good. Joined Battania as a mercenary, made a new save and quit the game.
Checked the save folder to see everything's alright, But nah, I have another 70mb save and sure enough game won't save anymore. But my other save just after joined Battania is still 35mb so I was able to recover my progress. Two saves are just 3 in game days and around 25 minutes apart from each other. One is 35mb and other one jumped to 70mb somehow.
So I continued with 35mb save, did the same exact things (more or less, fought two battles, donated some prisoners, smelted some weapons etc), but this time file size stayed stable.

So the problem is definitely file size but what causes it to jump, I have no idea. I tried to recreate by doing the same things but it didn't happen again (probably will happen as I play more though).
I'm playing with save folder open in the other monitor right now to check the file size everytime i save the game . This is ridiculous.

 

[hampton24]

I want to second Mama Luke's observation about the file size issue. Since they mentioned this being a possible issue I keep open the save game folder on a second monitor to check the file size as I played and save.

I got about 180ish days in with mods, when I went to save the game and the file size jumped from 39mb to 78mb. I then quit the game and restarted the 78mb save game and could not save. I then got a backup save that was about 20 minutes older and tried doing the same activities and no issues and the save game was still 39mb and I was able to continue the game.

I would suggest if you have dual monitors to have the save game folder open to keep an eye on the file size as you save and to have at least two save files that you alternate overwriting you game to so you do not lose too much time if this issue pops up.

 

[Crazy_Man]

I'm on the 1.4.0 hotfix and i get the same issue.
I got the Community patch so after i got the "Cannot create save data" message with First Chance exceptions enabled i printed diagnostics and got the exception in the end of the post.

Both the autosave and the corrupted save had almost doubled in size from 43 MB to 84 MB.

I had gotten this error earlier too so i am saving in a new file each time instead of using the same over and over again.
I'm also mitigating with the Better Autosaves mod

Recorded First Chance Exceptions:
1. System.NullReferenceException: Object reference not set to an instance of an object.
at TaleWorlds.Library.Extensions.GetDeterministicHashCode(String text)
at System.Collections.Generic.ObjectEqualityComparer`1.GetHashCode(T obj)
at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
at TaleWorlds.SaveSystem.Save.SaveContext.CollectObjects(Object parent)
at TaleWorlds.SaveSystem.Save.SaveContext.CollectObjects()
at TaleWorlds.SaveSystem.Save.SaveContext.Save(Object target, MetaData metaData)

 

[Crazy_Man]

I managed to reproduce it twice in a row by reloading a save and enter the smithy. There i had some weapons to smelt down.
Note: I am using the mods "Smith Forever" and "Improverd Smithing UI". The first one makes stamina irrelevant and the second gives me a smelt all button which i use.
In the smelting menu i go and spam the "smelt all" button until everything is gone, and then i go back to the town menu and save. It'll take a bit longer to save than usual(probably because of the amount of extra data being saved) and after that the game is corrupted.

If you load the save after this you can't save anymore.
Loading and saving other saves works fine without having to restart the game.

@Mama Luke Do you use similar smithing mods?

 

[Baki667]

I managed to reproduce it twice in a row by reloading a save and enter the smithy. There i had some weapons to smelt down.
Note: I am using the mods "Smith Forever" and "Improverd Smithing UI". The first one makes stamina irrelevant and the second gives me a smelt all button which i use.
In the smelting menu i go and spam the "smelt all" button until everything is gone, and then i go back to the town menu and save. It'll take a bit longer to save than usual(probably because of the amount of extra data being saved) and after that the game is corrupted.

If you load the save after this you can't save anymore.
Loading and saving other saves works fine without having to restart the game.

@Mama Luke Do you use similar smithing mods?

same issue here (but not sure if mods are causing this). Using none of your mods but "SmithingHideUnknown"

 

[Mama Luke]

@Mama Luke Do you use similar smithing mods?

I'm also using Improved Smithing UI and Bannerlord Tweak's "Hide Locked Weapons" feature is also on.
But I haven't been able to spot a pattern regarding double sized save games. Just after using "Smelt All" function for example, or something similar. It's happening pretty randomly for me.

 

[Radimov]

I never had this issue and already played 3 different stable versions, im currently on 1.4.0. I am posting here because i had an issue where it would freeze my whole PC at random points and i had to do a reset to comeback, all my Temps are good, no OCs or such so... the only way i found to fix this was by removing the Mount and Blade folder and verify the files with Steam, until now i had 0 problems, this issue might be from the same source as mine was? like going to several updates/versions and at some point creates these crashes/bugs. I never installed mods.

 

[yuzhno]

I had this "cannot create save data" error a few times with different mods. Trying to isolate the issue I started a vanilla campaign and played for a while, with no corrupted saves. Now adding a few mods, and my current suspect is Smithing Hide Unknown. Also saw this error mentioned in Improved Garrisons discussion.
It's possible that Smithing mods don't break the save by themselves, but allow the player to flood the market withn crafted weapons made for sale, and that triggers some bug in save system.

 

[uçanbiblo]

Hi all, i see almost everyone experiencing the issue have installed mods in their game. Please keep in mind that we can not offer support for the modded game. If you can reproduce the problem after removing the mod files and verifying the integrity of the game, please let me know.