Jump to content

False "save corruption" during gameplay


Ramagast

Recommended Posts

  • Replies 1.3k
  • Created
  • Last Reply

Top Posters In This Topic

I dont really know anymore what would cause it, its very consistent to happen during crafting in the matter of even accessing 1-2 menus, could be SkyUI affecting it who knows for me anyway. In all technicalities SKSE64 in beta might solve this issue if i upgrade from the 2.2 version to 5.1.

Link to comment
Share on other sites

I dont really know anymore what would cause it, its very consistent to happen during crafting in the matter of even accessing 1-2 menus, could be SkyUI affecting it who knows for me anyway. In all technicalities SKSE64 in beta might solve this issue if i upgrade from the 2.2 version to 5.1.

May have missed this in the massive compilation of this thread, but the issue is repeatable without SkyUI. But if you run 5.1 and still have issues then we still know it's not related to running an old version. The little time I've gotten to play with it, 5.1 still has the issue.

Link to comment
Share on other sites

Yeah, I believe in the 100 pages of trouble shooting, individuals have reported experiencing the issue, even with clear load orders - although it took a long time for it to present itself. Perhaps it is presumptuous to assume those reports were conducted with rigorous methodology (it's possible they still had some sort of modded files in their Skryim SE root/data directory).

While there are some more specifics, as to the cause the only thing we really have to go on is that increase in mod load order seems to expedite, or increase the tendency of the issue presenting itself. Given that, I thought it may have had to do with SSE Fixes, since it was explicitly meant to fix a strangely demanding increase in processing overhead from apparently redundant data processing as load order count increased, and since it isn't an ESP could be easy to overlook when testing an "unmodded" install... but that was quick to rule out by simply restoring the binkw64.dll loader and encountering the issue almost immediately. Perhaps something still in the save data itself that was generated while SSE Fixes was active during character creation? I guess I can try with a new character....

 

... huh... now, that's interesting...

 

Yup, nope. There is goes. Took 2 and a half hours. SSE Fixes was definitely not running. I suppose jury is out whether or not it is even any factor at all, but it certainly isn't the cause.

Edited by Guest
Link to comment
Share on other sites

Yeah if someone could verify that they did indeed get the corruption without any mods loaded or installed, that would be amazing, because then it solidifies my notion that its an inherent game engine flaw, and then Bethesda will then possibly look into it, and fix it. Of course, said flaw could also only be exasperated by loading a handful of mods, in which case the base game is then deemed a modded install, and that does NOT fall to Beth's responsibility, but the modders, at least in their eyes. And to that I actually agree. Someone trashes the whole code base with a mod, of course that's not Beth's fault. But until we can definitively prove it actually is the base game (only by running completely unmodded) will it then fall to Bethesda. All of my attempts to break the game with an unmodded install just ended in frustration.

Link to comment
Share on other sites

Yeah if someone could verify that they did indeed get the corruption without any mods loaded or installed, that would be amazing, because then it solidifies my notion that its an inherent game engine flaw, and then Bethesda will then possibly look into it, and fix it. Of course, said flaw could also only be exasperated by loading a handful of mods, in which case the base game is then deemed a modded install, and that does NOT fall to Beth's responsibility, but the modders, at least in their eyes. And to that I actually agree. Someone trashes the whole code base with a mod, of course that's not Beth's fault. But until we can definitively prove it actually is the base game (only by running completely unmodded) will it then fall to Bethesda. All of my attempts to break the game with an unmodded install just ended in frustration.

 

I'm assuming you mean on a clean save? By that I mean one that has never been modded.

Link to comment
Share on other sites

 

Yeah if someone could verify that they did indeed get the corruption without any mods loaded or installed, that would be amazing, because then it solidifies my notion that its an inherent game engine flaw, and then Bethesda will then possibly look into it, and fix it. Of course, said flaw could also only be exasperated by loading a handful of mods, in which case the base game is then deemed a modded install, and that does NOT fall to Beth's responsibility, but the modders, at least in their eyes. And to that I actually agree. Someone trashes the whole code base with a mod, of course that's not Beth's fault. But until we can definitively prove it actually is the base game (only by running completely unmodded) will it then fall to Bethesda. All of my attempts to break the game with an unmodded install just ended in frustration.

 

I'm assuming you mean on a clean save? By that I mean one that has never been modded.

 

Yes. Unmodded game, no mods active or installed, fresh game start, loading up the whole Bethesda logo and all from the very beginning, just like you got the game brand new and was loading it up for the very first time with no nexus or mods or anything.

 

I fought with this method several times (but never could really sit and do much for more than a couple hours at a time, so that may have effected the outcome) but never managed to get it to show.

Link to comment
Share on other sites

So, I don't want to issue yet-another-false-positive

 

But I believe relatively quickly it was identified that not one single mod was the cause here, as we compared load orders and saw no common denominator. And while that was excellent work by the community, it never sit well with me, because something corrupting the save architecture for runtime seems... well, too severe - especially since it persists through to main menu.

 

So similarly to my look into SSE Fixes as suspect, I am now pointing the finger at https://www.nexusmods.com/skyrimspecialedition/mods/245/? , and by extension the accompanying dll loader https://www.nexusmods.com/skyrimspecialedition/mods/3619/?. The latter might be particularly suspect as https://www.nexusmods.com/skyrimspecialedition/mods/8889/? also has been making use of the same dll loader.

 

Point is, all of these would escape comparing load orders, but if someone here can report they presently have a save/load order that uses NONE of the above, and still experiences the false save corruption, that would be helpful. Alternatively - since I redid my load order, anyone with a known "bad" save could try loading up with NONE of the above active and see if they can't A) provoke the bug on their current save B) load up a new character with the otherwise identical load order and see if they can not get the same results.

 

I had my load order completely overhauled testing some other things, so I do not have a known "bad" save to draw from to at least quickly confirm in 15-30 minutes whether or not this (might) not be a fix for existing characters. All I have is a revised load order (200+ deep), the has Achievement Mods Enabler, and xSHADOWMANx's DLL Loader removed (Skill Uncapper is loading via SKSE64).

 

Last point for comparison https://www.nexusmods.com/skyrimspecialedition/mods/1897/ . I do not personally suspect it - but the nature of this bug and failure to identify a common thread in load orders (esm/esp files) makes ANYTHING injected suspect, and I have used all of the above. Best option at this point is to look at known bad load orders and confirm whether or not some or none of these were ever used. If none... welp... crap.

 

 

EDIT: wow, this edit is really bad at parsing URLs. Yeah. I'm not going to try and fix these any more. Copy and paste.

Edited by Guest
Link to comment
Share on other sites

I do not, nor have ever had True 3D Sound for Headphones or the Skill Uncapper.

I DO however have Achievments Mods Enabler, and I believe two different DLL loaders. For all I know that in itself is a problem.

I might uninstall these and try without them. But I'm not going to redo my whole load order with a clean install without them. I'll also likely only test on my current save, not a new one.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...