Every actor (npc and player) cannot be added to sexlab to start animations

[heilhobo]

Attached are all relevant logs from papyrus and mo2. Uninstalled some mods and started a new game and realized 0 sexlab scenes could start. Not even the debug spell in sexlab could trigger one. Player, npc, doesn't matter. Everyone gets the error "Failed to add actor -- They were unable to fill an actor alias" or sometimes it will tell me they cannot be added to thread as they are already part of it.

 

Troubleshooting steps taken:

1. Stopping animations in sexlab and going to zaz to free player from ai and restore controls as debug didnt work in game.

2. Started new game and can't trigger even masturbation anims in the alternate life cell.

3. Restored local files and redowngrading

4. Making new mo2 profile, only enabling gameplay and graphic mods plus sexlab and aroused

5. Uninstalling completely, reinstalling, re downgrading, reinstalling skse and engine fixes.

6. Moving papyrus above and below sexlab and sexlab p+ in mo2 (neither worked)

7. Downloading a new sexlab file and sexlab p+, deleting old ones and installing the fresh downloads.

8. Deleting everything from overwrite folder besides bodyslide, mcm recording(havent run on new games ive made to test) and racemenu presets and re-running tools

 

General testing process I've done is start new game, wait for all mcm's to load. install sexlab. Enable debug then attempt the spell.

 

At this point I have no idea what could be causing the issue besides some weird mod issue that I have no idea what could do it.

SexLabDebug.0.log loadorder.txt modlist.txt plugins.txt Papyrus.0.log

Edited January 1, 2024 by heilhobo

[traison]

Quote

Error: Method SetActorEx not found on sslActorAlias.

 

...and the problem comes from here:

 

Quote

[12/31/2023 - 12:30:46AM] SexLab  - SexLab v2.0 P+ - Installing...

 

Make sure nothing is overwriting P+'s changes to sslthreadcontroller.pex, otherwise get rid of P+.

[heilhobo]

23 minutes ago, traison said:

 

...and the problem comes from here:

 

 

Make sure nothing is overwriting P+'s changes to sslthreadcontroller.pex, otherwise get rid of P+.

Currently going through a almost bare minimum mod setup and disabling things to try and get it to work. this is the image of my frame work and pplus. the p plus shows nothing is over riding it at all. 

[heilhobo]

28 minutes ago, traison said:

[12/31/2023 - 12:30:46AM] SexLab  - SexLab v2.0 P+ - Installing...

wait which log did you find this in? I can't find this. I did try a new game with p+ disabled and still had the same issue tho

[heilhobo]

Here are current logs. Papyrus at bottom says actor present during alias check, usually this will fix itself, but is a sign thread did not close cleanly. Is there a way to force close the thread? i think this line might be the issue?

Papyrus.0.log SexLabDebug.0.log

[quarzo]

well personally the times i try use P+ allways have problems. try firts sexlab/clean and build, if not luck disable/unistall p+

[heilhobo]

still having issues even with p+ completely removed from my mo2. Like i removed dat bitch from even the hidden files. So i know it isnt pplus

[traison]

48 minutes ago, heilhobo said:

wait which log did you find this in? I can't find this.

 

The papyrus log from the OP.

 

48 minutes ago, heilhobo said:

I did try a new game with p+ disabled and still had the same issue tho

 

Same symptoms, different problem (like you already discovered):

Quote

[01/01/2024 - 03:27:56AM] Info: SEXLAB - FATAL - Thread[0] AddActor(Prisoner) - AddActor(Prisoner) -- Failed to add actor -- They have been already added to this thread

 

 

35 minutes ago, heilhobo said:

Is there a way to force close the thread?

 

There's a button to clean SL in SL's MCM, that's the intended way to clear threads as far as I can tell.

 

Edit: And yes like @quarzo said, P+ is broken as far as I can tell. That, or people keep installing it wrong. Never looked into it myself. Generally though when people come here with issues related to animations not starting, most of the time its P+ seemingly having removed some base function from SL.

Edited January 1, 2024 by traison

[heilhobo]

I did reinstall a mod I've had problems with in the past. Thought if I left in but disabled it shit would work fine? Anyway i enabled it and it threw the error

 

0xffffffff (-1). 

 

google says this is a space issue, but that makes 0 sense as I'm running basically no script mods currently and i have a 4 tb nvme ssd that skyrim runs on with 2.75 free and over 20 gigs of gen 5 ram free even with skyrim is running.

[heilhobo]

4 minutes ago, traison said:

There's a button to clean SL in SL's MCM, that's the intended way to clear threads as far as I can tell.

 

Edit: And yes like @quarzo said, P+ is broken as far as I can tell. That, or people keep installing it wrong. Never looked into it myself. Generally though when people come here with issues related to animations not starting, most of the time its P+ seemingly having removed some base function from SL.

Edited just now by traison

Also I've cleaned it every new game I start, which I'm doing every time im disabling mods. p+ has been installed for a few months with no issues till the 30th and issue is there with out it. 

[traison]

2 minutes ago, heilhobo said:

Anyway i enabled it and it threw the error

 

Where? If that's the return code from a DLL I'd assume its just a generic error for "something went wrong". General convention is that 0 = SUCCESS, everything else is bad, but its up to the programmer to give meaning to the numbers. Some follow the standard Windows error codes, most don't.

[heilhobo]

Ah that was what it said in the console. It is a standard windows error code, but idk if that error code from the mod has the same meaning as the windows one.

 

It was public plaything. I enabled the mod hit get started and it threw that code in the console. It was one of the ones i uninstalled right before game stopped working properly as i could never get it to work correctly.

 

edit: Don't think any of the mods i uninstalled could cause this issue though as ive started new games since then

edit 2: none of the mods downloaded after the uninstall are currently active as disabling all of the new mods was the first thing i tried

Edited January 1, 2024 by heilhobo

[heilhobo]

Ok, I have ran out of mods to disable. I have sexlab, sky ui (which is required to install sexlab) fnis, sos, and alternate start with unofficial skyrim special edition patches.

 

what the fuck could it be at this point?!?!?

[traison]

Just now, heilhobo said:

I have ran out of mods to disable

 

Still using the same save?

[heilhobo]

made a new game every single time I disabled mods

 

so ive got like 60 new games in my save list

Edited January 1, 2024 by heilhobo

[traison]

If the error in the papyrus log is still the same (actor already added) then pretty much the only remaining option is that the version of SL you're using is bugged.

[heilhobo]

ok deleting everything including all my mo2 profiles. uninstalling all mods from virtual folder. deleting my skyrim se folder and reinstalling with skse and only installing sky ui sexlab framework alternate life and unofficial skyrim still have the issue.

 

It literally has to be the sexlab somehow despite deleting the old one and downloading a new one and installing that was the first thing i did

[traison]

I'm on 1.5.97 so I won't be testing it live but, which SL version are you using (maybe send a link?). I'll go through the script to see if there's something obvious going on there.

[heilhobo]

I am also on 1.5.97, I'm using slf v163. Downloads 2 through 4

also didnt work when i deleted the old one and installed a different one. I have even deleted the documents skyrim folder. So literally every thing skyrim at this point has been deleted and still having the issue.

 

There is no way all of these are broken??? I included the ones i just downloaded from the website and tried within last 10 minutes.

 

i've been modding skyrim for like 9 fuckin years at this point and have never ran into an error this persistent 

SexLabFrameworkSE_v163 (3).7z SexLabFrameworkSE_v163 (2).7z SexLabFrameworkSE_v163 (4).7z

[heilhobo]

reenabled papyrus logging cuz that got deleted with everything else. literally the same shit

SexLabDebug.0.log

[traison]

I'm running a customized version of v163 BETA 9, so if something went wrong it was between that and the version you just uploaded (3 times for some reason?).

 

That error message only comes from one location, and its when the following statement returns true:

Positions.Find(ActorRef) != -1

 

The callstack for the clean system option in SL's MCM looks something like this:

1. sslConfigMenu.OnSelectST (in state CleanSystem)
2. sslThreadSlots.StopAll
3. sslThreadSlots.StopThread
4. sslThreadController.Initialize
5. sslThreadModel.Initialize

Where the Initialize function in sslThreadModel sets Positions:

Positions         = PapyrusUtil.ActorArray(0)

 

So, assuming everything you've said is correct, what I'd do next is add debug messages to AddActor in sslThreadModel and print the callstack for every call to that function. If you want to make it fancy, also print an identifier for ActorRef so that you can isolate when, and what added the player to a thread (presumably) prematurely.

 

Edit: If this still doesn't lead to anything, I'll do a checksum/diff of BETA9 against the uploaded version.

Edited January 1, 2024 by traison

[traison]

1 hour ago, heilhobo said:

Can you link like a youtube tutorial on how to do that? cuz i got no idea where to even begin doing that.

 

Not really, setting it up for the first time is potentially going to take a lot of effort as well. Gonna be easier if I do it. Replace your existing script with the one uploaded here. Then analyze or post the papyrus log here (not the SL debug log).

 

If you analyze it yourself, search for lines starting with ">>>".

sslThreadModel.pex

[heilhobo]

I literally figured it out with help from computer science major thread, figured out how to downgrade creation kit to compile it. I am waiting for its scripts to unpack lol.

 

ty for preexisting file creation kit is low key aids to use

[heilhobo]

Papyrus.0.log

 

here are the logs post adding line of code

Papyrus.0.log SexLabDebug.0.log

[traison]

The issue comes from sslEffectDebug, it adds the player twice and the thread fails to start because an error (actor already exists) occurs in AddActor:

[01/01/2024 - 09:18:53AM] Info: >>> AddActor(Prisoner [20], ...)
stack:
	<unknown self>.Debug.TraceStack() - "<native>" Line ?
	[SexLabThread00 (06061EEF)].sslthreadcontroller.AddActor() - "sslThreadModel.psc" Line ?
	[SexLabThread00 (06061EEF)].sslthreadcontroller.AddActors() - "sslThreadModel.psc" Line ?
	[SexLabQuestFramework (06000D62)].sexlabframework.StartSex() - "SexLabFramework.psc" Line 3325
	[SexLabQuestFramework (06000D62)].sexlabframework.QuickStart() - "SexLabFramework.psc" Line 3329
	[Active effect 1 on  (00000014)].sslEffectDebug.OnEffectStart() - "sslEffectDebug.psc" Line 25
[01/01/2024 - 09:18:53AM] >>> Actors in thread (0) before adding new actor:
[01/01/2024 - 09:18:53AM] SEXLAB - NOTICE: ValidateActor(Prisoner) -- TRUE -- MISS
[01/01/2024 - 09:18:53AM] SEXLAB - ActorAlias[Prisoner] SetActor([Actor < (00000014)>]) - [sslActorAlias <alias ActorAlias004 on quest SexLabThread00 (06061EEF)>]
[01/01/2024 - 09:18:53AM] Info: >>> AddActor(Prisoner [20], ...)
stack:
	<unknown self>.Debug.TraceStack() - "<native>" Line ?
	[SexLabThread00 (06061EEF)].sslthreadcontroller.AddActor() - "sslThreadModel.psc" Line ?
	[SexLabThread00 (06061EEF)].sslthreadcontroller.AddActors() - "sslThreadModel.psc" Line ?
	[SexLabQuestFramework (06000D62)].sexlabframework.StartSex() - "SexLabFramework.psc" Line 3325
	[SexLabQuestFramework (06000D62)].sexlabframework.QuickStart() - "SexLabFramework.psc" Line 3329
	[Active effect 1 on  (00000014)].sslEffectDebug.OnEffectStart() - "sslEffectDebug.psc" Line 25
[01/01/2024 - 09:18:53AM] >>> Actors in thread (0) before adding new actor:
[01/01/2024 - 09:18:53AM] >>> +++ Prisoner [20]
[01/01/2024 - 09:18:54AM] Info: SEXLAB - FATAL - Thread[0] AddActor(Prisoner) - AddActor(Prisoner) -- Failed to add actor -- They have been already added to this thread
stack:
	<unknown self>.Debug.TraceStack() - "<native>" Line ?
	[SexLabThread00 (06061EEF)].sslthreadcontroller.FATAL() - "sslThreadModel.psc" Line 1933
	[SexLabThread00 (06061EEF)].sslthreadcontroller.AddActor() - "sslThreadModel.psc" Line ?
	[SexLabThread00 (06061EEF)].sslthreadcontroller.AddActors() - "sslThreadModel.psc" Line ?
	[SexLabQuestFramework (06000D62)].sexlabframework.StartSex() - "SexLabFramework.psc" Line 3325
	[SexLabQuestFramework (06000D62)].sexlabframework.QuickStart() - "SexLabFramework.psc" Line 3329
	[Active effect 1 on  (00000014)].sslEffectDebug.OnEffectStart() - "sslEffectDebug.psc" Line 25
[01/01/2024 - 09:18:54AM] SEXLAB - ActorAlias[Prisoner] ClearAlias([Actor < (00000014)>] / [sslActorAlias <alias ActorAlias004 on quest SexLabThread00 (06061EEF)>]) - Actor present during alias clear! This is usually harmless as the alias and actor will correct itself, but is usually a sign that a thread did not close cleanly.
[01/01/2024 - 09:18:55AM] SEXLAB - NOTICE: StartSex() - Failed to add some actors to thread

 

So to summarize this thread (as I understand it now): The problem in the OP was P+, which is now gone. Since then you've been testing with some internal SL animation starting utility which turns out to potentially have a flaw, or you're using it in a way that wasn't intended.

 

Try matchmaker again, if the last time you tried it was before P+.