False "save corruption" during gameplay

[NuveroticMods]

I just wanted to wave at all the people having the same problem as me. I'll keep checking back to see if there's a fix.

I checked my papyrus log to see if any scripts were being injected constantly which would cause Save Bloat and sure enough,

 

stack:

[_Frost_System_Clothing (49064B04)]._frost_clothingsystem.RecalculateProtectionData_SKSE() - "_Frost_ClothingSystem.psc" Line 482

[_Frost_System_Clothing (49064B04)]._frost_clothingsystem.RecalculateProtectionData() - "_Frost_ClothingSystem.psc" Line 423

[alias _Frost_PlayerAlias on quest _Frost_MainQuest (49064AF8)]._frost_playerequipmonitor.ProcessQueuedEvents() - "_Frost_PlayerEquipMonitor.psc" Line 106

[alias _Frost_PlayerAlias on quest _Frost_MainQuest (49064AF8)]._frost_playerequipmonitor.ProcessQueuedEvents() - "_Frost_PlayerEquipMonitor.psc" Line 112

[alias _Frost_PlayerAlias on quest _Frost_MainQuest (49064AF8)]._frost_playerequipmonitor.OnObjectEquipped() - "_Frost_PlayerEquipMonitor.psc" Line 38

[05/13/2018 - 07:43:29PM] error: Unbound native function "IntListGet" called

[05/13/2018 - 07:43:29PM] WARNING: Assigning None to a non-object variable named "::temp62"

This is running a few times a second every second my entire game. It looks like Campfire is the culprate. Possibly Frostfalls fault trying to work with Campfire? I don't know. I hear Frostfall causes bloat, but Campfire never will.
I will remove Frostfall, Frostfall Seasons and Wet and Cold and let you know what happens. Begrudgingly I might add. I seriously don't want to remove ANY of those mods from my load order but, I spent the past 2 weeks getting about 2 hours of sleep a night, getting this 300+ mod load order working in game, and there's no way I'm letting one mod jeopardize it all now.

If that doesn't stop it, I will also remove Campfire.

By the way, if you don't play with Legacy of the Dragonborn, you're playing Skyrim wrong.

Edited May 14, 2018 by NerdsPlayhouse

[Gothpunk4Christ]

I've been keeping up with the (lack of) progress occasionally, and wanted to interject, if my memory serves correctly, papryrus logs will 1) always find a way to bloat, and 2) are a very poor method of determining stability of the game, or whats causing said issues. Unless you're having direct issues with CTDs or lockups, papryrus logs will usually never help. I dealt with this a while back with SoT causing a bunch of log spam, but my CTDs were result of something entirely different.

 

That being said, I don't run Frostfall, or campfires, or (sadly dropped) Convenient Horses, changed out EFF for IAFT, dropped a few crafting mods that added bloat to the crafting system that I ended up never actually crafting anyways, I tweak my Immersive armors at each new game in order to remove crafting menu bloat, take my time scrolling through crafting menus, and with those changes for the crafting menus, it has been some times since I managed to force the corruption, and have yet to have it happen in game after 5+ hours of continuous play.

 

There's a small section of comment posts on a mod, SSE Fixes, initial post

 

 

This is great, would it be possible to port/recreate the 65K string fix from ”Crash Fixes” ?

 

This should not be needed. I\ve discussed it with Markdf (who discovered it in the first place).

While you can go over the strings count in SSE, quitting an reloading the save that is corrupted will allow you to carry on as normal. So in other words, SSE must have its own fix.

 

*EDIT* I forgot to interject, that in all of my knowledge of software engineering and common sense, having to quit a program to get it to function properly again in a workaround at best, not a "fix" because a fix would mean that it completely resolves an issue (the corruption bug never occurs to begin with) and a workaround allows you to continue working after the problem does arise. So in short, NO, SSE does not have its own "fix." */EDIT*

 

There's a little followup stating the one person was able to push over 75K strings without issue and another posting his in game strings hits 64K and he has issues.

 

I'd link the original posts, but I hadn't figured out how and frankly am not in the right mood for human interaction right now.

 

Good day.

Edited May 24, 2018 by Gothpunk4Christ

[aers]

Hey y'all,

 

The root cause of this issue is that SSE's file loader is outright breaking under certain circumstances. This causes it to fail to actually read save files, which reports them as corrupted (essentially it thinks they're 0 bytes). This is also what breaks everything else - the game is trying to load those things on the fly (NPC dialogue etc) and failing to read anything.

 

Basically: It's not a specific script's fault and its not the fault of string count or anything in your save game.

 

Don't have a fix (yet?) but it will obviously require skse plugin.

 

Edit: file open failed due to too many files open, the reason it works again after restarting is the game is fresh.

[aers]

Try this

 

https://www.nexusmods.com/skyrimspecialedition/mods/17230

[AudieMurphy135]

Hey y'all,

 

The root cause of this issue is that SSE's file loader is outright breaking under certain circumstances. This causes it to fail to actually read save files, which reports them as corrupted (essentially it thinks they're 0 bytes). This is also what breaks everything else - the game is trying to load those things on the fly (NPC dialogue etc) and failing to read anything.

 

Basically: It's not a specific script's fault and its not the fault of string count or anything in your save game.

 

Don't have a fix (yet?) but it will obviously require skse plugin.

 

Edit: file open failed due to too many files open, the reason it works again after restarting is the game is fresh.

 

You're an absolute genius. Now I can finally stuff all 255 plugins hopefully without running into this god forsaken bug.

[calfurius]

Aers fixed the bug. GIVE HIM KUDOS BOYS!

[aers]

I verified it fixed it on my test setup that replicates it pretty much as soon as I start playing, but its pretty hard to test all the cases.

[lethielnyrond]

*basically explodes*

 

I KNEW it was an engine problem and not a mod conflict! HAH!! Take that, world!

 

aers, you are amazing. Thank you. This thread can now die in peace. And if you don't get unfeasibly large amounts of kudos for this, there's no justice in the world.

 

Lethiel

[spoonsinger]

*basically explodes*

 

I KNEW it was an engine problem and not a mod conflict! HAH!! Take that, world!

 

aers, you are amazing. Thank you. This thread can now die in peace. And if you don't get unfeasibly large amounts of kudos for this, there's no justice in the world.

 

Lethiel

 

You might just want to send a suitable memo to that JLeavey :happy: (It's only been a year+).

[BaronofHe11]

Holy moly I just posted about this in the technical thread. My search and google fu has failed me.