Just some information on Skyrim se SOS Full Dll...

[Bullfye]

 

SOS dll cause for the CTD

 

 

Hey everyone

 

I was digging around an issue that I had now and than with the constant CTD  after normally changing my load order either cause installed a new Mod or cause installed an update of one, I was told that the reason for the Schlong dll failure was due to change is position in the load order, but today completely by accident I found the reason apart from the load order of the SOS esp file move on the load order there was something interesting that happened today ...

 

I installed a new version of a follower , and the Mod Autor advise to uninstall the old one and than install the new one, I have done so , but got 5 CTD on save game loading , I found this weird cause both old and new esp were flagged ESL so usually they do not count in the load order , I had my SOS esp and Addon locked in Mod organizer load order so that this way I could avoid them to be moved up or down after adding new esp mod files..

 

But I checked that and my SOS plugins were exactly in the positions in the load order I locked them so I was kind of scratching my head wondering WTF could be causing CTD, Thought corrupted mod ESP/ESL  from the follower mod but nope , installed the old one and still got the same CTD on save loading, the I remembered that the old follower esl file was above the SOS plugins in the load order and thought I new that ESL file do not count in load order I moved the Follower ESL file above , not to the same place but above SOS esp file..

 

The result was that the CTD vanished , the game loaded normally, Didn't know that esl files could cause the freaking sos dll to behave so mental , but now I do know ..

 

Any esp file or ESL one that you had in the load order if its bellow SOS esp file its ok if you use Loot for example and it moves your load order you better do as iI did , and lock your SOS plugins in the load order  and have a copy of your load order just in case , cause if you get this Netscript Framework error message and CTD you know that your SOS plug in was either moved or a esp that can be related to it that was above SOS was oved in the Load order..

 

Just to let you guys know this ..

 

Apparently even if you didn't used a follower that has an esp or esl file loading before SOS it will cause CTD if you move it for any reason later on...Loot can F... your game in a second on this matter, that is why you should always have a copy of the exact place SOS esp is on your load order and after using loot move the SOS esp file back to that position  also you now know that if any esp or esl file that is above SOS esp in the load order is moved  you'll get also a CTD...

 

 

Hope this helps people to know this to prevent starting the darn game every time you get a CTD cause the freaking dll starts going mental !

 

 

Salutes

[Mauserl]

You can tell Vortex to force SOS onto a specific plugin index, you can also disable SOS, do a clean save and reenable it.

[Bullfye]

10 hours ago, Mauserl said:

You can tell Vortex to force SOS onto a specific plugin index, you can also disable SOS, do a clean save and reenable it.

 

 

I stopped using Vortex long a go it was constantly screwing my game , I use  Mod Organizer that is by far a much more reliable  one !

[Bluegunk]

I'm not sure from your description, but I do know the SOS DLL will cause a crash if enough mods move about the load order, regardless of being ESP or the ESL-flagged ESPFE (pure ESLs sit with the ESMs).  ESPFE load order is as important as all the other mods. So if you move enough ESP and ESPFEs around, SOS will eventually notice and crash.  

 

If you use MO2, and .NetFramework you'll get a useful crash report specifying the SOS DLL has gone into error.

 

The trick is to use MO2's Hide function to hide the SOS DLL, and run the game. SOS will complain like fury but the game will start. Make a save. Unhide the DLL and you should be able to start the game again. SOS will retrace its add-ons and you are good to go. However, I usually force it to make another restart to make sure.

 

ESPFEs and ESLs do not count towards the mod limit of 255. But their positions in the load order do affect SOS if moved around.

Edited July 15, 2021 by Bluegunk

[Bullfye]

23 hours ago, Bluegunk said:

I'm not sure from your description, but I do know the SOS DLL will cause a crash if enough mods move about the load order, regardless of being ESP or the ESL-flagged ESPFE (pure ESLs sit with the ESMs).  ESPFE load order is as important as all the other mods. So if you move enough ESP and ESPFEs around, SOS will eventually notice and crash.  

 

If you use MO2, and .NetFramework you'll get a useful crash report specifying the SOS DLL has gone into error.

 

The trick is to use MO2's Hide function to hide the SOS DLL, and run the game. SOS will complain like fury but the game will start. Make a save. Unhide the DLL and you should be able to start the game again. SOS will retrace its add-ons and you are good to go. However, I usually force it to make another restart to make sure.

 

ESPFEs and ESLs do not count towards the mod limit of 255. But their positions in the load order do affect SOS if moved around.

 

 

Agree but netframework as I see it is rother useless and the info it gives its all but vague !....

 

About the load order I thought it would be needed just to mantain the SOS esp file in the same position in the load order but no , if by any reason you change the above SOS esp  files in that LO it can cause CTD... specially Followers esp or ESPFE or even ESL files... I tested it ... after find out ..and the result was CTD in 10 attempts to simulate the same thing..

[sofzx]

I was having this issue before. Got me a lot of headachess starting again thinking that my problem was another mod. When I install a new mod I just deleted the DLL. I wish there was a new version of SOS like the last update of sexlab  

 

 

[Bluegunk]

Well, all I can attest to is my experience where shuffling mods around in a load order will eventually cause the SOS DLL to lose track of its SOS Add-ons and crash the game while loading a save.  The .NetFramework crash report lists the DLL clearly at the very top of the report.

 

Hiding the SOS DLL and running the game, make a save and then re-establish the SOS DLL always solves it for me.

 

Good luck with your set up!

[jedi7000nathan]

I've had this same issue and it has destroyed numerous playthroughs of Skyrim for me: any advise for a Vortex user: I found MO too complex to use and having installed Vortex before the two kept alternating

[StrayHALO_MAN]

On 8/22/2021 at 8:37 AM, Bluegunk said:

Well, all I can attest to is my experience where shuffling mods around in a load order will eventually cause the SOS DLL to lose track of its SOS Add-ons and crash the game while loading a save.  The .NetFramework crash report lists the DLL clearly at the very top of the report.

 

Hiding the SOS DLL and running the game, make a save and then re-establish the SOS DLL always solves it for me.

 

Good luck with your set up!

Thank you so much for your posts, this helped me out alot.

I with SOS used esp names instead of form id to keep track of it's stuff lol.

[Gukahn]

On 8/23/2021 at 12:40 AM, jedi7000nathan said:

I've had this same issue and it has destroyed numerous playthroughs of Skyrim for me: any advise for a Vortex user: I found MO too complex to use and having installed Vortex before the two kept alternating

As above mentioned by @Mauserl

You can set a Rule so Sos keeps it's place. Almost every rule i have to make involving sos, i made sure it won't get overwritten by anything that don't need to.

@Bullfye made a sound advice tho, make a copy of your load order to always know how it looked like in a stable game before you change something major. That's true regardless of mod manager choice ?

 

Edited October 24, 2021 by Gukahn

[assassin394]

On 10/25/2021 at 3:54 AM, Gukahn said:

As above mentioned by @Mauserl

You can set a Rule so Sos keeps it's place. Almost every rule i have to make involving sos, i made sure it won't get overwritten by anything that don't need to.

@Bullfye made a sound advice tho, make a copy of your load order to always know how it looked like in a stable game before you change something major. That's true regardless of mod manager choice ?

 

Hi, how do you make a rule to force to forced SOS in place? I try to lock index in Vortex but the load order still change after I remove/install new mod and result CTD.

[Gukahn]

7 hours ago, assassin394 said:

Hi, how do you make a rule to force to forced SOS in place? I try to lock index in Vortex but the load order still change after I remove/install new mod and result CTD.

go in vortey to the plugin list, double click on the  mod you want to lock in, after that you get a window on your right where you can change it from sorted automaticly to locked to index. Afterwards you can give it a index number (you need to do that) . Be aware, I don't do that often, usually it does a good job in sorting stuff when you set your rules straight from the beginning. I never randomly crashed because Sos changed it's order tho, usually this indicates something else you did wrong or misunderstood ?

And it's not an all healing method ?

[assassin394]

39 minutes ago, Gukahn said:

go in vortey to the plugin list, double click on the  mod you want to lock in, after that you get a window on your right where you can change it from sorted automaticly to locked to index. Afterwards you can give it a index number (you need to do that) . Be aware, I don't do that often, usually it does a good job in sorting stuff when you set your rules straight from the beginning. I never randomly crashed because Sos changed it's order tho, usually this indicates something else you did wrong or misunderstood ?

And it's not an all healing method ?

That is exactly what I did but the esp still automatically change load order when I install/uninstall mods.( the index stayed the same but the load order number change). I don't have CTD problems with changed load order before either but it start happen a fews months ago and I have no idea why. The only thing I can do to avoid CTD is keep SOS esp at the same load order position. I have been manually moving esp below sos plugin every time I install a new mod to prevent sos load order change.

Edited February 11, 2023 by assassin394

[Gukahn]

18 minutes ago, assassin394 said:

That is exactly what I did but the esp still automatically change load order when I install/uninstall mods.( the index stayed the same but the load order number change). I don't have CTD problems with changed load order before either but it start happen a fews months ago and I have no idea why. The only thing I can do to avoid CTD is keep SOS esp at the same load order position. I have been manually moving esp below sos plugin every time I install a new mod to prevent sos load order change.

Can't you just make every new mod you install set to load after sos? ? It's kind of a strange problem you have here friend, I'm afraid I can just guess to help which ain't really helpful at all ?

[assassin394]

15 hours ago, Gukahn said:

Can't you just make every new mod you install set to load after sos? ? It's kind of a strange problem you have here friend, I'm afraid I can just guess to help which ain't really helpful at all ?

I don't know how to to that in Vortex/Loot. It depend on the mod, sometime the esp go above sos, sometime below. I have to manually check everytime.  Well, thank you anyway.

[FrancisThaPotato]

On 7/15/2021 at 11:37 AM, Bluegunk said:

I'm not sure from your description, but I do know the SOS DLL will cause a crash if enough mods move about the load order, regardless of being ESP or the ESL-flagged ESPFE (pure ESLs sit with the ESMs).  ESPFE load order is as important as all the other mods. So if you move enough ESP and ESPFEs around, SOS will eventually notice and crash.  

 

If you use MO2, and .NetFramework you'll get a useful crash report specifying the SOS DLL has gone into error.

 

The trick is to use MO2's Hide function to hide the SOS DLL, and run the game. SOS will complain like fury but the game will start. Make a save. Unhide the DLL and you should be able to start the game again. SOS will retrace its add-ons and you are good to go. However, I usually force it to make another restart to make sure.

 

ESPFEs and ESLs do not count towards the mod limit of 255. But their positions in the load order do affect SOS if moved around.

 Any clue how you could do this with Vortex ?

[Bluegunk]

3 minutes ago, FrancisThaPotato said:

 Any clue how you could do this with Vortex ?

Sadly I'm not a Vortex user. One solution that comes to mind is to look up the actual mod folder through Vortex, identify the SOS DLL and temporarily rename it DL0. 

Once SOS has regained its senses, rename it back to DLL.

 

Good luck. maybe a Vortex user can assist better.

[pinky6225]

3 minutes ago, FrancisThaPotato said:

 Any clue how you could do this with Vortex ?

 

You can set the rule by going to the plugin tab and clicking manage rules at the top and then selecting the plugin and saying must load after

 

(just picked one at random for the screenshot)

 

Although to be honest i prefer to just cut the SoS .DLL to desk top and load the save, make a save, quit and stick the .DLL back which also gets around the issue

[FrancisThaPotato]

2 minutes ago, pinky6225 said:

 

You can set the rule by going to the plugin tab and clicking manage rules at the top and then selecting the plugin and saying must load after

 

(just picked one at random for the screenshot)

 

Although to be honest i prefer to just cut the SoS .DLL to desk top and load the save, make a save, quit and stick the .DLL back which also gets around the issue

I just deleted it, loaded, saved and re-added it, worked well