Arizona_Steve

I use plain old Sexlab - I've never tried this with P+.

Yeah, the victim is an issue that I have wrestled with for a long time. The problem here is that SexLab does not formally identify a victim - instead position 0 is used unless the animation has the "femdom" tag, in which case it should be the first male position. I try to get around it by attempting to identify the victim position based on some of the other available animation tags, it works the vast majority of the time. But other than trying to figure out the victim position, my tag analysis code is mostly concerned with who gets a strapon and who doesn't. Arousal level only applies to attacker positions. The victim could have zero arousal despite a non-zero arousal threshold being set. Attackers do run to the victim.

RS works with SexLab Aroused to limit sex acts to those NPCs that are aroused, so that is another means to limit who does the chasing. It also prevents a sex act from starting under all the circumstances you mention, for the player at least. Although delays and race conditions may cause the sex act to start if (for example) an alchemy station is activated between the player check and the start of the sex act. It's not perfect by any means but it works 99% of the time.

Had a good laugh at this. You will be happy to know I have fixed this egregious and inexcusable oversight on my part by uploading screenshots of the MCM (version 20250121 no less).

Bump for new version. For those who have altered the code above I would recommend sticking with 20230107, which remains available in the downloads. Version 20250121 REQUIRES SEXLAB VERSION 1.66b OR ABOVE This version takes advantage of a flag that I added to SexLab to bypass the actor sort when creating a thread. This has allowed me to remove a significant amount of Papyrus code from the actor set-up and eliminates some possible issues as a result. I have also added an additional toggle that will set SexLab Arousal exposure to zero when a sex act completes. This can avoid a situation where an NPC engages in multiple sex acts due to the selected animation not being one that reduces exposure at the end. Been running this in my own game for several months now, so it should be solid.

If I can make a suggestion - one thing I have never seen anyone mod into Skyrim or Fallout is a denim skirt of any sort. If someone made this it would be an instant download for me. Don't care if Fallout 4 or Skyrim - I would convert to Skyrim for my own use.

1 - Yes. The beauty of CommonLib-NG is that you upgrade SKSE and the address library and things "just work". As Todd eloquently puts it. 2 - If you have animal-animal animations available, Random Sex can match 'em up.

Thanks, appreciate the detailed response. I'll have to spend some time getting my head around the tag notation before trying to port anything over.

So would this allow a female actor (with strapon) to take the dominant position in a M/M animation? And a female (without strapon) to take the submissive position if the animation is anal or oral? Looking to do a Random Sex port - sounds like I would not need my C++ code that handles animation and actor selection.

Just to add - biggest request for me is per-thread gender assignments - or simply allowing the NPC sorting to be disabled on a per-thread basis. As of now I have to do some hacking in Random Sex to make things work right there.

Been a while since I've been in here as I was converting a bunch of outfits and followers to CBBE (hair clipping, in particular, is an issue with followers). @Daemia - Thanks for the Polish translation. If Bethesda messes with Skyrim again I'll make sure that's included in the update. Thanks for the patches and comments. I have no issues with people adjusting things to suit their requirements. I include Papyrus source code for that reason, and have a link to my C++ source in my OP.

Just discovered this and am following with interest. I'll confess to having considered rewriting SexLab into (mostly) C++ and CommonLib NG, but didn't want to offend Ashal by doing so.

Yeah, thinking about this a little more, most of my followers have had the custom bodies and textures stripped out which might contribute to being able to run so many on my system. That's a lot of work so I automated a lot of the stripping out of extraneous stuff with Java code.

Hmm... from someone who has around 800 followers in his game, the biggest differences are the RAM (16GB vs 64GB) and the graphics card (6700xt vs 4090). It does sound like a resource issue, as a bad mesh on one or more followers is usually an insta-CTD.

You can use onEquipped(Actor npc) and onUnequipped(Actor npc), attaching both of these events to the item in question. The actor equipping the item is passed in as a parameter.