Help with a Crash

[Guest]

So I've had to start new games 3 times now because of this issue and I'm getting sick of it. so basically add ANY mods mid playthrough not even bug fixes or even run LOOT without adding any new mods. it seems if there is any sort of minuscule change to my load order even if I restore it to how it was before, any saves I have will just crash upon loading. Has anybody had this issue before?

[Canaduh]

So, in simplest terms, you see the numbers in the right panel next to your ESPs? Those are reference locations for data when your game is running. Altering those locations on a game already in progress means there is data no longer accessible to certain mods. This does not go for all mods, only those that have masters, or other dependencies. Ultimately what this comes down to is DO NOT MOVE MODS MID PLAYTHROUGH UNLESS YOU KNOW WHAT IS AND ISN'T. Same goes for updating mods mid play, as basically mods are a package of references, being referenced by the parent mod, which is in turn a reference for the game. 

 

Unless you know exactly what you moved to where and the order of every mod in the LO before you altered it, you're SOL. You can try removing all mods with ESL dependencies, or loading the save with no mods, and making a clean save state, then turning everything back on, but you will have to clean all the scripts off the save first. TBH, this is far more work that it's generally worth.

[traison]

Probably SOS, it has a tendency to throw a fit when the load order changes. But, instead of speculating, create a log.

[anjenthedog]

Which manager are you using? If Vortex, I'd recommend that you avoid performing loot operations independent of the manager. It has its own built in loot, and afaik, standalone  LOOT and Vortex's LOOT do not always produce compatible results. Having said that, if you're one of those folks who's expert on LOOT, please ignore my remarks, as they'd not be germane. I mean for the bulk of players, myself included.

 

If you're using MO2, maybe that's a different story (idk), but as a general rule, you shouldn't be fooling with load orders unless you know exactly what you're doing, Let the managers handle the task. At least for Vortex, almost everything is handled quietly in the back ground, and even when a decision has to be made, it usually coughs out the right suggested hierarchy of overwrites (ie, you still have to make a choice sometimes, but it usually marks "the right" answer, so the decision is easy as pie). And I'm pretty sure that MO2 works much the same, or can be used similarly, even if I haven't used it m'self.

Edited May 31, 2023 by anjenthedog

[pinky6225]

4 hours ago, traison said:

Probably SOS, it has a tendency to throw a fit when the load order changes. But, instead of speculating, create a log.

 

My guess is this as SOS gets very grumpy if its load order changes mid game and you'll start seeing...

 

Unhandled native exception occurred at 0x7FF8ED16F1F9 (SchlongsOfSkyrim.dll+F1F9)

 

Assuming your on the correct version of skyrim to use it - https://www.nexusmods.com/skyrimspecialedition/mods/21294

 

Is very handy for crash logs

 

Also assuming that is the issue go into \Steam\steamapps\common\Skyrim Special Edition\Data\skse\plugins and cut the SOS .DLL file and stick on your desk top, load skyrim and the save and SOS will freak out (ignore it) and let everything load then make a new save, quit skyrim and stick the .DLL back in its correct place and your good to go on that save you made

 

The alternative would be to set up load order rules so SOS never moves its load order

Edited May 31, 2023 by pinky6225