Bannerlord.Native/Mono and the new save system. (Bug?)

[Bunnyhop]

I'm not sure if this is strictly a proton issue, and it seems unlikely that a lot of people are running Native.exe amongst windows users - so given that:

The new save system seems to have broken saving in Bannerlord.Native.exe.
It works fine, still, in Bannerlord.exe using the net framework.

In the mono framework it will simply give a popup ingame saying unable to create save file.
A remnant 'whatever_name.tmp' "save" is created, it cannot be loaded.
Can someone on windows confirm/test whether this is solely an issue happening for wine/proton users or not? (run Bannerlord.Native.exe, in 1.4.2 Beta, make a new campaign/character, try to save)

[Bunnyhop]

Still happening after the latest hotfix, though I'm still not sure if this affects windows as well.

[Nyran]

Having the same issue using windows. Can't save since the patch, even auto-saves cause the 'Couldn't create Save file' massage to pop up.

[Bunnyhop]

Originally posted by shadowvampire93:

Having the same issue using windows. Can't save since the patch, even auto-saves cause the 'Couldn't create Save file' massage to pop up.

That's using

Bannerlord.Native.exe

? Or are you getting this launching it regularly (via launcher, which'll invoke Bannerlord.exe) (just to clarify)

And yep any save including the autosaves fail.

Bannerlord.exe works fine, though (but in this case it's particularly annoying since the current workaround for extremely long save times on linux via proton included using Bannerlord.Native for the full benefit).

[Nyran]

I've been using the launcher but went and tried using Native.exe which doesn't change anything only added bonus if I try to use the 'Load' menu with Native, instead of getting an empty menu the game crashes entirely.

[Bunnyhop]

As of current hotfix/patch (date of this post), this is still an issue, but I'd still like to get some verification/testing from more people?

Specifically:

Before this patch: https://www.taleworlds.com/en/News/354 (beta 1.4.2) which brought changes to the save system (compression rate), saves functioned normally and fine in both Bannerlord and Bannerlord.Native (the executables in the main folder, Bannerlord uses net framework, Bannerlord.Native uses win64 mono) with Proton/Wine.

After that patch, saves function normally with Bannerlord, but not with Bannerlord.Native (as if it's not updated to use whatever was upgraded/changed in the new save system related dlls?).

Bannerlord.Native cannot save anything, it fails on creating a save. It also cannot load saves made by Bannerlord main executable. It might be something which overlaps with other save failure bugs, but I'm specifically referencing this oddity which only started after the 1.4.2 patch.

To test (which would be very appreciated): If you can save normally using the regular executable, try running Bannerlord.Native (in the 1.4.2 Beta), and creating a new save/campaign, there. Post here if it fails, or succeeds. (whether you are on windows or using proton, I guess, which would clear up both if it's something only occurring with wine and if it's even more local - just some weird bug I'm having for some reason)