Jump to content

Weird teleporting on sex start


Recommended Posts

Posted

I really have no idea what is causing this.

Basically, whenever sex starts, seemingly from any mod (babo, defeat, estrus etc.) my character teleports to a random location, not the Giant Camp as is the known problem. Last time was a falmer cave somewhere. Now, if I get my character away from the location and another sex initiates elsewhere, the location changes. Starting teleport is disabled in sexlab. 
Posting modlist here would be too much, it's way too large. I'm just gauging to see if anyone else has experienced and fixed this. 

Posted

There was a bug in v163_BETA9 where for some reason a thread could get stuck in the wrong state after being used. Basically the scene marker is not removed and gets reused for the next scene that uses that thread. The "official" workaround for this is to use SL's MCM to clean/reset/restart SL. The more surgical workaround that I deviced is to loop through each thread in SL, and remove the marker:

Threads[i].CenterRef = none
Threads[i].CenterAlias.Clear()

 

Both work, but I like my approach better as it seems a bit overkill to reset everything every time this happens. Now as for why it happens, I'm not sure. I haven't seen this issue in a long time myself, so I've forgotten the details.

Posted (edited)

Thanks for the reply and suggested workaround, although what do you mean by looping through the threads and removing that? Or rather, how do I do that? I don't think I've ever encountered an issue like this, so I'm not familiar with the method.

 

Edit: I am assuming it's done in xEdit of course, but I am still quite lost.

 

Edited by Pump-a-rump
Posted

I have experienced in the past, back mainly when I was playing 1.5.80 but also periodically in 1.5.97. (I've had one giant camp thing happen in 1.6.1170 so far since February).

 

Back when, I associated it with what I might call "resource deficient" play, ie, for whatever reason (clashing mods, trying to do too much with too little, whatever) , my game was experiencing repetitive, increased lag and other visible signs of oddity leading up to the occurrence. Associated saves (when the game didn't eventually crap out from it) often showed signs of stress including large numbers (ie thousands)  of excess stacks/frames etc, when examined with Fallrim Re-saver...

 

My "solution", was to reduce load wherever I could. And cope where I couldn't.

Posted (edited)
42 minutes ago, Pump-a-rump said:

Or rather, how do I do that?

 

Papyrus. If you're not planning on getting into scripting I'd recommend you just use the SL MCM to reset everything; otherwise plan to spend a few days/a week setting it up - the first time is always complicated.

 

19 minutes ago, anjenthedog said:

My "solution", was to reduce load wherever I could.


Its entirely possible the reason I haven't seen this issue in ages, is because the last time might have been around the same time I started increasing my Papyrus budget to silly amounts. If Papyrus load is causing this, it would seem quite likely that there's a race condition of some kind in SL.

Edited by traison
Posted

Alright, I appreciate the warning. Unlikely I'll be getting into Papyrus for the time being. The cleaning does seem like a hassle, but should be okay if I export my settings. Thanks for helping out, I see you usually respond to a lot of threats here. Thanks for doing your thing!

Posted
4 minutes ago, Pump-a-rump said:

The cleaning does seem like a hassle, but should be okay if I export my settings.

 

This shouldn't be necessary, but perhaps you should do it before the first reset just in case.

Posted
5 hours ago, traison said:

The "official" workaround for this is to use SL's MCM to clean/reset/restart SL.

 

Actually there is one more, less drastic way of dealing with thread scripts, not sure if available in bare SLF but for sure present in SL Utility Plus, and is called "restart threads" - takes few seconds to complete, and from what I've observed inspecting savegame in ReSaver - it reInits all 15 quests/instances dealing with any crap (values) that could have been imprinted in (co)save and hard to shake off otherwise.

I'm not a strictly technical guy, so my description may sound improvised, but I hope it's understandable nonetheless.

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...