SexLab SE - Sex Animation Framework v1.66b - 01/18/2024

[Manperor]

12 hours ago, nefer385 said:

Yeah, I am having the exact same problem.  My character keeps equipping the Archmage robe (during sex scenes and even when I command a bathing scene via the Bathing in Skyrim mod).  So, I must have a specific mod causing that particular auto equip function/script to fire.  Weird thing is I don't even have the Archmage robes in my actual inventory, so it has to be a mod equipping that clothing during various scenes.  If I happen to find the culprit on my end, I will post it to you, in case we have the same or similar mod causing the auto equip.  I know that in my case my FNIS generated successfully prior to starting my new game, so I am confident that in my case it is a mod auto equipping my gear.

My player character has no such problem though, only NPC's.  I tried on a clean save but the problem persists; I also tried to uninstall all the newly installed mods after this problem appeared and still it wasn't fixed. I believe I am stuck here on this until all major mods for AE are out and go for AE.

[4nk8r]

2 hours ago, LewdZenn said:

 

I'm also experiencing CTD when loading a save, have you found any fix?

 

EDIT: Should I be letting Sexlab overwrite PapyrusUtils? At the moment I have SL being overwritten by it so maybe that's the issue?

 

That depends on what version of Sexlab and PapyrusUtils you're using together, as well as which version of Skyrim SE/AE and SKSE64.  Maybe if you read the description written on the PapyrusUtils page you might be able to connect the dots?

 

Some trivia...the developer of Sexlab is (at least in part) also the same as PaypyrusUtils...I know!!! Mind blown, right? Well...anyway.  I'll be going now.  Here's a link to help you figure things out.

 

 

In case you prefer NexusMods as a download site for PapyrusUtils:

 

https://www.nexusmods.com/skyrimspecialedition/mods/13048

Edited January 23, 2022 by 4nk8r
Changed inference on who developed what, as it was misleading 1st time around...

[Vyxenne]

22 hours ago, kukoricamorzsa said:

My Games\Skyrim Special Edition\SKSE\

My Games\Skyrim Special Edition\SKSE\ is not a legal Steam installation path for Skyrim Special Edition. If you are running a cracked game (pirated) that would explain all of the issues you are having. The root directory for your Steam Library can be on any drive and top-level directory, but it must eventually resolve to ..\Steam\Steamapps\common\Skyrim Special Edition.

 

Also, you apparently have no Data folder. The SKSE folder and pretty much all of the subdirectories you posted belong in ..\Steam\Steamapps\common\Skyrim Special Edition\Data and NOT directly in your Skyrim Special Edition folder.

 

Of course, if you are using MO2, nothing is "where it belongs," so disregard everything I just said- maybe someone who is familiar with that environment will jump in here and comment on your seemingly fatally-flawed path structures.

[fumos]

Seems the heel clear thing isn't working properly on Racemenu HH, anyone know a fix?

[freekoko]

hey, i should install the  163.beta9 or the framewok 163 normal for sse ?

 

Edited January 23, 2022 by freekoko

[dutchb]

anyone else having issues between the 2 lastest versions of sum and sexlab framework

[kukoricamorzsa]

Spoiler

 

 

I don't need any idiotic opinions ....

33 minutes ago, Vyxenne said:

Skyrim Special Edition

 

* it was an unnecessary and misleading comment ... since you didn’t read and or didn’t understand the previous conversation!   

 

------

Vannak akik imádják a saját dicsfényüket miközben a dolgok teljesem másfelé mutatnak arról tudomást se véve a színezett véleményért kommentálnak! Idióta...

 

[VeraDra]

3 hours ago, Vyxenne said:

My Games\Skyrim Special Edition\SKSE\ is not a legal Steam installation path for Skyrim Special Edition. If you are running a cracked game (pirated) that would explain all of the issues you are having. The root directory for your Steam Library can be on any drive and top-level directory, but it must eventually resolve to ..\Steam\Steamapps\common\Skyrim Special Edition.

 

Also, you apparently have no Data folder. The SKSE folder and pretty much all of the subdirectories you posted belong in ..\Steam\Steamapps\common\Skyrim Special Edition\Data and NOT directly in your Skyrim Special Edition folder.

 

Of course, if you are using MO2, nothing is "where it belongs," so disregard everything I just said- maybe someone who is familiar with that environment will jump in here and comment on your seemingly fatally-flawed path structures.

Guess I, and everyone else, is using a pirated version of the game.

 

But wait, maybe there's more to this?

 

Oh wait, there is!

 

 

"Documents\My Games\Skyrim Special Edition\SKSE" is a valid path, and is used to store plugin startup logs. As far as I can tell, there is no way to change this, nor is there any real *reason* to change it.

[kukoricamorzsa]

Oh ... god! Finally a meaningful manifestation!  
I've really missed one like this ...
... instead of the completely redundant and meaningless cuckoo ...  

 

---

Ó... isten! Végre egy értelmes megnyilvánulás! 
Már tényleg egy ilyet hiányoltam...
* az egyébként teljesen fölösleges és semmitmondó kakukk helyett...

[LewdZenn]

6 hours ago, 4nk8r said:

 

That depends on what version of Sexlab and PapyrusUtils you're using together, as well as which version of Skyrim SE/AE and SKSE64.  Maybe if you read the description written on the PapyrusUtils page you might be able to connect the dots?

 

Some trivia...the developer of Sexlab is (at least in part) also the same as PaypyrusUtils...I know!!! Mind blown, right? Well...anyway.  I'll be going now.  Here's a link to help you figure things out.

 

 

In case you prefer NexusMods as a download site for PapyrusUtils:

 

https://www.nexusmods.com/skyrimspecialedition/mods/13048

Can't tell if this comment is full of sass or if i'm just reading it that way, but I should've specified I'm on latest version of Sexlab for SE, posted on this page, and I have PapyrusUtils v3.9, that's on me. I've read that papyrsus page and was unsure if Sexlab had any changes/did anything different from the Papyrus v3.9, which is why I asked if either mod should be overwriting the other, since it isn't mentioned on that page. Also didn't know Ashal took part in creating PapyrusUtils, they aren't mentioned in the credits on the Nexus page, so thanks for that trivia.

Edited January 23, 2022 by LewdZenn

[Sailing Rebel]

52 minutes ago, LewdZenn said:

Can't tell if this comment is full of sass or if i'm just reading it that way, but I should've specified I'm on latest version of Sexlab for SE, posted on this page, and I have PapyrusUtils v3.9, that's on me. I've read that papyrsus page and was unsure if Sexlab had any changes/did anything different from the Papyrus v3.9, which is why I asked if either mod should be overwriting the other, since it isn't mentioned on that page. Also didn't know Ashal took part in creating PapyrusUtils, they aren't mentioned in the credits on the Nexus page, so thanks for that trivia.

Typical mod lists will give the standalone version of PapyrusUtil the highest priority in order to overwrite any incompatible versions distributed with other mods. This usually means it's overriding SL by default. Just make sure that the instilled PU version matches the installed SkyrimSE.exe version and that the appropriate Address Library is up-to-date.

 

Are Skyrim and all modding tools installed outside of Program Files and other protected areas of the file system? Accessing, adding or updating files in Windows-controlled folders (which SKSE mods will do regularly) can trigger security measures while the game is running which will lead to CTD.

 

Are anti-virus exclusions configured for the game folder, folders containing any modding tools, and the mod manager instance or staging folders? AV definitions in the last year have become very broad and aggressive, and now regularly scoop up modding-related items, preventing them from functioning correctly and leading to CTD. After adding new exclusions, it may be necessary to completely uninstall and reinstall any affected mods or tools, typically those with EXEs or DLLs. Ideally, exclusions should be configured before installing anything, even the game itself, but this is relatively new advice so many people will be stuck having to reinstall things if AV is the issue.

[4nk8r]

37 minutes ago, LewdZenn said:

Can't tell if this comment is full of sass or if i'm just reading it that way, but I should've specified I'm on latest version of Sexlab for SE, posted on this page, and I have PapyrusUtils v3.9, that's on me. I've read that papyrsus page and was unsure if Sexlab had any changes/did anything different from the Papyrus v3.9, which is why I asked if either mod should be overwriting the other, since it isn't mentioned on that page. Also didn't know Ashal took part in creating PapyrusUtils, they aren't mentioned in the credits on the Nexus page, so thanks for that trivia.

Sass, and I believe Ashal = ExiledViper on NexusMods.  But that might be a tinfoil hat moment for me...

 

There was a time when the stand-alone PapyrusUtil releases outpaced the one that was being bundled in Sexlab Framework archive, plus other mods, like Simply Knock and Frostfall (damn you, Chesko), like to include a version of PapyrusUtil DLLs to further confuse endusers, so making sure you are using the right version to match the other stuff you're trying to use is important.

[LewdZenn]

1 hour ago, Sailing Rebel said:

Typical mod lists will give the standalone version of PapyrusUtil the highest priority in order to overwrite any incompatible versions distributed with other mods. This usually means it's overriding SL by default. Just make sure that the instilled PU version matches the installed SkyrimSE.exe version and that the appropriate Address Library is up-to-date.

 

Are Skyrim and all modding tools installed outside of Program Files and other protected areas of the file system? Accessing, adding or updating files in Windows-controlled folders (which SKSE mods will do regularly) can trigger security measures while the game is running which will lead to CTD.

 

Are anti-virus exclusions configured for the game folder, folders containing any modding tools, and the mod manager instance or staging folders? AV definitions in the last year have become very broad and aggressive, and now regularly scoop up modding-related items, preventing them from functioning correctly and leading to CTD. After adding new exclusions, it may be necessary to completely uninstall and reinstall any affected mods or tools, typically those with EXEs or DLLs. Ideally, exclusions should be configured before installing anything, even the game itself, but this is relatively new advice so many people will be stuck having to reinstall things if AV is the issue.

Steam, Skyrim, and my mods folder are on separate SSDs than my main drive. I probably should've also mentioned that this crash only started with the recent version of SL. Never experienced it with previous versions. I haven't upgraded to AE/downgraded or anything, so nothing has changed about my setup on that front since using the previous versions of SL, all my skse plugins/dlls are still the matching SE versions-1.5.97.

Edited January 23, 2022 by LewdZenn

[3reaker]

36 minutes ago, LewdZenn said:

I probably should've also mentioned that this crash only started with the recent version of SL. Never experienced it with previous versions. I haven't upgraded to AE/downgraded or anything, so nothing has changed about my setup on that front since using the previous versions of SL, all my skse plugins/dlls are still the matching SE versions-1.5.97.

Yeah, that would be the problem, then.

 

SL 1.64c is only compatible with AE (SSE 1.6.x). If you are still on SSE 1.5.97 then you need to go back down to SL 1.63 and the corresponding version of PapyrusUtil that matches your SSE/SKSE versions.

 

While I can understand why you are staying on 1.5.97, you will find that that does mean that you also have to stay on increasingly old versions of many other mods as well.

[LewdZenn]

11 minutes ago, 3reaker said:

Yeah, that would be the problem, then.

 

SL 1.64c is only compatible with AE (SSE 1.6.x). If you are still on SSE 1.5.97 then you need to go back down to SL 1.63 and the corresponding version of PapyrusUtil that matches your SSE/SKSE versions.

 

While I can understand why you are staying on 1.5.97, you will find that that does mean that you also have to stay on increasingly old versions of many other mods as well.

I have v1.63 installed, I meant the most recent SE version that's back from November. I keep forgetting AE exists and I need to specify which version I'm on, but yeah, I dont have anything AE related downloaded or installed in my game. I'm only using SE versions of everything both Sexlab and normal SFW mods. I havent touched anything AE.

 

 

Edited January 23, 2022 by LewdZenn

[Sailing Rebel]

1 hour ago, LewdZenn said:

so nothing has changed

There in lies the problem: we are not in control and rarely informed of what and when things change in regard to AV and security. The silent updates in the background regularly add AV definitions, meaning that something that was ignored this morning might be considered suspect this afternoon. Short of doing without AV altogether, explicit exclusions is the only way to address this.

 

It is entirely possible that the issue at hand is not related to AV. But at this stage it should be thought of in terms of basic installation hygiene, along with install location, to eliminate potential problems.

[LewdZenn]

1 hour ago, Sailing Rebel said:

There in lies the problem: we are not in control and rarely informed of what and when things change in regard to AV and security. The silent updates in the background regularly add AV definitions, meaning that something that was ignored this morning might be considered suspect this afternoon. Short of doing without AV altogether, explicit exclusions is the only way to address this.

 

It is entirely possible that the issue at hand is not related to AV. But at this stage it should be thought of in terms of basic installation hygiene, along with install location, to eliminate potential problems.

I don't think the issue is AV related, but I'll see if flagging my mods and SE folder with exclusions changes anything.

[Sailing Rebel]

3 minutes ago, LewdZenn said:

I don't think the issue is AV related, but I'll see if flagging my mods and SE folder with exclusions changes anything.

A quick way to test is to temporarily shut down AV entirely and see if that helps.

[urophagia]

A note on the install instructions.

 

Quote

1. You should see a line that says "Reading SexLab..." if not you've done something wrong.
2. DO NOT ignore any warnings or errors you see in the FNIS window.
3. Activate the SexLab.esm file in your list of active mods.

This (at least for Mod Organizer 2) is wrong. You have to activate SexLab in order for FINS to see it and thus, Read it. Not selecting it first will cause FINS to not see or load it.

All that said i still cannot get animations to work. Im trying the methods outlined but none have worked so far.
 

[zarantha]

1 hour ago, urophagia said:

A note on the install instructions.

 

This (at least for Mod Organizer 2) is wrong. You have to activate SexLab in order for FINS to see it and thus, Read it. Not selecting it first will cause FINS to not see or load it.

All that said i still cannot get animations to work. Im trying the methods outlined but none have worked so far.
 

 

For MO2, the Sexlab mod (left side) must be active for FNIS to read it. The Sexlab ESM (right side) does not need to be active.
But activating the mod will normally activate the ESM, so ?‍♀️

[Manperor]

On 1/20/2022 at 10:37 PM, OsmelMC said:

That happens when you or some Mod add equip able items to the NPC after is already striped. Just find want Mod is adding or equipping a item at that moment and disable the mod or the option.

 

 

 

To be more clear, looks like some mod is detecting and using the SexLab event to equip the item that is trigging the redress.

I think I finally found the issue; the problem is gone after uninstalling some SPID related mod (Skill Based Muscle)

Edited January 24, 2022 by Manperor

[nefer385]

Interesting and unfortunate.  I too have that same mod, you may have figured out the culprit.  I am in the process of starting a new game, I will remove it from my load order as well.  Hopefully, that particular mod is the 'only' culprit in my setup.  As you mentioned earlier my play experience seemed to be a bit worse than your situation. 

[Johnbovnie]

Hi, I have been having a weird bug since I unequiped heels during a sex scene. Now everytime my character walk and stop she does a weird little jump. This also create problems during sex animations where actors randomly go up and down really fast every 4-5 sec. I tried reinstalling pretty much everything (skeleton, physics, sexlab and so on) but the problem is stilll there unfortunatly. I'd appreciate some insights if you guys have any ideas what could create such bug, thanks

 

ps: the bug persist with new game/saves  

[OsmelMC]

3 hours ago, Manperor said:

I think I finally found the issue; the problem is gone after uninstalling some SPID related mod (Skill Based Muscle)

I heard about that Mod, i think is enough with enable it just for the player. After all the issue is just with the NPC's

[Astarte29]

On 1/22/2022 at 9:12 PM, SerpentineStorm said:

I have to ask. I just installed Sexlab and a few associated mods (Sanguine's debauchery and Devious Devices) through Vortex. I already had FNIS and ZaZ up and running and they worked fine. But now my character is stuck in position. I can't use any movement anymore. I'm also getting a message as I start the game that Sexlab is outdated. All I found was the v1.63 one, I didn't find anything more recent. Looking at the date of posting here, I must be missing something obvious. But I have no idea what exactly. Can anyone help me out, please? I had these mods installed a while ago on the LE version of Skyrim. But I made sure to download only SE compatible mods, so that can't be the problem.

 

When i have a T-pose problem, it's usually an animation that has snuck in that is not SE compatible. 

 

My advice is to rerun FNIS, and carefully read the warnings-you'll need to track down the animation, and remove or convert it.