Jump to content

Sexlabframework and SOS missing after Skyrim AE update


Recommended Posts

Posted

HI. I had skyrim running just fine on my E disk, but whem the auto update happened, steam installed the update on my C disk, which was then full, causing total mayhem.

I managed to make space and reinstalled the update on C. I then installed the new SKSE64 beta version (2.0.20) that is supposed to be more or less ok with running mods  on the new version.

On vortex, I then reinstalled the sexlabframework and the SOS and related files and kept running FNIS until there were no errors, and sorted the load order.  At this point everything looked fine on Vortex. I then launched skyrim SE from outside steam and loaded my last clean save. 


The first error I got on the load screen "Slongs of Skyrim not found" "found -1 expected 300004" The second message I got was that it couldn't find SexlabUtil.dll in the plugins folder, missing file please reinstall! I tried loading a previous save , and got the same errors.

 

Reinstalling didnt change anything, so I checked in c:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins, and both SexLabUtil.dll and are both present. As there were errors, I would have thought that the mod configuration would be blank or have missing items but this is not the case , all my configurations are still there!

It's obvious that something is totally screwed either
By the new version not being compatible -is anybody else having similar problems?
or by

The change of disk  - maybe the program is trying to launch from E or is not looking in the right place, in which case what can I do to find a solution

 

Help!!!! PLEASE can anybody suggest something

Many thanks
 

PS please be patient with me as my advanced age (75) means that I am not quite as sharp as I used to be

Posted

Hi,

You're not alone. My limited understanding is that mods that rely on SKSE may work with the new build but mods that add DLLs require the mod author to make updates (or authorize someone else to). All of these amazing authors do this as a hobby so we will just have to see what they come up with! I would follow the mods you use and see when they are updated or possibly replaced. The same thing happened when Skyrim SE replaced Skyrim LE. Some mods may never be updated but functionality may be replaced by new mods so keep an eye out for that as well. 

 

For the time being Flower Girls (from the Nexus) seems to work ok for limited NSFW content so you can integrate that into an AE playthrough while you wait to see what happens.
 

Good luck!

Posted

Thanks for listening
After reading your reply, I decided as a last resort, to try reverting my version of skyrim SE to the old one using the Unofficial Skyrim Special Edition Downgrade Patcher https://www.nexusmods.com/skyrimspecialedition/mods/57618?tab=description
First I reverted  skse64 to the previous one before the update, then I ran the full patch ( no messing around - I've had enough of things that don't work)

and.....

IT WORKS PERFECTLY

I will now wait until my mods catch up before trying out the anniversary edition and next time I'll be sure not to update automatically on steam

  • 2 weeks later...
  • 7 months later...
Posted (edited)
9 hours ago, blackfoxkitsune said:

same problem, and it's not an skse or zaz problem. its Bethsda going out of their way to push creation clubs sub par mods by trying to destroy the wider Modding community. 

SL has a version for the latest game version since January. Get that, get the SKSE version for your game version and Address Library. All SL requirements stated in the description. And you're done. It's not rocket science, it's just looking at some numbers when you get the files.

Or disable automatic updates as everyone should do if they're serious about modding a game.

Edited by Just Don't
  • 2 weeks later...
Posted (edited)
On 7/19/2022 at 6:25 PM, Just Don't said:

SL has a version for the latest game version since January. Get that, get the SKSE version for your game version and Address Library. All SL requirements stated in the description. And you're done. It's not rocket science, it's just looking at some numbers when you get the files.

Or disable automatic updates as everyone should do if they're serious about modding a game.

so with out being a rude  jerk like you did with the whole "it's not rocket science" moment onwards.
1: I have automatic updates disabled, (have done since they came up with that pile of puke known as creation club)
and Like with MANY players of Skyrim SE, the AE updated was FORCED regardless of us saying "no auto updates please".

2: I came here and asked about it, BECAUSE the Description on how to install it WAS NOT WORKING, In fact after many days of doing it alone, and navigating LL the hard way (because google is faster than the in site search to find mods around here lately.)
The only way to fix it was a roll back mod "best of both" and to have BOTH SE and AE versions of SL installed with SL-SSE disabled (but installed) but have AE installed AND enabled. 

 

Edited by blackfoxkitsune
Posted (edited)
34 minutes ago, blackfoxkitsune said:

so with out being a rude  jerk like you did with the whole "it's not rocket science" moment onwards.

Why using a coloquial phrase to say something isn't very difficult is being a jerk? It's literally taking note of some numbers and verifying you're getting the correct files when you see some mod mentioning said numbers.

I just did a clean install of SE 1.6.353 with SL 164c, SOS AE and so on. It works. All you need to do is install the correct files.

I've been playing on 1.5.97 with SL 163 for months and I haven't had a single instance of unwanted updates.

 

34 minutes ago, blackfoxkitsune said:

The only way to fix it was a roll back mod "best of both" and to have BOTH SE and AE versions of SL installed with SL-SSE disabled (but installed) but have AE installed AND enabled. 

Best of both should revert to a 1.5.97 executable. Using SE+AE mods is a nonsense workaround and should only work if your game wasn't downgraded properly.

You'd save a lot of time if you just check your executable version and get the files for that version. But if after days of trying to troubleshoot this and with your weird workaround you made it work, more power to you. Hope you don't have to deal with yet another update though.

Edited by Just Don't

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   0 members

    • No registered users viewing this page.
×
×
  • Create New...