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

[Domilexiste]

10 hours ago, 4nk8r said:

 

This is an old bug.  Experienced it with LE many years ago.  Your x,y,z coordinates were lost or invalid during the animation positioning, so the game put you at location 0,0,0.  You've probably been tampering with your load order...updating/adding/removing mods, haven't you.

 

If you can't get a clean in Sexlab to work, you can try a full uninstall of Sexlab, load without it, save again, re-add it to your game, but there may not be a way back for this savegame.  Maybe Fallrimtools Resaver might help with pruning out Sexlab from your savegame?  Odds are you're going to end up making a new game and starting over.  Install this mod at the same time if you do:

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

I know you really shouldn't do those things during a save but just to make sure do they normally cause that exact bug? Def not the worse problem I've had since it doesn't always kill me and reloading after dying is not a big deal since I have my settings set to save regularly because I don't trust this game at all with how random it can be.

 

I'll try making a new character soon and not touch anymore mods for a while and see what happens because the bug is pretty rare. Think in the last couple weeks I've had it maybe 5 times or less. so like in 60 hours of gameplay. At least the teleporting to that area doesn't cause me a crash.

[CommunistNinja]

6 hours ago, Sailing Rebel said:

If there are any mods overriding SL's scripts, such as Separate Orgasm, completely uninstall them.

I packed them all into a bsa. I'll extract them, leave them loose, see what happens, and let you know if it worked.

[Sailing Rebel]

19 minutes ago, agmoyer955 said:

Should this overwrite sexlab as well? Tried that as it was the only conflict and I couldn't find it under plugins to force it to load after everything else just incase. I also added the exclusion to I believe the correct folders and same crash after system clean is finished when it says like it's ready to be used.

 

PapyrusUtil is an SKSE plugin mod. It will not appear in the Skyrim load order. The override here is with the files, since multiple mods may be trying to provide different versions of the PapyrusUtil.DLL and scripts.

 

Yes, the stand alone PapyrusUtil should override SL. The idea is to avoid the issue of other mods that containing outdated versions of PU which are then overriding SL. And the easiest way to do that is to make sure this one version always has priority, regardless of the relative priority of other mods.

[4nk8r]

47 minutes ago, agmoyer955 said:

I know you really shouldn't do those things during a save but just to make sure do they normally cause that exact bug? Def not the worse problem I've had since it doesn't always kill me and reloading after dying is not a big deal since I have my settings set to save regularly because I don't trust this game at all with how random it can be.

 

I'll try making a new character soon and not touch anymore mods for a while and see what happens because the bug is pretty rare. Think in the last couple weeks I've had it maybe 5 times or less. so like in 60 hours of gameplay. At least the teleporting to that area doesn't cause me a crash.

 

This bug isn't a guaranteed side effect of shifting load orders, but if a mod moves in your load order it has to reinitialize in its new memory location on game start before it becomes functional.  The game doesn't go hunting for a mod's previous memory address in the savefile when your load order isn't in alignment with the savegame.  Scripted mods are always risky to move around because of this.

 

Once you start a game, never let your load order shift.  Never install new mods in the middle of your load order, only at the bottom.  This means mods that add ESMs, will force all non ESL mods to shift downwards in location as a result.

 

ESLs and ESL flagged ESPs only effect the memory location of other ESLs and ESL flagged ESPs because they all occupy the FE memory space, where as a regular ESM or ESP is able to use memory locations from 05 - FD.  Vortex refers to this memory location as the Mod Index in the Plugin view.

 

Plugins providing overrides (no new objects) don't cause much issue if they are moved around, aside from any mods they happen to displace as a result.

 

Use profile management when you want to try new mods in a playthru that would cause shifts in load order.  Start using Project Proteus.

[Domilexiste]

6 minutes ago, 4nk8r said:

Use profile management when you want to try new mods in a playthru that would cause shifts in load order.  Start using Project Proteus.

Thanks I'll look into that mod. Like I said the bug seems really small and not a real problem since it doesn't crash my game, stop another mod from working or anything close to that, just a small inconvenience.

[Tokyoghoul67]

12 hours ago, 4nk8r said:

@Tokyoghoul67 An extra tip for Vortex and Bodyslide, if you go that way.  Without Vortex running, add a new folder within the Vortex Staging folder structure, and call it something like Bodyslide_Output, then start up Vortex.  It's going to fuss about the rogue directory showing up and ask if you want to close it or accept the new directory.  Accept it and it will show up as a mod in the mod view.  Start Bodyslide and go into the Advance options in the settings and point the output folder setting to the new folder you created in Staging.  Anything you output from Bodyslide lands in the meshes folder within that folder.  Enable it and deploy like any other mod.  Any brand new files you add there via Bodyslide will require another deploy for them to appear in game, but anything that already exists that you overwrite again with Bodyslide does not require another deploy step (due to the hardlink association already established).

Ok, I had to keep Steam on my C drive because that is the only drive I have. I installed Vortex but there is no Vortex Staging folder at all with the new organizer. Should I download an older version of Vortex or keep the new version before I start adding any mods?

[4nk8r]

3 hours ago, Tokyoghoul67 said:

Ok, I had to keep Steam on my C drive because that is the only drive I have. I installed Vortex but there is no Vortex Staging folder at all with the new organizer. Should I download an older version of Vortex or keep the new version before I start adding any mods?

 

Are you using the Vortex Beta for Nexus Collections?  I have the most recent non-beta of Vortex, and it has a Staging folder system.  Click on Settings, then Mods.  It should be listed at the top.

[Tokyoghoul67]

22 minutes ago, 4nk8r said:

 

Are you using the Vortex Beta for Nexus Collections?  I have the most recent non-beta of Vortex, and it has a Staging folder system.  Click on Settings, then Mods.  It should be listed at the top.

Ok, I see it there. I was thinking that it was a folder that was located in the Skyrim folder on the hard drive. Also, Merry Christmas!

[Vyxenne]

 

On 12/24/2021 at 7:55 PM, Tokyoghoul67 said:

I'm computer stupid... When I downloaded the MO2 and installed the mods it put them somewhere which I thought was the correct place. [...] I guess you just have to be a computer whiz for this type of gaming huh???

 

On 12/24/2021 at 7:35 PM, 4nk8r said:

MO2 requires strict adherence to how it does its thing or you will suffer pain and frustration attempting to use it with all the other 3rd party utilities required to correctly mod Skyrim [...] Perhaps Vortex is more your speed?

 

Even its adherents agree that MO2 is more difficult to learn, and use correctly, than Vortex is. Since you have self-identified as a newbie ("noob") vis-à-vis mod managers, you might appreciate the less-challenging learning curve and more intuitive, more automated operation (if you enable/allow the automation) of Vortex, as 4nk8r suggested.

 

EDIT: Upon reading the rest of the thread, I see you have already done as 4nk8r suggested. Happy modding!

Edited December 26, 2021 by Vyxenne
Because her reply to an earlier post was later rendered moot

[Tokyoghoul67]

6 hours ago, 4nk8r said:

 

Are you using the Vortex Beta for Nexus Collections?  I have the most recent non-beta of Vortex, and it has a Staging folder system.  Click on Settings, then Mods.  It should be listed at the top.

Ok, it's not recognizing SKE64 and one other program. I'm going to call it a night and buy an external hard drive tomorrow. I also noticed on the other page with the framework that a few individuals stated that it needs to be updated so I don't know if that is also causing the issue. Have a good night and once again thanks for your help.

[pennyq]

So, I just did a clean install of sexlab 164b and have checked that the required mods are up to date multiple times. I get the attached error when I load my game and I can't load my game within the skyui mod manager. Game runs fine but I obviously can't use any animations. My game says it's out of date when I load in and if I go to the page where you'd usually load sexlab, it doesn't show checkmarks next to anything, even if I have things installed.

I've looked through this thread, but nothing that was suggested has worked.

Quick edit: it seems that it might be a JContainers issue, but I'm still reading through things.

Edited December 26, 2021 by pennyq

[Cross69]

can any one tell me why my sex animations don't auto finish i have to manual finish and i don't get the cum after 

[4nk8r]

3 hours ago, Tokyoghoul67 said:

Ok, it's not recognizing SKE64 and one other program. I'm going to call it a night and buy an external hard drive tomorrow. I also noticed on the other page with the framework that a few individuals stated that it needs to be updated so I don't know if that is also causing the issue. Have a good night and once again thanks for your help.

1. Open Vortex in MODS view.
2. Drag the SKSE64 zip to the Drop Files area at the bottom.  It should now show up as a mod in Vortex.
3. Mark it Disabled.
4. Double-click on the SKSE64 row in Vortex MODS view (most anywhere works).
5. A side panel should open up on the right.
6. Change Mod Type to Engine Injector
7. Enable and Deploy
8. In MODS view, click the folder icon and select Open Game Folder
9. Find skse64_loader.exe, right click on it and select "Pin to taskbar".  It is about mid way in the menu that shows up.
10. Launch Skyrim SE from the icon on your taskbar from now on (make sure Steam is running 1st).

Edited December 26, 2021 by 4nk8r

[xordevoreaux]

After the installation of SKSE and SKIUI, I wish there was one platform -- not an AIO but a single mod-- that handled every part of this functionality rather than it being scattered hither and yon across so many moving parts. 

[Dmetal2001]

it seems like sexlab's included animations are not registering if that is a possible explanation why the actors hump the air before standing still.. Not sure how to get them to register.

[danoid22]

Why does my SexLabFrameworkAE_v164b.7z downloaded 12-08-21 cause CTD on launch and SexLabFrameworkAE_v164b.7z uploaded 12-14-21, downloaded and installed 12-26-21 appear to work?  Is it different?  Why does it not have a different version number or some indication?

 

Or is it something else I did?

Edited December 26, 2021 by danoid22

[xordevoreaux]

3 hours ago, danoid22 said:

Why does my SexLabFrameworkAE_v164b.7z downloaded 12-08-21 cause CTD on launch and SexLabFrameworkAE_v164b.7z uploaded 12-14-21, downloaded and installed 12-26-21 appear to work?  Is it different?  Why does it not have a different version number or some indication?

 

Or is it something else I did?

 

I was getting a CTD from that same download, but I also have SoS, and the CTDs on using Debug (Target) in SL went away when I updated SoS to the latest AE version. SL doesn't crash now, but doesn't do anything, now, either.

 

[danoid22]

I had everything (SL, SOS, CPBC, SSE Engine Fix, PapyrusUtil, JContainers, etc) except NetScriptFramework and RaceMenu updated and was still getting CTD on start until I reinstalled SL with the 12-14-21 upload.  Now most everything works as expected.

 

Version numbers are important.  If it changed it should have received some sort of minor version number increment.

[Tokyoghoul67]

On 12/24/2021 at 8:26 PM, 4nk8r said:

If you're going to switch to Vortex, you can use Vortex to install all of your 3rd party utilities, and it actually integrates with FNIS quite well.  Bodyslide also should be installed and deployed like a mod into the game folder and run from links that point to the real game folder.  To take advantage of Vortex's hardlink deployment method (recommended), you need to make sure the Vortex Staging folder is on the same drive letter as where the game library resides.

 

Does Vortex itself have to be on the F drive or does it need to be on the C drive?

[4nk8r]

22 minutes ago, Tokyoghoul67 said:

Does Vortex itself have to be on the F drive or does it need to be on the C drive?

 

The Vortex application can be installed wherever.  The critical part is having the staging folder be on the same drive as the game folder so you can use hardlink deployment.

[4nk8r]

6 hours ago, xordevoreaux said:

After the installation of SKSE and SKIUI, I wish there was one platform -- not an AIO but a single mod-- that handled every part of this functionality rather than it being scattered hither and yon across so many moving parts. 

 

Nice thought, but completely unrealistic.  You're talking about the work of multiple mod authors, and not everything is directly related to each other in the way you're implying.  But then there's nothing stopping you from making your own single mod to rule them all.

[Electroraptor]

Hi there. I must to ask you, because I'm out of ideas where or how i can find the solution. Skyrim version is 1.6.342.0.8, SKSE version is SKSE64 2.1.4, SL version is the last one, 163.7. I'm almost sure it's caused by the newest version of Skyrim SE, but I didn't upgrade it, I simply decided to download SE right now from Steam. Is there any way how to fix it or any patch in development? Thanks! 

[chaimhewast]

10 minutes ago, Electroraptor said:

I'm almost sure it's caused by the newest version of Skyrim SE, but I didn't upgrade it, I simply decided to download SE right now from Steam. Is there any way how to fix it or any patch in development? Thanks! 

If you're on 1.6 (also known as AE) then you want Sexlab 1.64b.

[Electroraptor]

9 minutes ago, chaimhewast said:

If you're on 1.6 (also known as AE) then you want Sexlab 1.64b.

1.64b gave me a missing .dll's message (SKSE plugin loader). I'm afraid to solve this is beyond my skill. Do you want to guide me? I'll appreciate it. 

Edited December 26, 2021 by Electroraptor

[4nk8r]

18 minutes ago, Electroraptor said:

1.64b gave me a missing .dll's message (SKSE plugin loader). I'm afraid to solve this is beyond my skill. Do you want to guide me? I'll appreciate it. 

 

You and anyone having difficulties figuring this stuff out should downgrade to 1.5.97 and stay there until Bethesda calms down on the updates.  There is another already in the works that will break all the SKSE64 shit again.  It's been lingering in limbo for about 11 days now.  Not sure when it is going to finally be released, but it's going to be a brand new shitstorm that you're still not ready to handle.  Take steps to prevent Steam from updating Skyrim without your permission and keep a watch on the threads here for when it all settles down.