SexLab Scenes Literally Breaking Beds

[H4tW4lrus]

So, after a Sexlab scene, no matter the duration, I am unable to interact with beds afterwards. I've stopped using beds during scenes but I really want to fix this bug.

 

Any help would be appreciated.

[traison]

Things that come to mind:

1. Have you tried the epc command?
2. Have you tried using something else, like an alchemy lab, then testing beds again?
3. Do you have that Better 3rd Person Selection mod, or a mod like it?
4. Is the bed actually still a FURN (furniture) when it's broken?
5. Is there a script attached to the bed that's blocking activation? (ie. any sleeping related mods?)

[H4tW4lrus]

So, responses to your suggestions:

 

1. Tried this command, no change.
2. Tried using an alchemy lab, beds were still usable afterwards, as was the alchemy lab. Tried other furniture too, scenes don't seem to break them. This issue seems to only be affecting beds.
3. Nope, no mods like that.
4. Yes. The bed is still usable in scenes and bed-related animations will still play as normal.
5. I use Go To Bed. I noticed that my version was out of date, so I updated, this did not fix the issue. I tried disabling the mod, the issue persists.

 

Is this a known bug? Is it a bug with SexLab Framework itself? 

[traison]

25 minutes ago, H4tW4lrus said:

Is it a bug with SexLab Framework itself?

 

Well, sort of. Typically if you interrupt an SL scene or otherwise just do things too quickly you can end up in a state where you can't activate things. Same can happen with ore deposits and most likely any other object that uses the SetVehicle or DisablePlayerControls methods. Easiest fix for this is to "do what you just did" or find another similar object - an alchemy table as an example.

 

But, since the alchemy lab thing didn't fix it, I'm still going to say you have a script attached to that bed which called BlockActivation. Question is, how does one test this easily. You may be able to do something with ReSaver and the bed reference id. Alternatively, if you've been keeping up with mod script sources, you can use Notepad++ to search though all *.psc files for BlockActivation.

 

Edit: Does disable/enable (in the console) purge attached scripts? Not sure.

Edited February 4, 2023 by traison

[H4tW4lrus]

I'll be sure to try those, thank you :).

 

Something interesting though, it doesn't happen if I'm using Sexlab Privacy, beds are still usable after scenes with that mod active.

 

Also tried it on a clean save, the issue is still there unless SL Privacy is active.

 

Edit: The reason I'm asking despite finding a "fix" in SL Privacy is because I want to move away from that mod, but currently it's the only mod that makes beds usable after scenes involving them.

Edited February 4, 2023 by H4tW4lrus

[traison]

How about a link to that SL Privacy mod?

[H4tW4lrus]

Here it is, it's incompatible with Furniture Sex Framework so I haven't been using them together.

 

t

[traison]

That mod modifies sslThreadModel. I can't compare the decompiled script to the original from SL, there's too many differences created by the decompiler. However, since this fixes it, your issue is most likely that something else overrides and breaks sslThreadModel.

[H4tW4lrus]

Any idea on how to fix that then? I can't say I'm very good with all this stuff.

 

Would you still recommend looking into ReSaver?

[traison]

File conflict resolution is done with your mod manager. Don't know about vortex, but in MO2 you can use the Data tab on the right side of the main view. You can also find the SL mod and view it's Conflict tab to see which mods are overwriting its files.

[H4tW4lrus]

So, I'm a Vortex user but I found the files easily enough.

 

You were spot on, though ironically no mod mentioned thus far was doing it. Turns out it was Sexlab Separate Orgasms, that mod was overwriting Sexlab Framework's sslThreadController. I changed it so now that file comes from Sexlab Framework. I tested it out in game and everything seems to be alright now.

 

Thank you for all your help

[H4tW4lrus]

So, Vortex guide to finding the files in case anyone else has this issue.

 

Open Vortex. On the left side of the screen, go to 'Mods'

Search for the mod you're looking for by name.

On the right, click the orange button with the downwards arrow in line with the mod you searched for.

On the drop-down menu, click 'Manage File Conflicts'.

From there, you'll be able to see file conflicts as well as which conflicting file Vortex is prioritising.

There will be drop-down menus on the right-hand side inline with all files that are conflicting.

 

[Ralph.B]

I have no idea how to prevent this bug - but can offer a solution to fix a bed that the player can't use anymore after having sex in it. If the disable/enable command doesn't work, you can simply delete and respawn it with console commands. It's ab bit laborious to get it into the right place with console commands, so I recommend to use Jaxxons object mover. With this tool you can move it easily wherever you want.

[anjenthedog]

fwiw, console player.tai can solve the "inability to interact" problem encountered after some SL related scenes, especially when the scene has been interrupted (unexpected combat events for instance) and prematurely exits the animation handler. Sometimes the post-animation, player reset doesn't fire properly and you're left with (player) TAI in the OFF state. 

 

When I run into that issue, I also fire off a quick enableplayercontrols too, just to make sure. It's probably just ignorant voodoo on my part, but whatever. unless you're using some sort of mod driven attribute restrictors, it can't hurt. 

 

Edited March 12, 2023 by anjenthedog
words

[Eros2469]

How do you fix this with MO2. I'm having the same issue.

[traison]

1 hour ago, Eros2469 said:

How do you fix this with MO2. I'm having the same issue.

 

Answer to your question is already in this thread.

 

On 2/4/2023 at 5:34 PM, traison said:

Don't know about vortex, but in MO2 you can use the Data tab on the right side of the main view.

 

sslThreadModel.pex, mod providing the file is in the "Mod" column conveniently enough.

[Eros2469]

43 minutes ago, traison said:

 

Answer to your question is already in this thread.

 

 

sslThreadModel.pex, mod providing the file is in the "Mod" column conveniently enough.

I found the conflicting mod, I just didn't know if I just delete the file or if there's a way to change the order. Im very new to all of this

[traison]

Unless you can fix the script, your only option is pretty much to remove the mod that adds it. Simply removing the script has the chance of breaking the mod it belongs to, swapping one problem with another. You can obviously try it, just don't continue some serious playthrough while testing as it may end in disappointment.