SKSE Co-Saves seem bloated

[Vyxenne]

I am still running game version 1.5.62 and SKSE64 2.0.12 due to all the issues and bugs in the latest HDT-SMP files for 1.5.73/2.0.15. I have no plans to update until everything I now use is updated, including HDT-SMP-SE.

 

In 2 months of playing since a New game start in Helgen, my ESS game-save files have grown to only around 5MB, which seems reasonable at Level 77, but my SKSE co-saves are running 56MB and creeping ever upward by a few KB with each new save. As a possible side effect of this bloating, it now takes 3-4 seconds for the game to make a save where in the past it was virtually instantaneous.

 

As info, I am running @ousnius genius SkyUI_SE Flashing Savegames Fix, which has completely stopped the insane "thumping" once per every 10 saves whenever I Saved or Loaded a game. However, there was no marked increase in my SKSE co-save size after I installed that patch, so I don't believe it could be doing anything except what Ousnius made it to do: stop the thumping.

 

Is 3-4 seconds to make a save and 56MB-and-climbing SKSE co-saves "OK?" If not, does anybody know how I can troubleshoot this?

[davisev5225]

This utility MAY be of some use to you, but I'm not sure if it is compatible with SSE or not.  Also, be sure to read all the directions very carefully before using it, so you understand what it does.

 

https://www.loverslab.com/files/file/3786-netimmerse-override-cleaner-skse-co-save-cleaner-utility/

[Sladen2019]

Are you overwriting your saves over and over ? Its best to always make new ones and to have all forms of auto save disabled.

 

Some theorize that using Form 33 plugins can help lead to save bloat. I do not know how true that is, but I always try to get mods in Form 44 when possible, or try to convert them myself to Form 44. I havnt yet noticed any abnormal save bloating, but I do use very few Form 33 plugins.

[phillout]

On 4/1/2019 at 10:02 AM, Sladen2019 said:

Are you overwriting your saves over and over ? Its best to always make new ones and to have all forms of auto save disabled.

 

Why would this matter at all? What SKSE does is clear from the code, common/IFileStream.cpp, 

 

That's it. Standard Windows API calls, such as  CreateFile(name, GENERIC_WRITE, 0, NULL, CREATE_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL);

 

CREATE_ALWAYS truncates the file if it already exists.

 

There is probably a mod at work here, generating tons of data for skse saves. I don't think guessing which one is going to help w/o the load order provided.