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

[Vyxenne]

14 hours ago, logiczinc said:

I found Matchmaker Light but cannot find the regular for SSE.

Install Oldrim Matchmaker. Matchmaker Light is only for SexLab Light and SoS-Light.

 

There is no SSE conversion of Matchmaker available, nor is it required that you convert it- the Oldrim mod works just fine in SSE "as is."

[Vyxenne]

10 hours ago, shebop said:

hopefully you are using MO2 or something similar (such as Vortex).  This is because you cannot keep the extracted files separate from files in other mods without MO or Vortex.  Looks like you are using NMM... so you will have to mix them up I guess.

This is absolutely untrue. NMM tracks which mod installs what files, and which files are overwritten by other mods' files, even when those files are mixed with other mods' files in the same folder, so it is always very simple to uninstall or update any mod that goes into or below the Data subfolder - which is 99.9999% of all mods - irrespective of where its files are in the game installation.

 

It's fine that everybody here seems to prefer the complex to use and unintuitive MO , but please don't post misleading statements about NMM to further your personal preference.

[fred200]

1 minute ago, Vyxenne said:

This is absolutely untrue. NMM tracks which mod install what files even when those files are mixed with other mods' files in the same folder, so it is always very simple to uninstall or update any mod that goes into or below the Data subfolder - which is 99.9999% of all mods - irrespective of where its files are in the game installation.

 

It's fine that everybody here seems to prefer the complex to use and unintuitive MO, but please don't post misleading statements about NMM to further your personal preference.

I have to say - NMM is the only mod manager that puts mods directly into the game directory. MO uses virtualization and Vortex uses hard links.

 

[Vyxenne]

1 hour ago, fred200 said:

I have to say - NMM is the only mod manager that puts mods directly into the game directory. MO uses virtualization and Vortex uses hard links.

Yes- and this "intuitive" placement makes it child's play to (for example) find a particular outfit mesh in Outfit Studio to add physics bones to it, then batch-build it in Bodyslide without having to know (and tell Bodyslide) the arcane, twisted path where MO has hidden the meshes. This straightforwardness is (to me) the biggest single advantage to NMM- you don't need a 4-year degree in "Mod Manager" to use it, and after you have used it you can find the files in the expected, standard places rather than tucked away in profile folders that bear no relationship whatsoever with where the files are supposed to be.

[fishburger67]

15 hours ago, GaymerBlue said:

Does Sexlab Aroused not work with this? Whenever I enable sexlab aroused mod my game won't open. ( load order attached)

Yes, Sexlab Aroused SSE works.  You can get it from here:

 

 

[HumbleKarp]

So, I've tried my best to avoid having to ask for help on an issue with this mod but Iv'e been googling for a couple days now and have found nothing on the issue. 

Im currently using SkyrimVR and I have the majority of things working, including SkyUI. I have the MCM showing up and what not, and the SexLab menu does show up, however- any time i click the install button I'm greeted by a "working", so i close the menu, the few bits of animations being installed scrolls by, then i get the "sexlab 1.63 etc" is ready. 
I then go back to the mcm menu for SL and find that it wants another install, then another, then another, and so on. It seems to consistently not want to install. Has there been something found out about this issue that i just didnt happen to come across? I had seen a few others with this issue but the only suggestions they got were "dont use SL light" or "you have to close the menu".

I have up to date SkyrimVR, sksevr, skyui, and skse64. As well as the main file and hotfix for SL, installed in the correct order. 
I have skse64 and sksevr because from what i found, you need to launch the game with sksevr but you need skse in order for loot and other programs to detect it correctly when it tries to compile and find errors or missing masters, all this is considering majority of the mods ill be using are SE mods.

Any help would be great o7
 

[Vyxenne]

58 minutes ago, HumbleKarp said:

So, I've tried my best to avoid having to ask for help on an issue with this mod but Iv'e been googling for a couple days now and have found nothing on the issue. 

Im currently using SkyrimVR and I have the majority of things working, including SkyUI. I have the MCM showing up and what not, and the SexLab menu does show up, however- any time i click the install button I'm greeted by a "working", so i close the menu, the few bits of animations being installed scrolls by, then i get the "sexlab 1.63 etc" is ready. 
I then go back to the mcm menu for SL and find that it wants another install, then another, then another, and so on. It seems to consistently not want to install. Has there been something found out about this issue that i just didnt happen to come across? I had seen a few others with this issue but the only suggestions they got were "dont use SL light" or "you have to close the menu".

I have up to date SkyrimVR, sksevr, skyui, and skse64. As well as the main file and hotfix for SL, installed in the correct order. 
I have skse64 and sksevr because from what i found, you need to launch the game with sksevr but you need skse in order for loot and other programs to detect it correctly when it tries to compile and find errors or missing masters, all this is considering majority of the mods ill be using are SE mods.

Any help would be great o7
 

Loading two copies of SKSE64 is bound to cause issues. Also, I suspect that only the last one you installed is active since it overwrote the first one. I'd bet that the version of SKSE64_loader.exe you're launching the game with doesn't match the version of SKSE64 that is active. Also, you might want to count the number of SKSE64 scripts installed- SKSE64 has 61, don't know how many SKSEVR has, but if it's not 61, and if any of them are not named identically to their SKSE64 counterparts, you will have two versions of SKSE64 scripts installed.

 

I'm not a world-famous expert, but I'm almost certain that having two versions of SKSE installed at once can't be good.

[HumbleKarp]

Thank you for the help, i removed the skse64 and any files relating to it, removed all other mod files, verified my files, and re installed everything again. I'm still having the issue even with the sksevr only. So now ive got to see if someone has a solution for the same problem except now I have only one skse.

Oof lol

 

Also when you're referencing the 61 files, are you saying that even with just the sksevr installed, it needs to have the exact same names and script count as the skse64 does for the vr version to work with SE mods? Im guessing that answer is no, otherwise making the vr skse would be pointless. But you never know ?

[Vyxenne]

25 minutes ago, HumbleKarp said:

Also when you're referencing the 61 files, are you saying that even with just the sksevr installed, it needs to have the exact same names and script count as the skse64 does for the vr version to work with SE mods? Im guessing that answer is no, otherwise making the vr skse would be pointless. But you never know ?

Not 61 "files" per se- SKSE64 has 61 SCRIPT (*.pex) files in Data\scripts- starting (alphabetically) with activemagiceffects.pex and ending with wornobject.pex. The "right way" to install them is to extract the SKSE64 archive and then zip up the scripts folder into a new 7z archive, then install that with NMM or whatever mod manager you use. This gives you a record that you installed SKSE and when you installed it, and makes it possible to uninstall the scripts with a mouse click- not easily done manually.

 

And no, I have no idea how many scripts SKSEVR has (I don't run VR) or whether or not their names are a 1:1 match with SKSE64- that was my whole point; if they're not, when you install one version over the top of another version, you will end up with two versions' scripts installed because they won't overwrite.

[fred200]

9 minutes ago, Vyxenne said:

Not 61 "files" per se- SKSE64 has 61 SCRIPT (*.pex) files in Data\scripts- starting (alphabetically) with activemagiceffects.pex and ending with wornobject.pex. The "right way" to install them is to extract the SKSE64 archive and then zip up the scripts folder into a new 7z archive, then install that with NMM or whatever mod manager you use. This gives you a record that you installed SKSE and when you installed it, and makes it possible to uninstall the scripts with a mouse click- not easily done manually.

 

And no, I have no idea how many scripts SKSEVR has (I don't run VR) or whether or not their names are a 1:1 match with SKSE64- that was my whole point; if they're not, when you install one version over the top of another version, you will end up with two versions' scripts installed because they won't overwrite.

Install all the game directory SKSE files - then just install the entire SKSE archive zip with the mod manager of your choice. All the scripts will wind up in the right place.

[HumbleKarp]

1 hour ago, Vyxenne said:

Not 61 "files" per se- SKSE64 has 61 SCRIPT (*.pex) files in Data\scripts- starting (alphabetically) with activemagiceffects.pex and ending with wornobject.pex. The "right way" to install them is to extract the SKSE64 archive and then zip up the scripts folder into a new 7z archive, then install that with NMM or whatever mod manager you use. This gives you a record that you installed SKSE and when you installed it, and makes it possible to uninstall the scripts with a mouse click- not easily done manually.

 

And no, I have no idea how many scripts SKSEVR has (I don't run VR) or whether or not their names are a 1:1 match with SKSE64- that was my whole point; if they're not, when you install one version over the top of another version, you will end up with two versions' scripts installed because they won't overwrite.

Ah i see, well i did manually make sure everything was in the right location and the sksevr was a fresh download this time around, so no mixed up files. Still no dice. I'm in shrug mode right now. Wondering if i could just use the SL lite version even though i have an skse :thinking: that'd atleast be a hold over until i can come up with a way to solve the issue.

Im open for any more suggestions since a single vr made skse and fresh install hasn't done the trick.

[Vyxenne]

33 minutes ago, HumbleKarp said:

Ah i see, well i did manually make sure everything was in the right location and the sksevr was a fresh download this time around, so no mixed up files. Still no dice. I'm in shrug mode right now. Wondering if i could just use the SL lite version even though i have an skse :thinking: that'd atleast be a hold over until i can come up with a way to solve the issue.

Im open for any more suggestions since a single vr made skse and fresh install hasn't done the trick.

Well since you're at a new game anyway, I would uninstall ALL mods including SKSE** and back up then delete your Skyrim.ini and other ini files (so the next steps can overwrite them) then have Steam "verify cache/local files" and make sure your game installation is OK, then see if you can start a game in stone-vanilla trim. If you can, add SKSE** and verify you can start a new game. Then add SkyUI and... you get the picture. Just basic troubleshooting 101.

 

If, on the other hand, you can't even start a new game in stone-vanilla trim, you know you're not actually in stone-vanilla trim yet, and you have an issue with something left over even after uninstalling all mods. In this case, I would manually delete your Data\Meshes & Data\Textures folders and all *.esp files, plus any *.esm and/or *.bsa files that are not vanilla game files. You should also manually delete any loose scripts and stray DLLs you find.

 

The whole point is you must find some way to get back to a stone-vanilla game before you can begin to troubleshoot whatever is wrong. The really-truly last resort is to delete your entire SSE folder (because some mods *cough*SKSE*cough* are installed above the Data folder) and re-download the game. That is guaranteed to work (unless you have a hardware or driver issue) but takes a while.

[HumbleKarp]

55 minutes ago, Vyxenne said:

Well since you're at a new game anyway, I would uninstall ALL mods including SKSE** and back up then delete your Skyrim.ini and other ini files (so the next steps can overwrite them) then have Steam "verify cache/local files" and make sure your game installation is OK, then see if you can start a game in stone-vanilla trim. If you can, add SKSE** and verify you can start a new game. Then add SkyUI and... you get the picture. Just basic troubleshooting 101.

 

If, on the other hand, you can't even start a new game in stone-vanilla trim, you know you're not actually in stone-vanilla trim yet, and you have an issue with something left over even after uninstalling all mods. In this case, I would manually delete your Data\Meshes & Data\Textures folders and all *.esp files, plus any *.esm and/or *.bsa files that are not vanilla game files. You should also manually delete any loose scripts and stray DLLs you find.

 

The whole point is you must find some way to get back to a stone-vanilla game before you can begin to troubleshoot whatever is wrong. The really-truly last resort is to delete your entire SSE folder (because some mods *cough*SKSE*cough* are installed above the Data folder) and re-download the game. That is guaranteed to work (unless you have a hardware or driver issue) but takes a while.

You did read my last post right? .-. ive already done the "from scratch" multiple times now and the last time i did it exactly as youd just mentioned.

I completely deleted SkyrimVR and SE, Reinstalled both.

Got vr running just fine without mods. Thats not the issue, even with mods the game plays fine, its just lacking any of the mods using animations or status effects considering they use sexlab as a root mod. And since SL will not actually install, (despite saying "ready" after i press the install button) Id say that deleting everything again to do the exact same process is not going to solve any issues. 

SL will not actually install (says it does in the notifications) in game when i press the install button, From a fresh folder with just SkyUI and the skseVR installed.
With or without SexLab i can load into the game fine, open the mcm and view the skyui options.
The only error i can build on this is that when i load a save I have a giant screen in my face that says something along the lines of my skyrim is out of date and that i should be at v1.9.3 or higher. This is most likely because SL is meant for SE and not VR, and id throw a long line to say they probably aren't on the same builds.
 

So either:
A - I need to find (and couldnt yet) a version of sexlab that is meant for vr that utilizes the skse for vr.

B - Theres a solution to the current problem based on sexlab seeing im on the "wrong" version of skyrim and not installing due to that.

[fred200]

I will note:

I have used pretty much every build of Sexlab Ashal has made.

I have never selected Install - and it works just fine.

[Vyxenne]

2 minutes ago, HumbleKarp said:

The only error i can build on this is that when i load a save I have a giant screen in my face that says something along the lines of my skyrim is out of date and that i should be at v1.9.3 or higher. This is most likely because SL is meant for SE and not VR, and id throw a long line to say they probably aren't on the same builds.

So sorry, I must've missed this. The Skyrim LE message is, as you say, a "throwback" to SexLab's Oldrim origins. What Ashal (or someone) said earlier in this thread is that the error is real but the message details are (obviously) bogus.

 

And yes, you are between a rock and a hard place- with SKSEVR, Sexlab won't work, and with SKSE64 SexLab pretends to work but the mismatch between the game version (VR) and the SKSE64 version (SSE) is causing your issues. I believe you may have to choose between playing SSE with SexLab or playing VR without it, at least until a VR version is released.

 

And again, sorry for missing part of your issue the first time.

[HumbleKarp]

Just now, fred200 said:

I will note:

I have used pretty much every build of Sexlab Ashal has made.

I have never selected Install - and it works just fine.

So yours just installs without the need to actually press the install selection in game? Odd I've seen someone else mention the same thing once before but i think id settle for just having it work for starters, then after ill worry about it starting up automatically haha

 

[HumbleKarp]

2 minutes ago, Vyxenne said:

So sorry, I must've missed this. The Skyrim LE message is, as you say, a "throwback" to SexLab's Oldrim origins. What Ashal (or someone) said earlier in this thread is that the error is real but the message details are (obviously) bogus.

 

And yes, you are between a rock and a hard place- with SKSEVR, Sexlab won't work, and with SKSE64 SexLab pretends to work but the mismatch between the game version (VR) and the SKSE64 version (SSE) is causing your issues. I believe you may have to choose between playing SSE with SexLab or playing VR without it, at least until a VR version is released.

 

And again, sorry for missing part of your issue the first time.

No no, no worries at all. I figured you were giving an answer based on either best judgement or based on solutions that might have worked for others, which is very fair. 

I feel i might be missing a critical step or mod but it might just be that the mods aren't ported/ updated yet if ever for the vr version. Majority of the mod creators are up in arms about vr and are not very willing to port to it. Ie: SkyUI, and a few other important mods.

Spend $60, hover forums until mods get updated, SeemsGoodMan lol

[Vyxenne]

31 minutes ago, fred200 said:

I will note:

I have used pretty much every build of Sexlab Ashal has made.

I have never selected Install - and it works just fine.

Me either, but he's being prompted to "install" because he has driven SexLab 1.63 batshit crazy by mix-n-matching game and SKSE versions, one of which (VR) isn't supported yet by SexLab (or vice-versa, actually, but you get my drift.)

[DoubleTrouble999]

1 hour ago, HumbleKarp said:

So yours just installs without the need to actually press the install selection in game? Odd I've seen someone else mention the same thing once before but i think id settle for just having it work for starters, then after ill worry about it starting up automatically haha

 

I think, the "install" is in MCM of SexLab Lite, which by the way, you shouldn't press, but let mod initialize itself.

And if it is really SexLab Lite, then you are in wrong thread.

[zarantha]

I think what fred200 meant is SexLab full will install itself in this situation:

 

1. Install the mod with your mod manager

2. Start the game

3. Wait for the messages the top right to finish, save and exit

4. Load the save. At this point SexLab starts installing itself without going into the MCM.

 

You can also install on step 3 by going into the MCM after the MCM is loaded instead of exiting - I think this is what most people do.

[lordescobar666]

11 hours ago, HumbleKarp said:

I have up to date SkyrimVR, sksevr, skyui, and skse64.

Sexlab 1.63 is currently not compatible to Skyrim VR and sksevr. The reason is that it contains two skse plugins (SexlabUtils.dll and PapyrusUtil.dll) that need to be recompiled for sksevr (hoping that they don't add new hooks into the game engine, because then recompiling is not enough). Also Sexlab's version check probably needs to be patched because Skyrim VR reports a different version number than normal Skyrim SE.

 

11 hours ago, HumbleKarp said:

you need to launch the game with sksevr but you need skse in order for loot and other programs to detect it correctly

As others have already said mixing two different skse versions is bound to cause problems. Fetch the newest development snapshot of LOOT which supports Skyrim VR.

 

 

 

@Ashal: Where can I get the source code for SexlabUtil and PapyrusUtil so that I can recompile them for Skyrim VR?

[blueballbob]

Couldn't find it anywhere, but in the BETA should the 0 HotKey for changing animation sets work?  It currently doesn't seem to do anything in my game, but other hotkeys work.

 

Thanks.

[Vyxenne]

1 hour ago, blueballbob said:

Couldn't find it anywhere, but in the BETA should the 0 HotKey for changing animation sets work?  It currently doesn't seem to do anything in my game, but other hotkeys work.

 

Thanks.

The o key is working in my game. It changes the animation as expected. At first I thought it was the 0 key too, but it's not- it's the letter "o."

[blueballbob]

1 hour ago, Vyxenne said:

The o key is working in my game. It changes the animation as expected. At first I thought it was the 0 key too, but it's not- it's the letter "o."

LoL, I'll try o instead of 0 then.   Yeah I thought it was the number key.

[sophiextime]

Hi! 

 

Just a quick question if i may. Is this Sexlab 1.63 Beta 2 for SE pretty much ready and usable? I know this 1.63 is beta but also sometimes people say that its about as good as its likely to get and therefore totally ok to use.

 

If not has anyone any 'guess'timate as to when an official version is likely to be ready? I am not being impatient as i am happy to wait. Its simply that a month from now i hopefully will have a pretty kickass PC and i really wanna fully mod skyrim SE but also fully sex it up as i used to with Oldrim but just wanting to get an idea where Sexlab is for SE and if its totally ok to use this beta version or if i should wait.