SexLabUtil version 1 (SexLabUtil.dll, SexLabFrameworkSE_v163_BETA8) reported as incompatible during query.

[tehmasta]

Hello, i came back to modding skyrim again after a while and i'm getting this error from MO2 "SexLabUtil version 1 (SexLabUtil.dll, SexLabFrameworkSE_v163_BETA8) reported as incompatible during query."

This has never happened to me before, i've been searching around the internet for a solution but i couldn't really fix it. Currently i have deleted everything except SKSE Sexlab and Skyui, also cleared whole overwrite folder. 
Game version is 1.5.97.0.8, SKSE version 2.0.19. Sexlab version 1.63 beta8. 

Any advices are welcome

[Just Don't]

Are you using the latest version of MO2? The times I've seen that issue when there is no actual version incompatibilities (given the version you list that shouldn't be the case), is because MO2 was outdated.

[tehmasta]

3 minutes ago, Just Don't said:

Are you using the latest version of MO2? The times I've seen that issue when there is no actual version incompatibilities (given the version you list that shouldn't be the case), is because MO2 was outdated.

Yep, it's the lastest one 2.4.1. 

I have completely reinstalled both skyrim and mod organizer, loaded only sexlab and still get same error. 
I have successfully ran out of ideas.

[PapaGeorge]

10 minutes ago, tehmasta said:

I have successfully ran out of ideas

[Just Don't]

Did you start from a clean install? You mention clearing the Overwrite folder, but that should be empty? In the same setup (MO2 2.4.1, SKSE64 2.0.19, SE 1.5.97, Sexlab 163 beta8) I can't reproduce that message. Only reason for this to happen would be if there are old files in your mo2 install or in the actual game folder (even if you re-install SE from Steam you need to manually remove the Skyrim Special Edition within Steam to get rid of remaining files from old installs).

 

edit: sexlab 163 beta 8 works in 2.0.17-2.0.19 fine, but I know some people have issues with 2.0.19 and other mods, not Sexlab, it might be worth replacing your SKSE64 install for the 2.0.17 version for tests (just make sure your mods work with 2.0.17, as some mods require 2.0.19).

[tehmasta]

6 minutes ago, Just Don't said:

Did you start from a clean install? You mention clearing the Overwrite folder, but that should be empty? In the same setup (MO2 2.4.1, SKSE64 2.0.19, SE 1.5.97, Sexlab 163 beta8) I can't reproduce that message. Only reason for this to happen would be if there are old files in your mo2 install or in the actual game folder (even if you re-install SE from Steam you need to manually remove the Skyrim Special Edition within Steam to get rid of remaining files from old installs).

 

edit: sexlab 163 beta 8 works in 2.0.17-2.0.19 fine, but I know some people have issues with 2.0.19 and other mods, not Sexlab, it might be worth replacing your SKSE64 install for the 2.0.17 version for tests (just make sure your mods work with 2.0.17, as some mods require 2.0.19).

 

Fixed it for now. To my surprise there was something messing with it from the my games folder, where skyrim keeps it's settings and saves. Deleted the entire folder and i don't get the error now. 
Thanks for your time. 

[Just Don't]

9 hours ago, tehmasta said:

 

Fixed it for now. To my surprise there was something messing with it from the my games folder, where skyrim keeps it's settings and saves. Deleted the entire folder and i don't get the error now. 
Thanks for your time. 

Ah so probably an old skse64 log (these are kept in your Documents near your save files and MO2 uses them to detect incompatible skse plugins). Good to know the reason. If your game actually gets to load, the issue is gone. It probably was just a stuck notification from having old files in that folder (generating a new skse64 log or removing the old one like you did is enough to solve it).

[LoneWolfCade]

On 4/16/2021 at 3:19 PM, tehmasta said:

 

Fixed it for now. To my surprise there was something messing with it from the my games folder, where skyrim keeps it's settings and saves. Deleted the entire folder and i don't get the error now. 
Thanks for your time. 

Can you explain what exactly what you did?