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

[hana120]

Not bad. But I prefer it in brown.
There, we would believe more than it is she.

I will wait patiently for Sexlabs, SOS, additem to be up to date.
Skse is up to date?

[Warbeck]

25 minutes ago, hana120 said:

Not bad. But I prefer it in brown.
There, we would believe more than it is she.

I will wait patiently for Sexlabs, SOS, additem to be up to date.
Skse is up to date?

I believe almost everything is updated besides SLFW. We just have to wait brother.

[Ashal]

Update for new SKSE is posted now.

[Emris18]

the Sexlab beta for SE is updated? if so could i get a link?

 

[Emris18]

12 minutes ago, Ashal said:

Update for new SKSE is posted now.

For that, sry if it wasnt clear.

 

[Snook001]

Thanks Ashal

 

[Vapor]

6 minutes ago, Emris18 said:

the Sexlab beta for SE is updated? if so could i get a link?

 

Main page, Emris.

Speaking of -- MO2's got Beta8 throwing incompatible plugins on papyrus and SexLabUtil like 7 was after the skyrim update. Gonna see if that's just MO being dense.

[Oninace]

not sure if this works but it's worth a try for the future.
https://steamcommunity.com/sharedfiles/filedetails/?id=1086279994

step 9 it showes the app text for the game you are playing. On the autoupdate line set it to 0 and try that. There are ways you can test it but I'm lazy. 

[Snook001]

2 minutes ago, Oninace said:

not sure if this works but it's worth a try for the future.
https://steamcommunity.com/sharedfiles/filedetails/?id=1086279994

step 9 it showes the app text for the game you are playing. On the autoupdate line set it to 0 and try that. There are ways you can test it but I'm lazy. 

This version work, I used it yesterday and it was a piece of cake.

 

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

[Oninace]

oh this was for all the ones who couldn't play. I copy my entire skyrim folder to another folder so when it updates I can just overwrite the update and play offline if I so choose.

[Vapor]

50 minutes ago, Vapor said:

Speaking of -- MO2's got Beta8 throwing incompatible plugins on papyrus and SexLabUtil like 7 was after the skyrim update. Gonna see if that's just MO being dense.

So, that's just MO2 being a butt, didn't get the pop-up in game about SexLabUtil being out-of-sorts like I was getting last night.

[JimKhan]

Well done with the update.

[Vyxenne]

7 hours ago, Musje said:

19 hours ago, Vyxenne said:

Au contraire, mon frère- There are 3 ways to stop Steam/Bethesda from updating your game:

1. Set Steam to update your game only when you launch it, then always use skse64_loader.exe to launch your game, which bypasses the vanilla loader
2. Set Steam to update games only during a one-hour period when your computer is never on (mine is set for 6:00 AM to 7:00 AM  )
3. Set Steam to Offline mode- you will get a dialog asking you to confirm this when your machine boots up, just tell it to stay offline

 

Personally, I use all 3 methods, although theoretically any one of them should do the trick. As an example of how well this works: I am still on SSE v1.5.62, SKSE64 2.0.12 and SexLab Framework 1.63 Beta 5, all of which are now 3 versions behind the current versions. I have not lost one second of game time to any Bethesda update for many months, and I have no plans to update my game until some mod that requires the latest versions offers something I simply can't live without.

 

Using only #1 didn't work for me, Steam still applied the update.

You must have inadvertently launched the game via the vanilla launcher, or launched it via skse64_loader.exe without Steam already running, which forces skse64_loader.exe to start Steam, which then starts your game for you via - wait for it - the vanilla game launcher. Regardless of how it happened, launching the game via the vanilla loader is the only way Steam could have detected a game-launch event, triggering the update.

 

Still, if you had set Steam to Offline, it could not have updated even after you gave it a game launch trigger. We're all human, and we all make mistakes- that's why I use all 3 possible methods to block Steam/Bethesda from push-updating my game. If I mess up and inadvertently bypass one of the 3 safeguards against game updates, the other two will save me.

 

And finally, that's why I keep a full backup, synchronized weekly, of my entire SSE folder plus the ini and savegames folder, which for me is Users\Angie\Documents\My Games\Skyrim Special Edition.

[Vyxenne]

7 hours ago, fred200 said:

Steam has client updates - frequently.

If you launch using SKSE - and Steam needs an update - it will bypass SKSE and launch the game. That also picks up the game updates.

ONLY offline works - if you never let Steam accept client updates.

This is not quite accurate- if you always make sure Steam is running first, then launch the game only via skse64_loader.exe, Steam will never update the game even if you allow it to be Online. When Steam needs a client update, it asks you for permission to update itself, and when you say OK it updates itself and then gives you the "Launch Steam in Offline mode?" prompt. Steam never launches any game as part of a Steam Client update.

 

I already posted the 3 possible ways to block updates (see post immediately above this one). Any one of those methods works, but using all 3 provides triple redundancy for when you inadvertently bypass one of the 3 blocking strategies as I have done on two occasions.

[Vyxenne]

7 hours ago, Sailing Rebel said:

Just a note on Steam update behaviour. I've found the least problematic way to deal with updates is to make a copy of SkyrimSE.exe, allow Steam to update Skyrim, then replace the new SkyrimSE.exe with the old one (but keep the new one as you are going to need it in future).

 

After that Steam will no longer try to queue the Skyrim update even though you are running an older version, unless you manually verify the files.

On at least one of the updates over the past couple of years, Bethesda updated multiple files, not just the game executable. I remember one in particular that I thought was particularly unexpected, Skyrim - Shaders.bsa. The reason I'm mentioning this is that just reverting the executable may not be all you need to do- you may also need to look up the "Core Files" Depot and ManifestID and download them (7 GB) as well when you revert.

 

Here is a boilerplate guide to updating/reverting that I compiled from a couple of sources last night:

 

You can "update" or "downdate" to any version of SSE via the Steam Console, but you have to have the ManifestIDs to do it.

You can find non-current versions of SKSE64 via a different link right below the current versions on the Silverlock page.

To update or revert your game, make note of the game and SKSE64 versions you need, and the ManifestID as well.

 

Game  / SKSE64 / ManifestID
1.5.97 / 2.0.17 / 2289561010626853674
1.5.80 / 2.0.16 / 2486778358967039909
1.5.73 / 2.0.15 / 6411417958676685207
1.5.62 / 2.0.12 / 7531846925655934196
1.5.53 / 2.0.10 / 4140371450004190946
1.5.50 / 2.0.08 / 583541185188584076
1.5.39 / 2.0.07 / 1298692161422189837
1.5.23 / 2.0.06 / 7780040377772731640
1.5.16 / 2.0.05 / 3146230552641174659
1.5.03 / 2.0.04 / 911281757511576655

 

Go to SteamDB, enter "Skyrim" into the search box, select Skyrim Special Edition and nose around a bit. You will see that:

• The appID for Skyrim Special Edition is 489830
• The depotID for the Skyrim Special Edition executable is 489833
• The depotID for the Skyrim Special Edition core files is 489832

The download command syntax is

download_depot <appID> <depotID> <manifestID>

To download any version of SSE:
1. Look up the ManifestID of the SSE version/files you want
2. Press Win+R
3. Type (or Copy > Paste): steam://nav/console
4. Type (or Copy > Paste): download_depot 489830 489833 <manifestID> where <manifestID> is the manifestID you looked up in Step 1
5. The file will be downloaded to [...]steamapps/content/app_489830/depot_489833\
6. Copy the file from [...]steamapps/content/app_489830/depot_489833\ into your Skyrim Special Edition folder, overwriting the old one(s)
7. If you need the core files, get the manifestID from SteamDB and repeat steps 2-6 above

 

You can find this and even more info at  Guide - How to rollback your skyrim after update so be sure to check it out for more info, pics, etc.

 

[fred200]

The scenario I experience is Steam not running, launch the game with SKSE launcher, Steam starts, loads it's updates, and skips SKSE. It goes to the Play / Options splash screen.

[StaticFriend]

Has SkyUI not been updated for the new SKSE yet?

[Sailing Rebel]

1 hour ago, StaticFriend said:

Has SkyUI not been updated for the new SKSE yet?

SkyUI is not dependant on a particular version of SKSE.

 

When using MO2 you can see which of your mods need to be kept up-to-date with the installed SKSE version by using the <Contains Script Extender> filter (bottom left of the left panel).

[Vyxenne]

6 hours ago, fred200 said:

The scenario I experience is Steam not running, launch the game with SKSE launcher, Steam starts, loads it's updates, and skips SKSE. It goes to the Play / Options splash screen.

That's exactly right, Fred, and thank you for confirming the accuracy of what I said:

You must have inadvertently launched the game via the vanilla launcher, or launched it via skse64_loader.exe without Steam already running, which forces skse64_loader.exe to start Steam, which then starts your game for you via - wait for it - the vanilla game launcher. Regardless of how it happened, launching the game via the vanilla loader is the only way Steam could have detected a game-launch event, triggering the update.

in my response above.

 

Pro tip: you won't "experience that scenario" if you don't try to launch the game without making sure Steam is running first.

 

 

[hana120]

12 hours ago, Ashal said:

Update for new SKSE is posted now.

Thank you, Ashal.
Fortunately we can count on the speed of the modders.

Only Engine remains to be up to date.

[Musje]

7 hours ago, Vyxenne said:

You must have inadvertently launched the game via the vanilla launcher, or launched it via skse64_loader.exe without Steam already running, which forces skse64_loader.exe to start Steam, which then starts your game for you via - wait for it - the vanilla game launcher. Regardless of how it happened, launching the game via the vanilla loader is the only way Steam could have detected a game-launch event, triggering the update.

 

Still, if you had set Steam to Offline, it could not have updated even after you gave it a game launch trigger. We're all human, and we all make mistakes- that's why I use all 3 possible methods to block Steam/Bethesda from push-updating my game. If I mess up and inadvertently bypass one of the 3 safeguards against game updates, the other two will save me.

 

And finally, that's why I keep a full backup, synchronized weekly, of my entire SSE folder plus the ini and savegames folder, which for me is Users\Angie\Documents\My Games\Skyrim Special Edition.

That's nice, but Steam really needs a setting per individual game to prevent automatic updates, so we don;t have to jump through these hoops. That was my point. Skyrim isn't the only game I play, and not the only one ever to get broken by a faulty update.

[onkalabonka]

8 hours ago, StaticFriend said:

Has SkyUI not been updated for the new SKSE yet?

SkyUi SE 5.2 is around for years now and is totally independant of SKSE version hassle, but Racemenu isnt, but that also got updated.

[hana120]

Now all that remains is Fixed Engine to be updated. Hope this is fast and do not wait a month.

[BarsikTheCaT]

I have some weird problem with this newest version - for some reason it requires an older version of SKSE
The one I currently have is 2.0.17, but Sexlab requires 2.0.9 for some reason

[tasairis]

5 hours ago, BarsikTheCaT said:

I have some weird problem with this newest version - for some reason it requires an older version of SKSE
The one I currently have is 2.0.17, but Sexlab requires 2.0.9 for some reason

The text there hasn't been updated, that's all.