Schlongs of Skyrim DLL CTD FIX

[DaddyDubstep13]

Schlongs of Skyrim DLL CTD FIX

View File

---

About a year ago I became super frustrated as to why the SOS DLL would crash my Skyrim if I changed load orders or downloaded new mods, so I spent literal days crawling through forum after forum trying to find a fix.

I found a super obscure comment from back in like 2017 that mentioned a problem very similar to what I was experiencing, and lo and behold I tweaked the steps and found out that it works flawlessly.

If you've been struggling with this problem, download this mod and follow the steps in the Text File. 

If this saves you a fuckload of headaches, please consider endorsing so other people can find this fix! ❤️

---

• Submitter
  DaddyDubstep13
• Submitted
  11/26/2021
• Category
  Adult Mods
• Requires
• Regular Edition Compatible
  Yes

 

[Erstam]

LOL, this problem is exactly what inspired my work on creating a dll-free version of Schlongs of Skyrim. I had installed new Creations, and could no longer load any save that was using SOS. NetScriptFramework told me that the crash was happening inside SchlongsOfSkyrim.dll, so my first idea was to hide the dll. However, even after reenabling it, my schlongs settings were all messed up, so I tried to work around the problem altogether.

[DaddyDubstep13]

1 hour ago, Erstam said:

LOL, this problem is exactly what inspired my work on creating a dll-free version of Schlongs of Skyrim. I had installed new Creations, and could no longer load any save that was using SOS. NetScriptFramework told me that the crash was happening inside SchlongsOfSkyrim.dll, so my first idea was to hide the dll. However, even after reenabling it, my schlongs settings were all messed up, so I tried to work around the problem altogether.

Dude honestly it's people like you that save the modding community.  I didn't realize how many people were running into the issues I was, which is kinda funny because there is literally ZERO documentation of how to fix it lol. I'm using your DLL less SOS right now and It's working like damn charm. This fix is for those who for whatever can't or wont update to your DLL, but I HIGHLY recommend that everyone download the file from Erstam.

 

Now... if you could fix Creature Framework to ACTUALLY properly equip schlongs that would be wonderful XD

[DaddyDubstep13]

1 hour ago, Erstam said:

LOL, this problem is exactly what inspired my work on creating a dll-free version of Schlongs of Skyrim. I had installed new Creations, and could no longer load any save that was using SOS. NetScriptFramework told me that the crash was happening inside SchlongsOfSkyrim.dll, so my first idea was to hide the dll. However, even after reenabling it, my schlongs settings were all messed up, so I tried to work around the problem altogether.

Also, theres an SOS Sexlab addon that is adds a feature that you can auto assign a Sexlab gender based upon the schlong. However it hasn't been worked on in ages and with SOS it will brick your scripts, if you would ever tackle that I would be so grateful. It makes it so much more convenient for Futa Npc's. I can assign the regular SOS and the Futa SOS to tell sexlab they are "male" for the animation, and my No Futa get's assigned as "female" The only problem is that it's not compatible with SOS now. I'd do it myself but I'm not super familiar with that coding, and last time I tried to use it whenever I tried to assign an armor as revealing it would CTD

[monty359]

7 minutes ago, DaddyDubstep13 said:

Dude honestly it's people like you that save the modding community.  I didn't realize how many people were running into the issues I was, which is kinda funny because there is literally ZERO documentation of how to fix it lol. I'm using your DLL less SOS right now and It's working like damn charm. This fix is for those who for whatever can't or wont update to your DLL, but I HIGHLY recommend that everyone download the file from Erstam.

 

Now... if you could fix Creature Framework to ACTUALLY properly equip schlongs that would be wonderful XD

I second that, great work with the SOS mod @Erstam. I also use your solution for collored SOS pubes for females. I hope, in future you can take a look at more mods with problems, that no one have been able to solve yet.

 

Crature framework is definitely that sort of mods. SLSeparate orgasm SE speed controll dll is another (you already commented on that one in another thread, but i still hope there is another solution possinble).

 

Thanks for your hard work

 

cheers

[ebbluminous]

Glad to see there are still heroes in the world!

[Erstam]

53 minutes ago, monty359 said:

I also use your solution for collored SOS pubes for females. I hope, in future you can take a look at more mods with problems, that no one have been able to solve yet.

If you use the Female Pubics mod, please override its SOS_Config script with this version. It integrates the changes from the new SOS with the color editing feature.

Script Override for PapyrusUtil SOS and Female Pubics mod.7z

 

As for fixing other mods you mentioned, I usually only work on mods that I personally use. So the chance is low, sorry.

[modball]

Thanks for creating this post.

 

I have been doing this for some time now (there is mention of this workaround on the .Net Framework common crashes page on Nexusmods) but good to have it more accessible on LL for SOS users.

 

Wish someone could find away to get rid of the slot 32,52 hassle entirely, particularly with followers, but I guess it would have been done by now if it were possible.

 

Cheers!

 

[DSAdam97]

There is a very simple workaround for the SOS dll CTD as stated here:
https://www.nexusmods.com/skyrimspecialedition/articles/3031

 

1) Clear Armors in the General Settings tab of SOS (wait a few secs if your modlist is script heavy) and make a save & quit
2) Temporarily rename/hide the SOS dll file from vortex/MO2 and load that save. You'll get an error message. Ignore this and make a new save & quit
3) Restore the SOS dll file and make whatever changes to your Load Order
4) load save #2 and it'll work as intended

 

If you mess up the order or forget to clear Schlongified armors, some SOS addons will permanently go missing (restore to save #1 and start over in this case). I've done this dozens of times on a 1700 plugin Load order, so it should work on any setup.

[2Dimm]

yeah... "fix"

 

i quickly downloaded this thinking someone was actually able to fix the issue and it wasnt going to be just the same workaround everyone has been doing since forever ?‍♂️

 

another """"fix"""" is to just never move anything related to schlongs of skyrim in the load order, with MO you can lock the ESP in the loadorder and freely move stuff before or (preferably) after it without breaking SOS

Edited November 27, 2021 by 2Dimm

[GaymerX]

Hello skyrim friend, this may be a stupid question for you and I'm really not angry with you if you just ignore me. I stopped playing skyrim two years ago because I only had one CTD after the other and it took away any joy of the game. Last month I reinstalled Skyrim SE with the current versions of SOS and Sexlab and in the whole six weeks to date I have not had a single performance problem and not a single CTD. So I don't know what your thread is about and what your patch is for. But I would like to know what your patch is doing.

[DaddyDubstep13]

To be clear for everyone, my file is not a patch. It was simply a set of instructions for anyone who had their Skyrim crashing due to the way the original SOS's DLL worked. It doesn't matter if you locked the load order for SOS, adding or removing ESPFE/ESL always had a chance to brick the game. I know, because they have been locked in my load order since I've had them lol, I just wanted a resource that people could reference in case they have ever run into the issue themselves.

 

Secondly, Erstam up above has created a DLL-less version of SOS, and it works fucking WONDERS. Highly recommend downloading it. I've been using it all afternoon with zero problems. 

 

The beauty of posts and "fixes" like this is that when people find them, they can easily read the comments and find a more permanent fix like what Erstam has done.

[agiz19]

10 hours ago, Erstam said:

If you use the Female Pubics mod, please override its SOS_Config script with this version. It integrates the changes from the new SOS with the color editing feature.

Script Override for PapyrusUtil SOS and Female Pubics mod.7z 20.19 kB · 34 downloads

 

As for fixing other mods you mentioned, I usually only work on mods that I personally use. So the chance is low, sorry.

Could you explain what this does? What issue does it fix? And also would like to know about your SOS version without DLL - can regular SOS be replaced on existing save and what are the benefits of this over DLL version besides that load order issue thingy?

[monty359]

10 hours ago, Erstam said:

As for fixing other mods you mentioned, I usually only work on mods that I personally use. So the chance is low, sorry.

 

Sorry, if i bother you with this, but do you use Apropos 2? If so, the Wear and Tear system works there on a per orgasm basis. Would it be possible to change that to on per act basis and take the sexlab stats and penis size into accout?

 

thanks anyway

 

cheers

Edited November 27, 2021 by monty359

[Tiress]

Do we really have to download a file to read a few lines? I appreciate the effort, but.. really? ?

[Erstam]

3 hours ago, agiz19 said:

Could you explain what this does? What issue does it fix? And also would like to know about your SOS version without DLL - can regular SOS be replaced on existing save and what are the benefits of this over DLL version besides that load order issue thingy?

The female pubics for SOS mod has a custom MCM script that allows the user to edit pubic hair colors. The DLL-free SOS version has edits to the same script, to invalidate the probability cache when certain settings have been changed (this cache helps to speed up schlongification in Papyrus). So the two mods would conflict. The file is a patch that includes the changes from both mods.

 

Pros of the dll-free version:

- works with AE as well as with previous SE versions (as long as the corresponding SKSE and PapyrusUtil versions are installed)

- no crash when load order changes

 

Cons:

- somewhat slower

- may still have bugs

Edited November 27, 2021 by Erstam

[gaps1]

OMG it worked, After all this time I have my saves back(I love you) Simple little thing like this was the problem all this time...Your the man.Thanks

[Bluegunk]

I was doing this anyway! But thanks for advertising.

Edited November 27, 2021 by Bluegunk

[DaddyDubstep13]

8 hours ago, Tiress said:

Do we really have to download a file to read a few lines? I appreciate the effort, but.. really? ?

Unfortunately due to how mod sites work, things like this only get attention if people "download" something. The algorithm reflects that unfortunately, so while I could've just made a post, most people would never have seen it, which means they wouldn't have an opportunity to see the fix that Erstam has done. An evil I don't like, but a necessary one to get eyes on solutions

 

Hopefully that clears up why it's a file.

 

Also, these steps are ONLY if for whatever reason you don't want to use Erstam's DLL-less SOS, but I cannot stress enough that you need to download it. It's fucking incredible

[ebbluminous]

28 minutes ago, DaddyDubstep13 said:

Unfortunately due to how mod sites work, things like this only get attention if people "download" something. The algorithm reflects that unfortunately, so while I could've just made a post, most people would never have seen it, which means they wouldn't have an opportunity to see the fix that Erstam has done. An evil I don't like, but a necessary one to get eyes on solutions

 

Hopefully that clears up why it's a file.

 

Also, these steps are ONLY if for whatever reason you don't want to use Erstam's DLL-less SOS, but I cannot stress enough that you need to download it. It's fucking incredible

Maybe make it a lot of lines to download? Then we'll be getting value for money lol

[DaddyDubstep13]

3 minutes ago, ebbluminous said:

Maybe make it a lot of lines to download? Then we'll be getting value for money lol

Hahahaha Just fill it with random info XD Nah, I kept it short and sweet, because to be honest the steps were pretty easy.  There was just little to no documentation on it. When I posted this same file on Nexus, I had a ton of comments from people who had no idea to fix the glitch XD. 

[4nk8r]

Nice to have a work around, and I'm not saying the DLL couldn't use some fixup to mitigate the issue, but you shouldn't really ever allow load order changes to occur after you start a new game.  This will always negatively effect previous saves to some extent, whether that results in a CTD or not.  Even if your game seemingly loads OK after allowing a shift, the damage might not become apparent until much later in your game play.  Always add new mods to the bottom of your load order when at all possible to avoid this issue.

 

You can also pretty effectively use blank plugins of an appropriate type (espfe, esp, esm, esl) as spacers to prevent your load order from shifting should you decide to remove a mod in the middle somewhere.  Wrye Bash can facilitate both empty plugin creation of the various types as well as keeping your load order intact.  WB has a feature to lock the load order and restore it should it shift, (creating a kind of history of previous load orders that you can roll fwd/bkwd thru).  The caveat is WB must be open and running to notice or record the historical placement.  Opening it after a load order shift will result in a popup about any changes and asking if you want to restore the last known order.

 

WB also displays the savegames mod load order, using color coding and a last:current kind of view to help you visualize what moved where.  Very useful in fixing a shifted load order.  If you decide to use Wrye Bash in this way, I recommend you don't use LOOT or any kind of plugin sorting features of MO2 or Vortex (especially Vortex's complex artificial dependency system it uses as a drag/drop sorting mechanism).  WB and Vortex will fight endlessly, otherwise.  I have no experience with MO2 in this regard, so you'll have to experiment if you want to do this.

 

I'm in no way suggesting to use Wrye Bash as an alternative to MO2 or Vortex...just another tool to use WITH either one.

 

20 hours ago, modball said:

Thanks for creating this post.

 

I have been doing this for some time now (there is mention of this workaround on the .Net Framework common crashes page on Nexusmods) but good to have it more accessible on LL for SOS users.

 

Wish someone could find away to get rid of the slot 32,52 hassle entirely, particularly with followers, but I guess it would have been done by now if it were possible.

 

Cheers!

 

 

The slot conflict is on purpose and allows SOS to exploit vanilla game logic to handle outfit conflict.  Without the slot conflict created by adding slot 52 to slot 32 items, you'd have genitals/pubes equipped 100% of the time, clipping thru your outfit and just looking silly.  SOS assigns slot 52 to all 32, AFAIK, not just some, so vanilla game logic handles immersive situations where equipping a full body/slot 32 item or equipping the genitals or even panties (often a slot 52 pelvis item) while wearing a slot 32 item would cause the genitals to clip thru.  Skyrim doesn't otherwise know those items should be mutually exclusive outside of pure 1:1 slot conflict.

 

This is where the keyword assignment comes in:  SOS_Revealing for slot 32 to allow slot 52, and SOS_Concealing for non-slot 32 items that should visually obscure slot 52 (some slot 49 cuisses in the more elaborate outfits visually obscure the crotch and would benefit from this, but it is more rare).

 

Ideally, outfits that are just a bra or other nipple/boob only covering, should not be using slot 32 (which Skyrim normally considers a full body, from ankles to wrists to neck).  They should use something like slot 46 or 56 (both considered chest items by game convention) without the reference body (the naked body) included in the outfit mesh.

 

More outfit creators could make their stuff more SOS-friendly by making underwear use slot 49, which is a secondary pelvis slot, though it is certainly more apropos that they use slot 52 and directly conflict with the genitals/pubes.

[modball]

7 minutes ago, 4nk8r said:

Ideally, outfits that are just a bra or other nipple/boob only covering, should not be using slot 32 (which Skyrim normally considers a full body, from ankles to wrists to neck).  They should use something like slot 46 or 56 (both considered chest items by game convention) without the reference body (the naked body) included in the outfit mesh.

Unfortunately the vast majority of bra/tops are set as 32 with the reference body/baseshape.

 

I understand the need for using a slot for equipping purposes and maybe it's just my set up, but I am frequently having to go into a followers outfit and remove and re-add the slot 52 item to get it to equip again, even though the slot 32 item is tagged in SOS MCM. Not an issue with PC, just followers.

 

Quote

you shouldn't really ever allow load order changes to occur after you start a new game.

Actually this would be a good warning to add to the description. For those of us who do this somewhat regularly, keep older saves and know the risks, it is fine (I would not do this with a play through that I intended to complete all the quests etc.) but you are spot on that you risk completely wrecking your game messing with the load order.

[4nk8r]

7 minutes ago, modball said:

Unfortunately the vast majority of bra/tops are set as 32 with the reference body/baseshape.

 

This can be corrected with xEdit (to create a plugin with altered slots) and Outfit Studio (to adjust the slots defined inside the outfit and ditch the reference body).  If there are Bodyslide files for the outfit, make the changes in the master NIF that produces the outfit vs. the final product.  PITA, but possible.

 

 

7 minutes ago, modball said:

I understand the need for using a slot for equipping purposes and maybe it's just my set up, but I am frequently having to go into a followers outfit and remove and re-add the slot 52 item to get it to equip again, even though the slot 32 item is tagged in SOS MCM. Not an issue with PC, just followers.

 

Actually this would be a good warning to add to the description. For those of us who do this somewhat regularly, keep older saves and know the risks, it is fine (I would not do this with a play through that I intended to complete all the quests etc.) but you are spot on that you risk completely wrecking your game messing with the load order.

 

I do often see the hole in the crotch of an NPC that is otherwise correctly ID'd as having a schlong.  I always suspected this as a side effect of Papyrus lag, either FPS related or just a delay in the checking for the SOS assignment.  Might also be an issue with NPC's that have predefined equipment by template.  AFAIK, vanilla game logic doesn't override an NPC's default equipment unless the new item has a higher armor rating than the old one.  Something to consider.  I could be off base.

 

I got annoyed enough with what you describe that I switched to SAM light (not the SOS version of SAM) over SOS for males.  I still use SOS for futa situations (I didn't activate any male addons in my load order).  Given that I'm not running 100% futa-fems, I feel this has less chance of suffering from any kind of script lag due to the volume of NPC's it might have to track/scan.  Not a perfect fix for everyone, but I'm satisfied with the result so far.

[modball]

1 hour ago, 4nk8r said:

PITA, but possible.

 

Yeah, it's not a question of how, but how many hours. I have changed the nif partition body parts and plugin biped flags in a few cases but have too many armor/clothing mods for this to be practical.

 

Quote

I do often see the hole in the crotch of an NPC that is otherwise correctly ID'd as having a schlong.  I always suspected this as a side effect of Papyrus lag, either FPS related or just a delay in the checking for the SOS assignment.  Might also be an issue with NPC's that have predefined equipment by template.  AFAIK, vanilla game logic doesn't override an NPC's default equipment unless the new item has a higher armor rating than the old one.  Something to consider.  I could be off base.

 

It's not a problem with missing sos meshes (plus I have sos no futanari set for all female followers) just the slot 52 clothing items will unequip randomly and is not equipping anything in it's place. Happens with vanilla and custom followers including a few of my own, which are pretty basic. Maybe related to NFF outfit management not playing nice with SOS slots but pretty sure I was dealing with this with vanilla inventory before installing that. I only keep a few items in vanilla follower inventory now (weapons, hair etc.) no slot 32 or 52 items specifically,

 

It's a minor inconvenience which I will likely have to live with