Jump to content

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


Recommended Posts

Posted (edited)

Hi, all. I'm having an issue, and despite looking through all the pages of this thread since v164 came out, I haven't been able to find a solution.

None of the animations will auto-advance stages, even though I have auto-advance stages checked in the MCM; all animations just repeat and continue indefinitely.

If this was just my PC that this happened on, I could deal with it, since I can just advance stages with a hotkey, but this issue is also occurring with animations that don't involve my character (NPC-NPC scenes and NPC masturbation animations).

I know I can advance those by targeting those animations, hitting "N", and then manually advancing the stages, but it's getting a little tiresome having to do that a dozen times whenever SLA, SLEN, or Spectator Crowds starts an orgy and the entire population of Solitude gets stuck in SexLab animations.

Going through this thread, I saw that Cross69 had the same issue back in January (page 337), and Saryon8 posted the same issue in the Technical Support forum, but neither of them received any answers.

Any help you could offer would be greatly appreciated!

 

Edit: Nevermind, I'm dumb. When checking the versions on everything to update this post, I found that one of my other mods was overwriting some of SexLab's features back to v163, and uninstalling that fixed everything.

Edited by ThanatosII
I'm dumb
Posted
7 hours ago, sebas379 said:

since I dont have the AE upgrade I assume I need the old version, right?

Don't assume. Check your skyrimse.exe version (wherever your game is installed, right click in that exe file, pick Properties, Details and check the product version). Unless you did something to avoid or revert automatic updates, you likely have the latest game version which everyone refers to as AE. It doesn't matter if you didn't buy the paid stuff, all it matters is which version is your exe.

So check that and get the proper version for all the mods containing a dll + Address Library.

Posted
23 hours ago, sebas379 said:

By now i've checked and rechecked, uninstalled and reinstalled everything several times over, checked load orders, versions and everything I could think of and I keep getting this error.

Based on the error images you posted, you seem to have installed SexLab for Oldrim into your SSE/AE game. Please check the version of SexLab Framework you have installed.

Posted (edited)
On 7/25/2022 at 9:10 PM, Vyxenne said:

Based on the error images you posted, you seem to have installed SexLab for Oldrim into your SSE/AE game. Please check the version of SexLab Framework you have installed.

 I checked again and its SE versions on my SE install. But you gave me an idea to test, and well...

 

EIther I'm mad (quite possible) or AE isnt the upgrade thats available on steam but that I dont have. Cause I tried installing what I assumed was the wrong version and a first quick test seems to say its working......Sure it now gives different error messages when I started, but the game works....

Edited by sebas379
Posted (edited)

I am almost certain this mod is causing a major issue in my game.  Brand new game (first official playthrough of SSE... can't use oldrim anymore with the number of mods I have).  I have been troubleshooting this problem for a full day and I was very lucky to save JUST BEFORE sexlab activates to find that it was this mod causing the problems.  Just before this mod shows a message in the upper left corner that it is initializing, I suddenly can't interact with major objects in game.  Some objects seem to work like crafting stations.  However things like guardian stones and wood chopping blocks do not work at all.  The objects don't do anything when E is pressed.  I am using v163.  I don't know if v164 addresses this problem but I will try it.  This issue needs to be fixed if I am going to use SexLab again.

 

NOTE: I DO NOT have AE so I don't know if v164 would work.

Edited by shebop
Posted
42 minutes ago, shebop said:

NOTE: I DO NOT have AE so I don't know if v164 would work.

 

Cannot stress this enough: There is no Anniversary Edition of Skyrim.

 

The so-called Anniversary Edition is an optional DLC content pack that does not affect the game version at all. SKSE plugin mod developers mentioning AE as their compatibility condition are absolutely wrong. All they are doing is confusing the hell out of users like you.

 

Ignore any mention of Anniversary Edition. There is only Legendary Edition and Special Edition.

 

There are currently two extant minor versions of Special Edition, 1.5.97 (last available in Nov 2021) and 1.6.353 (up-to-date). Unless you have taken steps to avoid recent updates for Special Edition, or have used the Unofficial Downgrade Patcher, then you are on 1.6.353. This means, when selecting SKSE and SKSE plugin mods, they must be explicitly compatible with 1.6.353 or 1.6.x with the appropriate version of Address Library.

 

Just to be absolutely clear, the only thing you need to get 1.6.353 is to own Skyrim Special Edition and let Steam update it.

 

If you are not certain which version you have, go to the game installation folder and right-click on SkyrimSE.exe, then locate Properties > Details > Product Version. That is the version to use when selecting SKSE and SKSE plugin mods.

 

Once you are certain of your Skyrim version, go through all installed SKSE plugin mods and ensure they are compatible with it and that all dependencies are installed. SKSE plugin mods are those that add DLLs to the Data/SKSE/Plugins folder. They can be identified in MO2 using the <Contains Script Extender Plugin> filter, or in Vortex using the Extender option in the Content filter (if this filter is not visible, use the cogwheel above the mod list and enable it).

Posted (edited)
9 hours ago, Exploited Kiri said:

So I'm getting this error popup. Can anyone direct me to the correct download link? Much thanks in advance.?

 

 

 

 

ScreenShot1316.png

 

That is just a SUM issue, it does not mean you installed the wrong sexlab version. There's a file in SUM that you can add your sexlab version to, assuming you downloaded the SE version of the mod.

 

 

Fix:

 

And just realized he didn't put the path in. It's here. I've used the properties in MO2, if you're on vortex, just browse to that location in the mod staging folder and use a text editor to edit the file.

 

Spoiler

 

image.png.cc7ee2390f51031944d526fde94e39a0.png

 

 

Edited by zarantha
updated with file locationscreenshot.
Posted (edited)
9 hours ago, Sailing Rebel said:

 

Cannot stress this enough: There is no Anniversary Edition of Skyrim.

 

The so-called Anniversary Edition is an optional DLC content pack that does not affect the game version at all. SKSE plugin mod developers mentioning AE as their compatibility condition are absolutely wrong. All they are doing is confusing the hell out of users like you.

 

Here is where you are wrong.  I am NOT confused  about the issue (but you appear to be).  I am a developer and have been programming for over 30 years.  I know the differences.  No, the changes weren't major (they didn't really affect non SKSE plugins); BUT...

  1. I heard that they upgraded to a different version of Visual Studio (which can result in differences in compiling and native computer instructions)
  2. C++ is HIGHLY sensitive to changes in code, unlike more "modern" languages (which ARE still fairly sensitive unless they are linked at runtime)
  3. ANY change made to a method will 99.99% of the time change call addresses of methods (offset from where a dll and/or exe loads into memory.)
  4. Any change made to the library used can change the call address as well (which often happens when changing compilers).
  5. If there hadn't been changes there would have not been a need to update the plugin address library or SKSE.
  6. ANY DLL THAT USES SKSE WILL NEED TO BE RECOMPILED TO INCORPORATE THE UPDATED CALL ADDRESSES.  THE VERSIONS ARE NOT COMPATIBLE
  7. SexLab HAS AN SKSE DLL.

As far a papyrus is concerned, I don't know if the papyrus executable (pex) file is directly linked or indirectly linked (by proxy) to method calls.  If the former, it also will need to updated.  My guess though is that the addresses are linked at runtime. 

 

As far as my post is concerned, it certainly does make a difference per the above facts.  Your own post makes this clearly evident.

 

EDIT: As far as your advice goes.  I certainly know enough to know which version of Skyrim I use; which version of SKSE I need; and which versions of a mod to download.  The only thing I am "guilty" of is not reading all the update notes for 1.64.  So stop assuming people are stupid and address the question next time.

 

EDIT2: YOU ARE DOUBLY WRONG.  IF YOU PAY ANY ATTENTION TO FILE NAMES IN THE DOWNLOAD 1.64 EXPLICITLY STATES IT IS FOR AE ONLY.  The version in the download STILL posted for SE is 1.63.  This is WHY I stated what I did in my OP.  It is why I believed it was for AE when I downloaded it over a month ago.

Edited by shebop
Posted (edited)
5 hours ago, shebop said:

Stuff

 

There is no 'AE Version'.

 

There is LE version.

There is outdated SE version.

There is current SE version.

 

Thats it.

Edited by shardoom
Posted
9 hours ago, Sailing Rebel said:

 

Cannot stress this enough: There is no Anniversary Edition of Skyrim.

 

The so-called Anniversary Edition is an optional DLC content pack that does not affect the game version at all. SKSE plugin mod developers mentioning AE as their compatibility condition are absolutely wrong. All they are doing is confusing the hell out of users like you.

 

Ignore any mention of Anniversary Edition. There is only Legendary Edition and Special Edition.

AE acts as a way to simply disern major versions with the game, like SE and LE.

If someone is talking about LE today, we can be reasonably certain they mean 1.9.32.0.8, 32-bit engine, but it does not specify if they have any specific DLC or not. We use LE to describe both versions of the game, the original release and the release with all the DLC (called "Legendary Edition"), for convenience sake.

 

AE is used in the same context. If we are talking about SE, we are most likely talking about 1.5.97, and if we are talking about AE, we are talking about 1.6.353 (currently). This is often specified by mod authors as well if it is relevant.

 

Most of the community understands that AE means 1.6.X, with or without the DLC, while SE means 1.5.97. On a technical level, these are essentially different games (where this distinction is most important), even if on a practical level, ir's a minor upgrade over the previous version.

Posted
11 hours ago, shebop said:

I am almost certain this mod is causing a major issue in my game.  Brand new game (first official playthrough of SSE... can't use oldrim anymore with the number of mods I have).  I have been troubleshooting this problem for a full day and I was very lucky to save JUST BEFORE sexlab activates to find that it was this mod causing the problems.  Just before this mod shows a message in the upper left corner that it is initializing, I suddenly can't interact with major objects in game.  Some objects seem to work like crafting stations.  However things like guardian stones and wood chopping blocks do not work at all.  The objects don't do anything when E is pressed.  I am using v163.  I don't know if v164 addresses this problem but I will try it.  This issue needs to be fixed if I am going to use SexLab again.

 

NOTE: I DO NOT have AE so I don't know if v164 would work.

I've had 1.64 seemingly crash when SexLab first does the setup, and it seems to be somewhat random, with some persistence it eventually succeeds. Staring at a wall, or being inside might help.

 

1.64c is for the AE version, 1.6.353 specifically. Using 1.63 will cause issues, as it is made for 1.5.97 ("SE"). Assuming you let steam update the game, it will be 1.6.353

Posted
3 minutes ago, CaptainAdultGames said:

How to delete SexLab animations? I want them all gone.. they take up too many vital animation slots I would rather use on newer animation SLAL packs.

 

Look for a mod called remove default sexlab animations or something like that, it's on LL somewhere. 

Posted
4 minutes ago, VeraDra said:

Most of the community understands that AE means 1.6.X, with or without the DLC, while SE means 1.5.97.

Most, I'm sure. Alas, the rest show up regularly to ask why the game is telling them they have the wrong mod versions installed, even though they didn't buy AE.

 

And that's not their fault. It's confusing, and frustrating.

 

Yes, it has become a convention, but a problematic one. To the uninitiated, "AE" very strongly suggests something that just isn't true: that users only need "AE" compatible mods if they own the Anniversary Edition mod pack.

 

We, users and developers, would all be better served sticking to using 1.5.x / 1.6.x to make the distinction between the SE executable versions where necessary, and not mentioning AE at all (unless a mod actually depends on the mod pack).

Posted
14 minutes ago, bnub345 said:

 

Look for a mod called remove default sexlab animations or something like that, it's on LL somewhere. 

 

Sorry if i'm ignorant about this but isn't that mod (which I did find earlier before asking) for LE and ealier SE version not the updated SE(AE)... i'm not sure if it makes a difference. If it doesn't let me know and I will try this.

Posted
6 minutes ago, CaptainAdultGames said:

 

Sorry if i'm ignorant about this but isn't that mod (which I did find earlier before asking) for LE and ealier SE version not the updated SE(AE)... i'm not sure if it makes a difference. If it doesn't let me know and I will try this.

 

Yeah my bad that mod is LE only. 

Posted (edited)
2 hours ago, shebop said:

There is no Anniversary Edition of Skyrim.

Based on semantics alone, this is not true- the first 1.6.xxx (VS 2019) build of SSE was released on 11/11/2021, the 10th Anniversary of the first Skyrim release, which occurred on 11/11/2011. So even if version 1.6.xxx had not been recompiled via Visual Studio 2019, rendering it incompatible with any and all existing Native Code mods, and instead just been a graphics enhancement update numbered 1.5.971 or 1.5.99 or whatever, it still could legitimately be called the "Anniversary Edition" based solely upon its release date.

 

But of course, that was not what Beth did- they updated the executable in such a way that it is/was incompatible with previous release addresses and hooks, and most if not all Native Code mods (DLL-based mods) AND THEN released it on the Anniversary Date. It was already being called "AE" by most cognoscenti websites months before its release, to clearly differentiate it from the long line of previous SSE releases. Sadly, this tactic not only killed SKSE64 (for a time) and all dll-based mods, it disabled the seminal .Net Script Framework mod and any mods dependent on it. I don't blame @meh321 for not wanting to rewrite it from the ground up.

Edited by Vyxenne
Because date math is not her strongest subject
Posted

Semantics and technical jargon aside, referring to specific exe version is way more accurate. Yes, LE / SE / AE is a perfectly clear distinction, if we all know what we're talking about. That's not the case, ffs the amount of users saying "bUt I dOn'T hAVe aE" while they're on the latest patch is too damn high. Asking and referring to specific executable versions is often the only way to offer help and get users to understand what's going on and how to fix it.

Posted (edited)

 

2 hours ago, Just Don't said:

Asking and referring to specific executable versions is often the only way to offer help and get users to understand what's going on and how to fix it.

I totally agree with this. From a Skyrim Modding standpoint, the actual version numbers of the executable should be requested and used. My post above was simply to show that a case can be made that 1.6.xxx releases can legitimately be called "AE," not that they should be.

Edited by Vyxenne
Because reading it twice before submitting it apparently isn't enough for her
Posted (edited)

So many of you are missing the point.  A rose is a rose by any other name.  (Shakespeare - In other words it doesn't matter what you call it).  This is a forum to help people with their problems.  STOP ARGUING SEMANTICS.  THEY DON'T MATTER AND AREN'T HELPING ANYONE.  The point is that you cannot use 1.64 with "Anniversary Edition".   THIS WAS MY POINT FROM THE BEGINNING.   THIS IS NOT THE SOURCE OF MY PROBLEM.  The issue is that Sexlab is causing me not to be able to interact with stuff such as wood chopping blocks and Guardian Stones.  This isn't the first time this issue has been reported; though usually people find that it is a Sexlab Addon and that it happens after sex.  The former may (or may not) be the case here but I have no idea which one (or if it is Sexlab itself) and it is happen when Sexlab initializes.  The point is that FOUR TIMES while troubleshooting this issue, I have seen the Sexlab initializing notice come up about the same time that it starts happening.  Two of those times were directly after loading a save game where Sexlab initializes almost as soon as I load the game and I was able to use the wood block only once.  As soon as Sexlab started its thing I couldn't use it anymore.

 

EDIT: The reason those other posts about this issue didn't help is because I am only running 6 or so Sexlab mods in this runthrough (I am role-playing a "loyal" character).  I am perfectly capable of troubleshooting myself.  Problem is that the troubleshooting here is very difficult as the problem occurs at an upredictable time since it is related to mod start-up and I often have to save the game and re-load before it occurs.  The only Sexlab mods currently installed are:

  • Aroused
  • Interactive Arousal
  • Light Me Up
  • Auto Vanilla Voices
  • Spouses Enhanced
  • Lovers Comfort
Edited by shebop
Posted (edited)
8 hours ago, shebop said:

STOP ARGUING SEMANTICS.  THEY DON'T MATTER AND AREN'T HELPING ANYONE.  The point is that you cannot use 1.64 with "Anniversary Edition".   THIS WAS MY POINT FROM THE BEGINNING.   THIS IS NOT THE SOURCE OF MY PROBLEM.  The issue is that Sexlab is causing me not to be able to interact with stuff such as wood chopping blocks and Guardian Stones.

Well, this all started because you said

On 7/27/2022 at 9:39 AM, shebop said:

I am using v163.  I don't know if v164 addresses this problem but I will try it.  This issue needs to be fixed if I am going to use SexLab again.

 

NOTE: I DO NOT have AE so I don't know if v164 would work.

You can't use 163 or 164 willy-nilly because you think it'll solve something. You must use the correct one for whatever version of the executable you have. As you say quoting Shakespeare, it doesn't matter what you, me, your neighbor, or Todd himself calls it. All it matters is which executable version you have.

 

Now, to test your hypothesis of 164 causing issues in an AE game I went ahead and updated, clean install product version 1.6.353, got Address Library for AE, SKSE 2.1.5 and Sexlab 164c.

Spoiler

Installing SL

image.png.01b4d5824cea90d4a2f793feca5b4043.png

 

Activating a Standing Stone

image.png.19db8d7fbded287e07e0e96d90086a63.png

 

Activating a wood chopping block

image.png.108435d84dfdede36b06e7fc737f1d9e.png

 

Thus SL 164 works fine when used as intended, with its corresponding requirements. I should add I started the game via Skyrim Unbound and only triggered the SL installation once I had full control of my character, then waited for it to complete before doing anything else. You know, just as the description states. Your problem is likely elsewhere (a different mod, or doing things you're not supposed to do before/during the SL installation). Note that loading a save where SL is enabled but hasn't been installed will trigger an automatic install, you shouldn't need to be loading and reloading saves that early, perhaps you should slow down and let all your mods initialize.

 

ps: 163 also works fine when you use it with the corresponding version of SL requirements. What I'm saying with this is don't expect the issue to be fixed by using one version or the other, because your issue isn't easily replicable which would indicate it's something on your side.

Edited by Just Don't
Posted
11 hours ago, shebop said:

The issue is that Sexlab is causing me not to be able to interact with stuff such as wood chopping blocks and Guardian Stones.  This isn't the first time this issue has been reported; though usually people find that it is a Sexlab Addon and that it happens after sex.  The former may (or may not) be the case here but I have no idea which one (or if it is Sexlab itself) and it is happen when Sexlab initializes.  The point is that FOUR TIMES while troubleshooting this issue, I have seen the Sexlab initializing notice come up about the same time that it starts happening.  Two of those times were directly after loading a save game where Sexlab initializes almost as soon as I load the game and I was able to use the wood block only once.  As soon as Sexlab started its thing I couldn't use it anymore.

 

Is not SexLab and probably none of Mods related with SexLab but could be.

 

If the problem is just with one bed or furniture just after be used for a sex scene then is almost sure that is a corrupted file on SexLab but in your case where the problem is with all the objects and not even related with a animation, the relation you find look more like a coincidence. Like when I save the game in a inn and once I leave the inn some dragon appear after few minutes and not matter the amount of times I load the game, the dragon still appears.

 

 

First let me explain what must be happening:

The "Activation Control" that is what you seems to be missing can be disabled by scripts and is a very common mistake done by the mod author to forget to check some conditions before use it and many times they forget to set a script to revert it not matter what. But in most of the cases is related with some animation idle applied to the player by some Mod in which case you can try starting a sex animation with keep holding the "N" for 15 seconds or use any hotkey of any Mod that force some animation idle on the player. 

 

 

Solution:

Pay attention for what happens with the player before and after loss the "Activation Control", that should bring you a more accurate idea of what is trigging the issue. Then remove, update Or find a patch for the Mod with the issue, if you have two or more Mods overwriting the same file is almost sure that you need a patch to prevent issues like this.

 

 

Posted

Hi guys, sorry for probably a basic question, but do you have any idea why SexLab is not reading translation file? I tried to search forum and this topic but I found nothing about such problem. Got Skyrim SE/AE, SexLabFramework 1.64c, translation files are on place, and everything works great, except translation. It is a bit confusing setting mod looking like that. 

The Elder Scrolls V  Skyrim Special Edition Screenshot 2022.07.29 - 11.58.19.23.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   1 member

×
×
  • Create New...