Schlongs of Skyrim SE

[Bushwalker2]

10 hours ago, Sandatharius said:

Error 1114 is an SKSE64 error that has to do with Skyrim SE game engine. If you have Engine Fixes installed, that can also be part of the error that the Engine Fixes can't resolve.

Yes, it started happening when I had to update SKSE from 2.0.17 to 2.0.19. Suddenly, SOS wouldn't load because it was deemed outdated. You're also correct that I'm using SSE Engine Fixes, but I don't know how to check if that mod is causing problems.

[Pfiffy]

7 hours ago, 4nk8r said:

AFAIK, you can't stop it, aside from not having it installed or hacking its scripts.  You can work with the keywords it provides, however.

 

Add the SOS_Revealing keyword on all slot 32 items that should also allow schlongs/pubes/bottoms/underwear to be visible when the "top" is equipped.

 

Underwear/bottoms should use slot 52 so it naturally "hides" the schlongs/pubes when equipped without having to add keywords.

 

If you have non-slot 32/52 items that need to obscure slot 52, like pants/stockings/cuisses or other crotch obscuring items that aren't already defined for slot 52, add the SOS_Concealing keyword to those items (or add slot 52 to the item).

 

You'll need to make your plugin dependent upon "Schlongs of Skyrim - Core.esm" to use the keywords.

 

Since the keywords are added to the Armor record for the part, if the item has a model for and is wearable by both genders, the keyword effects both.

Thank you. This really helped. I'm going to pm you if I have further questions. (I guess I will have a lot of them.)

[gnerd]

I'm not getting the ERF or normal addons

[jharise]

I can't get vagina collisions with any schlong, even with the SMP addon. Vagina collisions work with hands (and oddly enough, creatures), but not schlongs.

 

Anyone know what's up or how to fix this?

[Crate123]

Anyone know what causes this ? The only male mod I have is SoS and the skeleton I have set it to use is XPMSE. This doesnt happen for all males, but mainly named ones, random bandits and whatever generally appear proper naked.

[Yossarian22]

I got this problem about savegame data do not match the data from the SKSE co-save even though i have everything up to date. Can somebody please help me?

 

Thank you in advance

[Sandatharius]

8 hours ago, Crate123 said:

Anyone know what causes this ? The only male mod I have is SoS and the skeleton I have set it to use is XPMSE. This doesnt happen for all males, but mainly named ones, random bandits and whatever generally appear proper naked.

Check your load order and make sure that nothing is overwriting the XPMSE Skeleton. That is usually the case with what you're seeing in the screenshot. Or, update the XPMSE Skeleton to the most current version, if you are using a previous version.

[Crate123]

3 hours ago, Sandatharius said:

Check your load order and make sure that nothing is overwriting the XPMSE Skeleton. That is usually the case with what you're seeing in the screenshot. Or, update the XPMSE Skeleton to the most current version, if you are using a previous version.

Thanks for trying to help but XPMSSE is the most current version and nothing overwrites it, or the SOS files, for humans at least, Baka ABC overwrites it for most creatures but that should not impact the humans.

 

EDIT: Seems Men of Winter was the problem. Weird thing is, it didnt show as overwriting anything AND it was loaded earlier than both SOS and XPMSSE...

[Arken]

Hey guys sorry if this question is slightly OT, but I was having an issue with SoS being after XP32 in the load order and looking it up in this thread I solved the problem. But I wanted to ask you, as a rule of thumb is it smarter to keep XP32 a bit low in the load order to ensure compatibility? I ask because my thought was XP32 was better to be as high as possible so it would load first the skeleton and then the mods that are based on it, but when doing so for example SoS was working but not showing up in MCM.  

I know it's a bit of a silly question but keep in mind I use very little mods, basically only Sexlab related and some armors and graphics, so a general rule should be ok.

[Sandatharius]

4 hours ago, Arken said:

Hey guys sorry if this question is slightly OT, but I was having an issue with SoS being after XP32 in the load order and looking it up in this thread I solved the problem. But I wanted to ask you, as a rule of thumb is it smarter to keep XP32 a bit low in the load order to ensure compatibility? I ask because my thought was XP32 was better to be as high as possible so it would load first the skeleton and then the mods that are based on it, but when doing so for example SoS was working but not showing up in MCM.  

I know it's a bit of a silly question but keep in mind I use very little mods, basically only Sexlab related and some armors and graphics, so a general rule should be ok.

No, NOTHING should ever overwrite the XPM32SE Skeleton. For all body types, male skins, SoS, female bodies. It should always load AFTER everything of that nature.

[Just Don't]

6 hours ago, Arken said:

my thought was XP32 was better to be as high as possible so it would load first the skeleton and then the mods that are based on it

That's not how loadorder works, if a mods requires a certain plugin you have no option but load the required plugin before the plugins requiring it. That's not the case for most of the mods that use the XPMSSE skeleton. As these mods don't require the plugin, but the skeletons (hkx files) that it provides. Which takes me to the next clarification to answer your question: when you have several mods providing different skeletons the important part is the hkx files, not the loadorder. If you install the SOS skeletons they'll conflict with the XPMSSE ones, the loadorder for the plugins from SOS and XPMSSE have nothing to do with which hkx files will be used in game. Instead, the install order (if doing manual installs or using NMM) or the priority order you define (in mod managers like MO2 or Vortex) will determine which skeletons will be used in the game.

 

And generally speaking, you should keep the skeletons from XPMSSE, don't even bother installing the ones that come with SOS. And if you're using MNC you should let MNC overwrite XPMSSE as MNC provides better skeleton for creature types. That's it I think, I don't know of other mods providing skeleton files that are relevant.

 

[agiz19]

On 8/30/2020 at 5:04 AM, jharise said:

I can't get vagina collisions with any schlong, even with the SMP addon. Vagina collisions work with hands (and oddly enough, creatures), but not schlongs.

 

Anyone know what's up or how to fix this?

install Baka SOS SMP Patch , google it, its on bakas patreon freely avaliable

[jharise]

On 9/1/2020 at 5:16 AM, agiz19 said:

install Baka SOS SMP Patch , google it, its on bakas patreon freely avaliable

Thank you!

[LynErso666]

How in the WORLD has the Briarheart missing dick glitch, upon taking the heart out, never been solved!?

[4nk8r]

2 hours ago, LynErso666 said:

How in the WORLD has the Briarheart missing dick glitch, upon taking the heart out, never been solved!?

I'll see what I can whip up.  1st attempt didn't work.

 

What male body replacer are you using?  Briarhearts in my game don't end up nude when I take all their gear.  The bodysuit that has the hole in the cheast (there are 2, one for with heart, one without) includes the skirt/kilt/whatever the males wear.  Mine are never nude unless I issue "unequipall" on them, which also removes the "hole in the chest" bodysuit.  Makes them nude but lacks the chest hole.  Kali Ma.

 

Here's a patch for what, in my game, would be the Briarheart with and without heart armor records.  USSEP, if you have it installed, already flags them as slot 35 instead of 32.  I added the SOS_Revealing keyword to all the records I found.  Does nothing in my game for reasons I stated above, or I edited the wrong records. 

 

Dead_Briarheart_SOS_fix.esp

[Elysian97m]

I'm getting a dll error. Seem hard to fix.

[Just Don't]

19 minutes ago, Elysian97m said:

I'm getting a dll error. Seem hard to fix.

Make sure the SKSE version you have installed matches the one listed in the requirements.

[Elysian97m]

3 hours ago, dontknowdontcaredontask said:

Make sure the SKSE version you have installed matches the one listed in the requirements.

Where is the up - to - date dll?

[Just Don't]

5 minutes ago, Elysian97m said:

Where is the up - to - date dll?

SOS 1.1.4 (the current version) works for 2.0.17 and .18 / .19, there is nothing more up to date than that. If you're getting an incompatible dll warning you likely have a different SKSE version or didn't install SOS 1.1.4.

[Elysian97m]

 

1 hour ago, dontknowdontcaredontask said:

SOS 1.1.4 (the current version) works for 2.0.17 and .18 / .19, there is nothing more up to date than that. If you're getting an incompatible dll warning you likely have a different SKSE version or didn't install SOS 1.1.4.

I downloaded it and even reverted back to .17. Still a dll error.

[Just Don't]

17 hours ago, Elysian97m said:

I downloaded it and even reverted back to .17. Still a dll error.

I don't know which mod manager you use (fine detail to share when you ask for help), but as an example when I get an incompatible dll reported by MO2 I need to fix it, then launch the game as usual (skse loader through MO) in order to see if the incompatible dll notification goes away or not. This is because MO will check the last skse64.log to gather that info. So it could be that (listed in order of likelihood)

1. you have everything installed correctly but you're not attempting to start the game after fixing it.
2. you have multiple instances of the mod installed and some are old versions (applies to MO, perhaps to Vortex too).
3. Your installed SKSE version is not the one you think (you can quickly check in game by typing getskseversion in the console).
4. your mod manager is incorrectly detecting the sos dll as incompatible. 
5. you live in another universe where version checks and mod rules don't apply as we (in this thread) know.

[lacoka13]

For me, the npc's schlongs during animation when erect are bent to the side, what I mean is the dick itself is straight (not in an arc shape) but the tip point toward the side for about a 10 degrees angle, like its offset. XPMSSE (4.72) is overwriting SOS and loaded after SOS(1.1.4). I have searched everywhere but no solution so far. I've attached my LO if of any help.

loadorder.txt

[Sandatharius]

38 minutes ago, lacoka13 said:

For me, the npc's schlongs during animation when erect are bent to the side, what I mean is the dick itself is straight (not in an arc shape) but the tip point toward the side for about a 10 degrees angle, like its offset. XPMSSE (4.72) is overwriting SOS and loaded after SOS(1.1.4). I have searched everywhere but no solution so far. I've attached my LO if of any help.

loadorder.txt 2.37 kB · 2 downloads

When installing SoS, did you opt to use the SoS Skeleton by chance? If so, reinstall and opt out of using that one.

[Guest]

16 minutes ago, Sandatharius said:

When installing SoS, did you opt to use the SoS Skeleton by chance? If so, reinstall and opt out of using that one.

No, I left the sos skeleton box option unchecked, so  I can use xpmsse instead

[lacoka13]

6 hours ago, lacoka13 said:

For me, the npc's schlongs during animation when erect are bent to the side, what I mean is the dick itself is straight (not in an arc shape) but the tip point toward the side for about a 10 degrees angle, like its offset. XPMSSE (4.72) is overwriting SOS and loaded after SOS(1.1.4). I have searched everywhere but no solution so far. I've attached my LO if of any help.

loadorder.txt 2.37 kB · 5 downloads

Its like the dick can't completely return to its centered horizontal position at the start of an animation. Pressing "]" button or "u"  does not fix it. It happen to npc only and about 3/4 the time. My character is female. Other than that my setup works flawlessly.