slso SexLab Separate Orgasm LE

[WhatRules]

There is something wrong with the enjoyment progression. With arousal setting it only increases by 2% on stage advance, pressing the left button has no effect and there is no "enjoyment over time" as far as I can see. It's impossible to even reach orgasm like that. I'm using SLAX but I tried with the normal SL aroused and it makes no difference. If I don't use arousal as modifier it works though. I also think you should remove or decrease the stamina loss on stage advance. It's unfair.

 

Papyrus.1.log

[WhatRules]

On 2/12/2020 at 2:56 AM, Lupine00 said:

I'm not sure yet whether SLAX needs updating to work with latest SLSO or not.

In theory not. In practice, perhaps it does.

 

Will probably be a few days before I get a chance to look at this properly though.

Yes, it needs an update.

[Lupine00]

4 hours ago, saltshade said:

Yes, it needs an update.

I only see problems in multi-partner sex scenes, where it remains impossible to act on the other partners, even if they are selected.

This is a bit odd, as it should have nothing to do with SLAX.

 

The other issues, I do not see. I get plenty of enjoyment progression, and with a single partner, clicks are effective.

 

Are you allowing SLAX to overwrite SLSO?

[WhatRules]

2 hours ago, Lupine00 said:

I only see problems in multi-partner sex scenes, where it remains impossible to act on the other partners, even if they are selected.

This is a bit odd, as it should have nothing to do with SLAX.

 

The other issues, I do not see. I get plenty of enjoyment progression, and with a single partner, clicks are effective.

 

Are you allowing SLAX to overwrite SLSO?

Overwrite? There are no conflicts detected by MO.

[Lupine00]

22 minutes ago, saltshade said:

Overwrite? There are no conflicts detected by MO.

There won't be unless you install the SLSO patch for SLA/SLAR, which SLAX doesn't need.

 

Without that patch - or SLAX - SLSO doesn't work how you might expect because there's no arousal modification from SLSO orgasms.

 

 

Enjoyment changes shouldn't have anything to do with that though, which is one of the things puzzling me here.

The SLA(R) patch for SLSO and the SLAX behaviour are basically about handling mod events and arousal changes, so that you get appropriate arousal loss for orgasms, and in some cases appropriate arousal loss blockage for devices. i.e. the chastity handling in SLAX is a bit more refined than in the original SLSO patch.

 

The other mod I have that changes SLSO, is the SLS mod for mouth opening, but I had the multi-partner scene behavior before I added that.

 

This is something I want to look into when I seriously look at SLAX, but I'm procrastinating on doing that at the moment, for no good reason other than it's not a particularly fun job.

 

SexLab itself is fairly complicated, and I find some of the SLSO changes don't make sense to me. I remain uncertain if SLSO is simply wrong, or whether there are things in SexLab I'm not understanding properly. Resolving that to my satisfaction will be a lot of work with not much payoff.

[WhatRules]

42 minutes ago, Lupine00 said:

There won't be unless you install the SLSO patch for SLA/SLAR, which SLAX doesn't need.

 

Without that patch - or SLAX - SLSO doesn't work how you might expect because there's no arousal modification from SLSO orgasms.

 

 

Enjoyment changes shouldn't have anything to do with that though, which is one of the things puzzling me here.

The SLA(R) patch for SLSO and the SLAX behaviour are basically about handling mod events and arousal changes, so that you get appropriate arousal loss for orgasms, and in some cases appropriate arousal loss blockage for devices. i.e. the chastity handling in SLAX is a bit more refined than in the original SLSO patch.

 

The other mod I have that changes SLSO, is the SLS mod for mouth opening, but I had the multi-partner scene behavior before I added that.

 

This is something I want to look into when I seriously look at SLAX, but I'm procrastinating on doing that at the moment, for no good reason other than it's not a particularly fun job.

 

SexLab itself is fairly complicated, and I find some of the SLSO changes don't make sense to me. I remain uncertain if SLSO is simply wrong, or whether there are things in SexLab I'm not understanding properly. Resolving that to my satisfaction will be a lot of work with not much payoff.

The payoff will be that you can use arousal modifiers for SLSO, but I can understand if you're not bursting with excitement at the thought. However, you should discuss this with the author of SLSO, to get more clarification of how it works, and if there is something you can do about it. I'm playing with it off right now though, because that's the only thing that works.

 

Regarding the open mouth mod, is it normal that the mouth is open at the start of all scenes?

[Ed86]

10 hours ago, saltshade said:

There is something wrong with the enjoyment progression. With arousal setting it only increases by 2% on stage advance, pressing the left button has no effect and there is no "enjoyment over time" as far as I can see. It's impossible to even reach orgasm like that. I'm using SLAX but I tried with the normal SL aroused and it makes no difference. If I don't use arousal as modifier it works though. I also think you should remove or decrease the stamina loss on stage advance. It's unfair.

 

Papyrus.1.log 778.88 kB · 0 downloads

hm... as far as i can tell from that log, everything works as it should,  you didnt run a single sl scene so everything is fine

 

useless log aside, judging by description, you did not install slso

you didnot overwrite sexlab/sla scripts with slso ones, therefore slso works but nothing you do has any effect on scene

[Lupine00]

2 hours ago, saltshade said:

The payoff will be that you can use arousal modifiers for SLSO, but I can understand if you're not bursting with excitement at the thought. However, you should discuss this with the author of SLSO, to get more clarification of how it works, and if there is something you can do about it. I'm playing with it off right now though, because that's the only thing that works.

 

Regarding the open mouth mod, is it normal that the mouth is open at the start of all scenes?

My SLSO is working fine for normal 1 partner scenes, so it only makes a difference to multi-participant scenes, which I use a lot less, and which previously didn't have good support anyway. I kind of want that working right of course, but I suspect the problem is not SLAX, and is caused by some other mod, or simply won't show up when I test it on my dev machine.

 

With open mouth functionality, yes, it's normal for it to be open at scene start if you left it open in the previous scene.

You can even open it outside of sex, in a very ME way. It would be neat if doing that to an SLS tweaked guard or toll collector would add a kneel animation and initiate the appropriate response  

 

I think @Monoman1 could polish this a little by closing the mouth at scene end, so you always know for sure that you have to reopen it for a new scene, but it's good that we got it at all.

[7osisg4d]

I get crazy script issues upon enabling SLSO with SLSO, SLAX, and AC on both new or existing games. 

 

Enabling:

- SLSO

- Shrines

- SLSO VPs

- Apropos SLSO

- PSQxSLSO

 

 

Aroused Creatures will find new partners mid-scene, then magically fly between them. 

SLSO orgasms will proc right after it says that it's blocked for a victim, often several times at once!

After enabling the above, arousal goes down minimally after a scene with a male orgasm, even if the orgasm is at the very end.

The game orgasm bar will also fill up fully, but an orgasm won't happen for quite a while, often scene change.  When they do happen, a ton of orgasms can show up all at once:

 

 

Has anyone ever seen anything like this?

[OsmelMC]

@Ed86

Checking the SLSO sslSystemConfig I see to issues.

 

1. The script apparently have one small mistake when set de value of the minStage variable because check the stageCount that way:

 

if StageCount > 3

    minStage = 2

elseIf StageCount > 5

    minStage = 3

endIf

 

And that means the "StageCount > 5" part never run because 5 is always bigger than 3

 

2. In the same script the conditions related to aggressor orgasm and the stage are wrongly placed inside the GoToStage function. Resulting on the player can't take real control of the Animation even when the SexLab MCM "Disable Victims Control" is Disabled for debugging proposes.

The right place to set those conditions is on the event Update just inside the autoAdvance condition.

[Lupine00]

7 hours ago, 7osisg4d said:

Aroused Creatures will find new partners mid-scene, then magically fly between them. 

That's entirely Aroused Creatures bad behavior. Something like that going on is going to create chaos with SLSO.

 

7 hours ago, 7osisg4d said:

SLSO orgasms will proc right after it says that it's blocked for a victim, often several times at once!

After enabling the above, arousal goes down minimally after a scene with a male orgasm, even if the orgasm is at the very end.

You have script lag.

 

7 hours ago, 7osisg4d said:

The game orgasm bar will also fill up fully, but an orgasm won't happen for quite a while, often scene change.  When they do happen, a ton of orgasms can show up all at once:

It's more script lag.

 

Is the final orgasm a result of you ticking the Always Orgasms box by any chance?

As you don't describe your configuration in any detail, just the mods you have, it's impossible to say if the behavior is right or wrong.

 

 

SLSO will (probably) not be causing your script lag. Likely it's caused by some idiotic mod like HDT HH that just loads your game like crazy, or something that loads Papyrus specifically when a sex scene runs. Apropos possibly?

 

I made a patch for HDT HH that fixes the overloading.

 

Apropos is not a lightweight mod. I removed it and things have been better ever since.

If you use something like Sex Worker's Life, you can live without it and still have wear & tear.

There are many bugs in the W&T functionality anyway, and the means by which it calculates it isn't ideal either, because it takes no account of how long the sex lasts for, and provides no allowance for stretching or other genre conventions, not even as options, (however unrealistic, they are still genre conventions).

[Lupine00]

32 minutes ago, osmelmc said:

1. The script apparently have one small mistake when set de value of the minStage variable because check the stageCount that way:

 

if StageCount > 3

    minStage = 2

elseIf StageCount > 5

    minStage = 3

endIf

 

And that means the "StageCount > 5" part never run because 5 is always bigger than 3

Yes, I think that's even been mentioned before.

 

32 minutes ago, osmelmc said:

2. In the same script the conditions related to aggressor orgasm and the stage are wrongly placed inside the GoToStage function. Resulting on the player can't take real control of the Animation even when the SexLab MCM "Disable Victims Control" is Disabled for debugging proposes.

The right place to set those conditions is on the event Update just inside the autoAdvance condition.

The control handling is a little hairy overall. When I wanted to hack it so that I could click once and get an orgasm (for testing SLAX) I found some interesting behaviors you wouldn't expect. The design overloads the meaning of variables in non-obvious ways and handles the same condition in multiple places within some complex branching; it's inherently hard to maintain and debug. Some of this may have happened due to features creeping in.

 

I never entirely agreed with the decision to change the orgasm events, as it breaks many mods that are looking for the orgasm event and never see it.

 

Most recently, I found it broke TitD, which waited for the standard orgasm event to determine scene end and advance a quest. Quest never advanced, and of course the scenes couldn't be played again, but even if you could, the quest could never advance.

 

I had to reload, set the behavior to Always Orgasm and replay the scenes. Quest advanced.

 

IMHO, SLSO should play its own orgasm event for each orgasm, regardless of whether it's the last one.

Then at the end of scene, it should play the standard event too, regardless of whether there is a SLSO orgasm - unless the player specifically disables that with an option.

Then, SLSO supporting mods could safely ignore the standard event - if they've seen a SLSO orgasm - and look only at SLSO orgasms, and non-SLSO mods would function exactly as before.

 

The existing design not only breaks existing mods that aren't SLSO aware, it makes handling complicated inside SLSO aware mods because you need to know how SLSO is operating to decide whether to handle the standard event or not - because SLSO may not be present, or may not be configured to act like SLSO.

 

Too late now though, because SLSO has established a pattern of not playing the standard event if SLSO orgasms are enabled.

For a modder who wants to support orgasms properly in a mod, SLSO is quite painful, and it was totally avoidable.

 

If you want to know whether an orgasm was 'forced' or not, and what scene it occurred in, and handle the final orgasm, and also track sex events (orgasm or not) and whether they are forced or not, you have some real problems right now.

Instead of a nice clean system where you simply handle scene-start, and orgasm events, and get the data from there, you have to hook the stage end events and poke inside SexLab to find out if its the final stage or not (and then some annoying mod REPLAYS the stage) and what actors are partaking in what ways, and what animation is playing, then try and synch that data up to disconnected orgasm events. It is about as unreliable as anything can get in Skyrim.

[Ed86]

7 hours ago, osmelmc said:

Checking the SLSO sslSystemConfig I see to issues.

 

1. The script apparently have one small mistake when set de value of the minStage variable because check the stageCount that way:

 

if StageCount > 3

    minStage = 2

elseIf StageCount > 5

    minStage = 3

endIf

fixd

7 hours ago, osmelmc said:

2. In the same script the conditions related to aggressor orgasm and the stage are wrongly placed inside the GoToStage function. Resulting on the player can't take real control of the Animation even when the SexLab MCM "Disable Victims Control" is Disabled for debugging proposes.

The right place to set those conditions is on the event Update just inside the autoAdvance condition.

dunno it was writen like 2-3 years ago, so i dont remember much of this

but afaik SexLab MCM "Disable Victims Control" is useless, i dont see any code disabling hotkeys

code in GoToStage prevents timed and hotkey advance, which is what it should do

i've probably decided to patch one place rather than few

[Ed86]

7 hours ago, Lupine00 said:

I never entirely agreed with the decision to change the orgasm events, as it breaks many mods that are looking for the orgasm event and never see it.

 

Most recently, I found it broke TitD, which waited for the standard orgasm event to determine scene end and advance a quest. Quest never advanced, and of course the scenes couldn't be played again, but even if you could, the quest could never advance.

 

I had to reload, set the behavior to Always Orgasm and replay the scenes. Quest advanced.

 

IMHO, SLSO should play its own orgasm event for each orgasm, regardless of whether it's the last one.

Then at the end of scene, it should play the standard event too, regardless of whether there is a SLSO orgasm - unless the player specifically disables that with an option.

Then, SLSO supporting mods could safely ignore the standard event - if they've seen a SLSO orgasm - and look only at SLSO orgasms, and non-SLSO mods would function exactly as before.

 

The existing design not only breaks existing mods that aren't SLSO aware, it makes handling complicated inside SLSO aware mods because you need to know how SLSO is operating to decide whether to handle the standard event or not - because SLSO may not be present, or may not be configured to act like SLSO.

 

Too late now though, because SLSO has established a pattern of not playing the standard event if SLSO orgasms are enabled.

For a modder who wants to support orgasms properly in a mod, SLSO is quite painful, and it was totally avoidable.

 

If you want to know whether an orgasm was 'forced' or not, and what scene it occurred in, and handle the final orgasm, and also track sex events (orgasm or not) and whether they are forced or not, you have some real problems right now.

Instead of a nice clean system where you simply handle scene-start, and orgasm events, and get the data from there, you have to hook the stage end events and poke inside SexLab to find out if its the final stage or not (and then some annoying mod REPLAYS the stage) and what actors are partaking in what ways, and what animation is playing, then try and synch that data up to disconnected orgasm events. It is about as unreliable as anything can get in Skyrim.

SLSO's whole point is to break other mod orgasms, sexlab since 1.60 seperate orgasms they work exactly as you want, but no one gives a fuck about them and no one will ever support them, they have 0...(uh very little) reason to exist, they are irrelevant

this is one of main things slso fixes

there is compatibility option to always orgasm, it will never be enabled by default, because compatibility is a worst choice when you add new functionality

 

if ppl rely on orgasm event rather than animation end its shit coding mostly

idk, dont use Delzaron mods, they are broken mess that never gets finished, ill never forget broken dwemer milkers that break saves (idk if its even fixed)

 

idk what problems you're talking about, my mods have orgasm function wrapped inside and difference is 2-3 lines of variables setup

old system is shit

idk how you guess "what actors are partaking in what ways, and what animation is playing" unless you have huge manually tag sorted db of all animations stages with each stage tagged

sl has 2 types of animations - foreplay, tagged main animation, what you're saying would require huge sl and animation overhaul, which no one would give a fuck because old system is better

this is object programming, you create alias and fill it with your data, update when needed and purge when dont

 

if you want some improvements to slso im ready to hear it

if its "always orgasm" was better - get out

[Lupine00]

1 hour ago, Ed86 said:

SLSO's whole point is to break other mod orgasms, sexlab since 1.60 seperate orgasms they work exactly as you want, but no one gives a fuck about them and no one will ever support them, they have 0...(uh very little) reason to exist, they are irrelevant

this is one of main things slso fixes

there is compatibility option to always orgasm, it will never be enabled by default, because compatibility is a worst choice when you add new functionality

 

if ppl rely on orgasm event rather than animation end its shit coding mostly

idk, dont use Delzaron mods, they are broken mess that never gets finished, ill never forget broken dwemer milkers that break saves (idk if its even fixed)

I support SLSO and vanilla orgasms, so I do give a fuck, but ... of course Delzaron doesn't ... others support orgasms as best they can too, and care about it.

 

Personally, I'm going through trying to fix the worst problems in Things in the Dark, so I can play it, and others can play it, and it won't explode your game in a shattered heap of burning computer parts.

 

The milkers are working OK now, in that they run your script AND his, so you get MME milk, and you get the milk his quest needs (whether you need it or not), and it's a ridiculous way to get masses of free milk, because it adds one every 10 seconds or so as long as you remain in the milker.

 

Not saying any of that is your problem...

 

1 hour ago, Ed86 said:

sexlab since 1.60 seperate orgasms they work exactly as you want,

I'm not sure what you mean here. That you changed SLSO to work how I described above in 1.60 ?

 

If so, great ... though that means I need to make some changes to support it correctly again.

 

 

  

1 hour ago, Ed86 said:

idk how you guess "what actors are partaking in what ways, and what animation is playing" unless you have huge manually tag sorted db of all animations stages with each stage tagged

As it happens, I care about these things:

1) is the aggressive flag set? Which should indicate a rape.

2) is it a solo session? Can't be a rape, but must be masturbation.

3) does an orgasm occur? I want to know if it's a rape or non-rape orgasm, or a masturbation.

4) should orgasm be blocked by a belt or other chastity device? DD makes this rather complex to determine.

 

I obtain the answers to those questions and update my state accordingly.

I count every orgasm, and every forced orgasm separately, and don't count them if they are blocked by devices.

I don't look at the animation tags, except to determine whether the chastity device is blocking orgasm.

To do that, I only care about vaginal, anal, and oral tags.

I don't have to worry much about the many other tags that may be present or may not be present because it's an FB anim, and he put practically no tags on them.

 

As I've said many times ... one day I dream of going through and writing a new tag set for FB so that massive anim pack has the same detail of information as Leito or Anub. Still not done. Keep hoping somebody else will do it before I get to it.

 

 

  

1 hour ago, Ed86 said:

if you want some improvements to slso im ready to hear it

The new target selection mechanism delivered one of my big wishes. My cavil may also be fixed, depending on what you meant above.

 

Also, I did want a key to force open the PC mouth, but Monoman made one.

 

I guess a "debug" option for testing, where you can cause a "legitimate" instant orgasm would be useful. I modified my "dev" copy of SLSO to do that, as I needed it for testing. I instantly make the enjoyment or excitement (whichever is whichever) enough for an orgasm, as if the bar had been filled naturally to do it.

 

 

I think some people would like more clarity about what the 'E' value in the on-screen widget is, and why it doesn't change.

Fill bar => orgasm seems easy to understand, but the fixed 'E' number is not self-explanatory.

 

 

If you wanted to make it super-graphically-cool, every time the bar goes up, it could add a little differently colored section, then animate it backfilling, so you can see the size of each change you make. When initially added, the color would indicate the "source" of the change. I can live without that. Probably everyone can, just an idea.

 

Or if that sounds incomprehensible, or stupid, some other way to see visually how much bar fill you're getting from your active sex-effort, vs how much is being passively gained (or lost), or gained or lost from a special event like an orgasm or stage end.

 

 

Monoman's additions to sex in Spank that Ass, are very awesome. It's particularly good when you are getting aggressive spank sex, and can speak or "fuck back" with the STA button, and you get immediate audio feedback, and spanks, or not spanks, and possibly text feedback. The written feedback has a flicker problem though.

 

 

The hacked up voice samples he's made for sex are mostly pretty good, and some are even played appropriately. When it all fits together it's very effective. I think he wanted to use the SLSO clicks or "sex effort" to measure whether you were actively participating in your own rape orgasm. This was something I wanted to do in SLD too, but you said it was stupid. There has to be a non-stupid way to do it?

 

Monoman made his own button because he doesn't know if SLSO will be present, but you can assign it to the SLSO main or secondary action (it can't handle shift though). If SLSO main or secondary action coincides with "fuck back" or "ask for spanks" then it all makes sense to do that. I put it on a different button because that's not how it is. More ability to configure how SLSO buttons work could be nice there?

 

 

Another area things could be more fun is if "sexually broken" was determined in some more sophisticated way, and had some more interesting consequences. I'm still planning to do something to help that in SLAX, and provide a way for SLD to deliver the consequences outside of sex.

 

 

Hormones is mostly ... trouble ... but I sort of like the beg for sex feature. It's just a little basic, and needs a bit more sophistication in how it's handled, so you can push it aside at those times it's in the way of genuinely important dialog. That ties naturally into sexually broken, but as the latter is only apparent on a per sex-scene basis, it has no lasting consequence. You can look at Lewd, but that's a blunt instrument. I'm not sure Lewd by itself really has the resolution or operates with sufficient nuance to really bear that heavy load of mechanics. Again, something I thought might be possible to improve in SLAX.

 

I think people are very interested, it's just me being slow and not doing stuff to SLAX holding that back.

 

 

The mod that causes me most pain right now is EC+.

It stuffs up skeleton nodes sometimes, setting them to zero, or causing other havok. No idea why. Sometimes forcing them to 1.0 repeatedly fixes it.

 

It also has a lame interaction with MME. Chaurus pregnancy should constantly add lactacid while pregnant if you have MME (so you're basically locked at max lactacid), but should not cause boob growth of its own. If that were the case, EC+ wouldn't need to mess with nodes, and there would be less conflict, and the much better boob morphing of MME would apply instead of EC+ doing it's crude node scaling. EC+ post pregnancy would then happen naturally, at least for boobs, as the lactacid stops being added, and is used up.

 

I'm getting so annoyed with EC+ that I might crack and patch it myself.

[Ed86]

1 hour ago, Lupine00 said:

I'm not sure what you mean here. That you changed SLSO to work how I described above in 1.60 ?

 

If so, great ... though that means I need to make some changes to support it correctly again.

no, i mean that sl 1.60 has mechanic for sep orgasms, but it takes a lot of time to reach it and its ruined by always orgasming at end

 

you can test it by using only sl passive and stage change gains and everything else disabled

 

1 hour ago, Lupine00 said:

As it happens, I care about these things:

1) is the aggressive flag set? Which should indicate a rape.

2) is it a solo session? Can't be a rape, but must be masturbation.

3) does an orgasm occur? I want to know if it's a rape or non-rape orgasm, or a masturbation.

4) should orgasm be blocked by a belt or other chastity device? DD makes this rather complex to determine.

that doesnt sound like very hard

 

1 hour ago, Lupine00 said:

If you wanted to make it super-graphically-cool, every time the bar goes up, it could add a little differently colored section, then animate it backfilling, so you can see the size of each change you make. When initially added, the color would indicate the "source" of the change. I can live without that. Probably everyone can, just an idea.

not sure that is possible without rewriting widget, and gl finding someone who can do that

 

1 hour ago, Lupine00 said:

The mod that causes me most pain right now is EC+.

It stuffs up skeleton nodes sometimes, setting them to zero, or causing other havok. No idea why. Sometimes forcing them to 1.0 repeatedly fixes it.

that is because its compatibility on top of compatibility + needs other mods... a total mess

ive tried cleaning it a bit but lost interest

[Ed86]

2 hours ago, Lupine00 said:

I guess a "debug" option for testing, where you can cause a "legitimate" instant orgasm would be useful. I modified my "dev" copy of SLSO to do that, as I needed it for testing. I instantly make the enjoyment or excitement (whichever is whichever) enough for an orgasm, as if the bar had been filled naturally to do it.

there is hotkey, tho its disabled in code

[7osisg4d]

Thanks for the help!

15 hours ago, Lupine00 said:

That's entirely Aroused Creatures bad behavior. Something like that going on is going to create chaos with SLSO.

Right, script lag.  Doesn't happen without SLSO on, I guess it was the last straw.

Quote

Is the final orgasm a result of you ticking the Always Orgasms box by any chance?

Nope. Definitely script lag. 

 

The failure to block only happens in non-consensual scenes, blocking due to the lack of a vaginal tag (eg a b.j.) works correctly.

 

Quote

As you don't describe your configuration in any detail, just the mods you have, it's impossible to say if the behavior is right or wrong.

What else can I share to help diagnose the issue? My entire modlist?

 

Quote

 

SLSO will (probably) not be causing your script lag. Likely it's caused by some idiotic mod like HDT HH that just loads your game like crazy, or something that loads Papyrus specifically when a sex scene runs. Apropos possibly?

Why yes, I do have both of those mods.

Quote

I made a patch for HDT HH that fixes the overloading.

Patch installed! It's a lot better. Thank you!

SLSO orgasms proc when the bar gets full (though orgasm count didn't reset between encounters and arousal is really stuck for the male).

 

 

Papyrus.0.log

Will the lag have f'd up my game to the point that I need to go to an earlier save?  

[OsmelMC]

7 hours ago, Ed86 said:

SexLab MCM "Disable Victims Control" is useless, i dont see any code disabling hotkeys

code in GoToStage prevents timed and hotkey advance, which is what it should do

i've probably decided to patch one place rather than few

Ok in fact right now in SLSO that option are completely useless because the option is use on just one condition were the objective is enable the controls because previously in the original all the controls was Disabled. On SLSO the Disable All controls part is not more, but that's another issue somehow you manage.

[jpee1965]

On 2/25/2020 at 7:11 PM, Lupine00 said:

 

I made a patch for HDT HH that fixes the overloading.

 

 

Hi Lupine00, would you please post a link for your patch for HDT HH? I use that mod and would like to get things fixed up.

 

THANKS!

[Lupine00]

10 hours ago, jpee1965 said:

Hi Lupine00, would you please post a link for your patch for HDT HH? I use that mod and would like to get things fixed up.

It's in my blog: https://www.loverslab.com/blogs/entry/10723-hdt-hh-performance-patch/

 

[Lupine00]

20 hours ago, 7osisg4d said:

My entire modlist?

Pertinent mods that impact on the same area might be worth knowing about. Your weather or texture configurations, not so much.

 

Most important to get useful help is to specify your mod manager, because that is usually the tool you will use to fix, or at least diagnose the problem.

How you got your sort in the first place (LOOT?) and how you modified it afterwards.

 

Also, information relating to what you see when you load up your entire LO into Tes5Edit where overwrites of SLSO, SLAX or SexLab occur, and of course how you performed your file overwrites (back to mod manager again).

 

What happened when you disabled specific mods. What happened when you tried running with a barebones and just the problem mods, etc.

[Lupine00]

23 hours ago, Ed86 said:

that doesnt sound like very hard

It's always easy when somebody else does it. I'm sure you've noticed that the other way around.

[Ed86]

5 hours ago, Lupine00 said:

It's always easy when somebody else does it. I'm sure you've noticed that the other way around.

xD

[7osisg4d]

12 hours ago, Lupine00 said:

Pertinent mods that impact on the same area might be worth knowing about. Your weather or texture configurations, not so much.

 

Most important to get useful help is to specify your mod manager, because that is usually the tool you will use to fix, or at least diagnose the problem.

How you got your sort in the first place (LOOT?) and how you modified it afterwards.

 

Thanks!

 

Attached my mods, the order is crazy because I followed MO2's conflict avoidance.  Read bottom to top.  I excluded any that I figured were irrelevant to try and make it easier.

 

I'm overriding SLSO with SLAX.

 

Using MO2 with default loot sort and a smashed patch.

 

Quote

Also, information relating to what you see when you load up your entire LO into Tes5Edit where overwrites of SLSO, SLAX or SexLab occur, and of course how you performed your file overwrites (back to mod manager again).

 

TE5 overwrites:

SL: Draugr voice changed from dog to draugr, improved strapon.

Nothing on SLAX or SLSO.

 

Quote

 

What happened when you disabled specific mods. What happened when you tried running with a barebones and just the problem mods, etc.

 

Before enabling SLSO I didn't have issues.  Now with your HH fix I no longer get the poor Aroused Creatures behavior!

 

It has also mostly fixed the orgasm issue for the PC.  I was able to get the multiples at once when I created lag by changing animation just prior to.

 

Tried patch and disabling Apropos.

 

SLSO still sometimes fails to execute an orgasm for a male attacker even when full for extended periods of time, and after the encounter their arousal doesn't always go down.

Some of this is linked to how duration affects arousal reduction but I've had very long scenes with an orgasm at the end where the male is still at 99 while SL Aroused shows a recent orgasm.  This is intermittent.

 

 

loadorder.txt loaded modlist.txt