Jump to content

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

Ashal

By Ashal,
in Downloads - SexLab Framework SE

Recommended Posts

Vyxenne

Vyxenne

Posted
Posted (edited)
On 12/14/2021 at 11:08 PM, Martok73 said:

 

Not talking about AE this has all been about SE 1.5.97 and SL v1.63, so no AE screw the ASShat Edition.

But.. but... FISHING! ?

Edited by Vyxenne
Because she thought for a brief moment that she had misspelled "FISTING"
1

Martok73

Martok73

Posted
Posted
2 hours ago, Vyxenne said:

But.. but... FISHING! ?

 

LMAO nty, boring AF IRL can only imagine how boring AF it would be in a video game, LOL... I think honestly the only CC thing I "might" be interested in is that vampire lair underground cave house, that thing looks bad ass.

Martok73

Martok73

Posted
Posted

@OsmelMC @Ashal Sorry to bother y'all again, but just had a crash and had a huge amount of these errors in the papyrus, and a very strange .net crash log. The crash prolly has nothing to do with sexlab, but these papyrus errors have the sexlab questregistry and sexlab thread reference in them so I thought I should probably share the part that is repeating over and over in the log for you to look at, "just in case"...

 

It's under the spoiler tag so as to not take up too much room:

Spoiler

[12/16/2021 - 04:14:09PM] ERROR: Cannot access an element of a None array
stack:
    [alias RegistrySlot369 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.GetLipFixedPhase() - "sslBaseExpression.psc" Line 330
    [alias RegistrySlot369 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.IsLipFixedPhase() - "sslBaseExpression.psc" Line 371
    [alias RegistrySlot369 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.ApplyPhase() - "sslBaseExpression.psc" Line 75
    [alias RegistrySlot369 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.Apply() - "sslBaseExpression.psc" Line 64
    [alias ActorAlias003 on quest SexLabThread00 (09061EEF)].sslActorAlias.RefreshExpression() - "sslActorAlias.psc" Line 2241
    [alias ActorAlias003 on quest SexLabThread00 (09061EEF)].sslActorAlias.SyncThread() - "sslActorAlias.psc" Line ?
    [alias ActorAlias003 on quest SexLabThread00 (09061EEF)].sslActorAlias.SyncActor() - "sslActorAlias.psc" Line ?
[12/16/2021 - 04:14:09PM] ERROR: Cannot access an element of a None array
stack:
    [alias RegistrySlot370 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.GetLipFixedPhase() - "sslBaseExpression.psc" Line 330
    [alias RegistrySlot370 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.IsLipFixedPhase() - "sslBaseExpression.psc" Line 371
    [alias RegistrySlot370 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.ApplyPhase() - "sslBaseExpression.psc" Line 75
    [alias RegistrySlot370 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.Apply() - "sslBaseExpression.psc" Line 64
    [alias ActorAlias004 on quest SexLabThread00 (09061EEF)].sslActorAlias.RefreshExpression() - "sslActorAlias.psc" Line 2241
    [alias ActorAlias004 on quest SexLabThread00 (09061EEF)].sslActorAlias.SyncThread() - "sslActorAlias.psc" Line ?
    [alias ActorAlias004 on quest SexLabThread00 (09061EEF)].sslActorAlias.SyncActor() - "sslActorAlias.psc" Line ?
[12/16/2021 - 04:14:10PM] ERROR: Cannot access an element of a None array
stack:
    [alias RegistrySlot370 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.GetLipFixedPhase() - "sslBaseExpression.psc" Line 330
    [alias RegistrySlot370 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.IsLipFixedPhase() - "sslBaseExpression.psc" Line 371
    [alias ActorAlias004 on quest SexLabThread00 (09061EEF)].sslActorAlias.RefreshExpression() - "sslActorAlias.psc" Line 2242
    [alias ActorAlias004 on quest SexLabThread00 (09061EEF)].sslActorAlias.SyncThread() - "sslActorAlias.psc" Line ?
    [alias ActorAlias004 on quest SexLabThread00 (09061EEF)].sslActorAlias.SyncActor() - "sslActorAlias.psc" Line ?
[12/16/2021 - 04:14:10PM] SEXLAB - ActorAlias[bandit]  - Expression.Applied(Sad) Strength:7; OpenMouth:False; IsLipFixed:False
[12/16/2021 - 04:14:10PM] ERROR: Cannot access an element of a None array
stack:
    [alias RegistrySlot369 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.GetLipFixedPhase() - "sslBaseExpression.psc" Line 330
    [alias RegistrySlot369 on quest SexLabQuestRegistry (090664FB)].sslBaseExpression.IsLipFixedPhase() - "sslBaseExpression.psc" Line 371
    [alias ActorAlias003 on quest SexLabThread00 (09061EEF)].sslActorAlias.RefreshExpression() - "sslActorAlias.psc" Line 2242
    [alias ActorAlias003 on quest SexLabThread00 (09061EEF)].sslActorAlias.SyncThread() - "sslActorAlias.psc" Line ?
    [alias ActorAlias003 on quest SexLabThread00 (09061EEF)].sslActorAlias.SyncActor() - "sslActorAlias.psc" Line ?

That specific stack dump occurs probably a hundred times in the log and I only had sex like 10 times maybe before the crash. Anyway lemme know if you want to look at the entire pap log and or the crash log. Thanks for checking it out in advance :) .

OsmelMC

OsmelMC

Posted
Posted
3 hours ago, Martok73 said:

@OsmelMC @Ashal Sorry to bother y'all again, but just had a crash and had a huge amount of these errors in the papyrus, and a very strange .net crash log. The crash prolly has nothing to do with sexlab, but these papyrus errors have the sexlab questregistry and sexlab thread reference in them so I thought I should probably share the part that is repeating over and over in the log for you to look at, "just in case"...

 

It's under the spoiler tag so as to not take up too much room:

  Reveal hidden contents

That specific stack dump occurs probably a hundred times in the log and I only had sex like 10 times maybe before the crash. Anyway lemme know if you want to look at the entire pap log and or the crash log. Thanks for checking it out in advance :) .

 

 

The stack Dump are made for some Mods just to track many things at the same time. 

 

Usually is enough with disable all the Debug options of your installed Mods, but some times the Mod author don't allow disable it.

 

 

If you are not making Mods or fixing scripts, is better if you keep the logs disabled on the Skyrim.ini until somebody ask you for the "Papyrus.0.log". Keep the logs enabled allow the Mod author's track the issues but some of the errors in the logs cause CTD just if you are tracking the errors.

Martok73

Martok73

Posted
Posted
2 minutes ago, OsmelMC said:

 

 

The stack Dump are made for some Mods just to track many things at the same time. 

 

Usually is enough with disable all the Debug options of your installed Mods, but some times the Mod author don't allow disable it.

 

 

If you are not making Mods or fixing scripts, is better if you keep the logs disabled on the Skyrim.ini until somebody ask you for the "Papyrus.0.log". Keep the logs enabled allow the Mod author's track the issues but some of the errors in the logs cause CTD just if you are tracking the errors.

I've been having issues with a few mods all of a sudden (was working fine then for no reason they started throwing errors), so I keep the log on to track those errors. I've been noticing over the last week roughly several errors popping up that were not there before, and have been having strange CTDs and each crash log (netscriptframework) is showing different errors and the CTDs so far have not had the same cause twice. That stack dump I sent has not been there before and by tracing the numbers it is directly linked to SexLab.esm so yeah I was concerned that now all of a sudden it's throwing errors when it hadn't done it before. The 09 part of the 090664FB number is where my sexlab.esm is located in my load order and as I said it has never done that before, this error stack dump is new to me, so I was abit concerned about it and what it actually means? It is only throwing that stack dump error during a sex scene, as long as there is no sex, there is no error in the log, so what is causing it?

Wolfblade57

Wolfblade57

Posted
Posted
On 12/15/2021 at 10:43 PM, Samson Nite said:

Hi Ashal,

I had an issue for Papyrus Utility Warning/Error for SL frame 1.63 for SE version.

I finally nailed down the cause. It was "sslSystemConfig.pex" causes the error.

I installed SL 1.63 except this file(kept old version file/ SL 1.63beta9), and it worked without any error. SL informed 1.63 SE is updated successfully.

 

Can you look into this matter and fix for us????? Thank you always for your work !!! 

Yep i am Still having the same issue but systemconfig is doing nothing to fix it for me, unless i am having some irregular issue, but i also using AE version.

seventhsword2

seventhsword2

Posted
Posted (edited)

okay since the last patch this mod causes a crash to desktop after the bethesda logo shows on startup

I know it is this mod as i have disabled  all non-nexus mod  except for Tawoba remastered and it runs fine, but when i enable sexlab it crashes at the logo (all the other disabled mods are sexlab dependent or Shlongs of skyrim related)

Edited by seventhsword2
OsmelMC

OsmelMC

Posted
Posted
7 hours ago, Wolfblade57 said:

Yep i am Still having the same issue but systemconfig is doing nothing to fix it for me, unless i am having some irregular issue, but i also using AE version.

The only PapyrusUtil warning I know is the one from use the Nexus version over the SexLab PapyrusUtil version. Is because the version included on the SexLab is newer than the officially released.

 

So make sure that none Mod be overwriting the SexLab Framework files and remove any other PapyrusUtil you may have installed.

 

PS: Replace files with older versions is the worst idea ever (even if solve your issue, is almost sure that will make new ones and possibly worst)

OsmelMC

OsmelMC

Posted
Posted
13 minutes ago, seventhsword2 said:

okay since the last patch this mod causes a crash to desktop after the bethesda logo shows on startup

I know it is this mod as i have disabled  all non-nexus mod  except for Tawoba remastered and it runs fine, but when i enable sexlab it crashes at the logo (all the other disabled mods are sexlab dependent or Shlongs of skyrim related)

 

The most common users error right now is install the wrong version of the SexLab, because many of the users are being receiving the Steam AE basic update without notification and others are being installed the mod to rollback that update.

 

My recommendation: Try both versions (the official 1.63 for SE and the 1.64b for AE)

By the way the AE version need another Mod from Nexus and that Mod need to be updated because is the one that keeps the SexLab compatible with the new AE updates.

elfdrow

elfdrow

Posted
Posted
1 hour ago, OsmelMC said:

 

The most common users error right now is install the wrong version of the SexLab, because many of the users are being receiving the Steam AE basic update without notification and others are being installed the mod to rollback that update.

 

My recommendation: Try both versions (the official 1.63 for SE and the 1.64b for AE)

By the way the AE version need another Mod from Nexus and that Mod need to be updated because is the one that keeps the SexLab compatible with the new AE updates.

can confirm the error. CTD on tittle screen load on AE 1.6.342

only mod causing this one  is the SL framework.

the address library for SKSE plugin and SKSE has already been updated to this version. so it looks like SL 1.64b is not playing nice with it's new friends XD

PippinTom

PippinTom

Posted
Posted
7 minutes ago, elfdrow said:

the address library for SKSE plugin and SKSE has already been updated to this version. so it looks like SL 1.64b is not playing nice with it's new friends XD

 

Which 1.64b ?

Because there are two - depends when did you download yours - current and previous one, with the same name. while older was for previous "update" of Anal Explosion.

1
elfdrow

elfdrow

Posted
Posted
18 minutes ago, PippinTom said:

 

Which 1.64b ?

Because there are two - depends when did you download yours - current and previous one, with the same name. while older was for previous "update" of Anal Explosion.

now that did the trick. I didn't know there were 2 different files for the same version.

but the one that is for download right now. don't cause any CTD on load. and seems to works well. thank @PippinTom

 

probably what is happenening to @seventhsword2 is the same thing. so just in case. download the SL framework again. even if it has the same version name... is not the same version XD

Ghostman7nz

Ghostman7nz

Posted
Posted

I ran into an issue where I installed the most recently uploaded file  with the new util files into my game and for some reason the mod manager didn't delete all of the old files. It took me hours of testing to finally pin down the cause of the crash on load, but once I completely uninstalled the sexlab framework and then installed the current version again it fixed all the crashing issues.

I think it would not have happened with a change to the file name to 1.64c, though small things like that are easy to miss

OsmelMC

OsmelMC

Posted
Posted (edited)
1 hour ago, Ghostman7nz said:

it would not have happened with a change to the file name to 1.64c, though small things like that are easy to miss

 

Probably but the last update was just for the PapyrusUtil and technically is another Mod even when comes with the SexLab. 

 

I suppose in this case would be better if the PapyrusUtil update was released just independent instead of rebuild the SexLab setup with the new PapyrusUtil.

 

 

By the way I just noticed that in fact was released on Nexus, two days ago, the version 4.2 for SE/AE

Edited by OsmelMC
zwdragonbone8314

zwdragonbone8314

Posted
Posted

Hi, I just reinstalled the skyrim AE and upgraded the SKSE64 to 2.1.4. I have upgraded all the necessary core mods to the lastest version. I think sexlab Framework 1.64b might need to be upgraded as it is not compatible with the lastest SKSE64. I found out by enable the mod on MO2 one by one and find out that the current 1.64b with SKSE2.1.4, I got ctd when launch the game. When I took out sexlab, I can launch the game normally. 

 

Not try to push for upgrade to Ashal, just though he should know about that.

1
Ashal

Ashal

Posted
  • Author
Posted
3 hours ago, zwdragonbone8314 said:

Hi, I just reinstalled the skyrim AE and upgraded the SKSE64 to 2.1.4. I have upgraded all the necessary core mods to the lastest version. I think sexlab Framework 1.64b might need to be upgraded as it is not compatible with the lastest SKSE64. I found out by enable the mod on MO2 one by one and find out that the current 1.64b with SKSE2.1.4, I got ctd when launch the game. When I took out sexlab, I can launch the game normally. 

 

Not try to push for upgrade to Ashal, just though he should know about that.

 

Redownload 1.64b and/or upgrade papyrusutil to 4.2. The CTD at startup that came with the update to 2.1.4 was fixed already and the file was reuploaded with it.

2
zwdragonbone8314

zwdragonbone8314

Posted
Posted
46 minutes ago, Ashal said:

 

Redownload 1.64b and/or upgrade papyrusutil to 4.2. The CTD at startup that came with the update to 2.1.4 was fixed already and the file was reuploaded with it.

Hi thanks for telling me. I have already upgraded the papyrutil to 4.2, but I still got ctd on start.  I have not redownload the sexlab 1.64b yet. I will redownload it and try again. 

feyrisnyannyan

feyrisnyannyan

Posted
Posted

Something strange in the 1.64b version.

Installed the framework with all it's requirements.

Started a fresh game, installed framework in MCM.

However, no animations would play, not even with a matchmaker spell.

After a long while of searching what is going on,

randomly tried the "Rebuild & Cleanup/Clean System" in the MCM of the framework.

It fixed the issue and it is working as normal now.

 

This should not happen in a fresh installation should it?

SquatsAreLife

SquatsAreLife

Posted
Posted (edited)

I have the same CTD as zwdragonbone8314. All my mods are upgraded to SKSE64 2.1.4 and Skyrim 16.342. Once I install 1.64b I have CTD at startup. If I disable Sexlab 1.64b the games runs normally. I'll try and see if another mod is involved.

 

Update:

removing 1.64b from MO2 and reinstalling fresh worked for me.

Edited by Eileen1968
Zugger

Zugger

Posted
Posted (edited)

Not sure if this is the right place to ask, but I ran into a problem that wasn't there before - SL scenes use Gender-Priority when deciding actor role. So, if I approach female NPC with SoS addon(gender is set to Male in SL) and initiate say a BJ scene - she would always be the one performing the oral side.

 

Am I missing something? Some new settings?

 

NVM, It worked before because I initiated the scenes through SLEN which auto adjusted gender...Although, if anyone has better idea, I'm all ears :)

Edited by Zugger
RyukyuShin1997

RyukyuShin1997

Posted
Posted
16 hours ago, Ashal said:

 

Redownload 1.64b and/or upgrade papyrusutil to 4.2. The CTD at startup that came with the update to 2.1.4 was fixed already and the file was reuploaded with it.

Did all that, and it's still broken

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
Go to topic listing
×
×
  • Create New...