OsmelMC Mod Tweaks

[ShimizuModding]

anyone have a way to unlock the sliders of the expressions in sexlab? maximum value is at 100 while im want to go beyond it

[applesandmayo]

I'm getting something odd with SL 1.63 beta 8 and the latest SL Utility (2022.12.19). Any time a sexlab animation begins with two or more actors, (in this case for just narrowing down purposes, myself the PC and some random NPC), before the animation actually begins, the NPC will strip for a half second, redress fully, and the animation will then start.

 

I know that SLSF has a redress utility, for which I have turned off, but I'm still getting this error. Any ideas on where I should look in logs for what is causing it?

[r3mind]

There is an option in SLSO to make consensual animations require actors to orgasm (not only aggressors), but I always wondered why it never worked until I decided to study the sslThreadController.psc code. For some reason in function SLSO_Animating_GoToStage(int ToStage) there is a condition "if ActorAlias.IsAggressor() && ... " which basically makes the option I mentioned useless. I made 2 small changes to the script (this condition and also got rid of SLSO_shouldrun_SLSO_Animating_GoToStage condition) and managed to make all scenes in my game to keep switching animations until male actors orgasm (which is pretty handy with auto advance stages enabled). 

 

Is there a reason why this SLSO feature doesn't work by default? I think it would be nice to have it finally fixed^^ I'm asking in this thread, because I'm using SexLab Utility Plus and it overwrites SLSO scripts anyway.

Edited January 2, 2023 by Vigor

[OsmelMC]

11 hours ago, applesandmayo said:

I'm getting something odd with SL 1.63 beta 8 and the latest SL Utility (2022.12.19). Any time a sexlab animation begins with two or more actors, (in this case for just narrowing down purposes, myself the PC and some random NPC), before the animation actually begins, the NPC will strip for a half second, redress fully, and the animation will then start.

 

I know that SLSF has a redress utility, for which I have turned off, but I'm still getting this error. Any ideas on where I should look in logs for what is causing it?

The most common reason is that some Mod already force one or more equippable items to stay always equipped in which case the actor get redressed each time one equippable item is added. This case usually isn't related with SexLab but can be related to some Sex Mod adding items to the actor before the scene start.

 

Also you shouldn't be using the BETA 8

[OsmelMC]

10 hours ago, Vigor said:

There is an option in SLSO to make consensual animations require actors to orgasm (not only aggressors), but I always wondered why it never worked until I decided to study the sslThreadController.psc code. For some reason in function SLSO_Animating_GoToStage(int ToStage) there is a condition "if ActorAlias.IsAggressor() && ... " which basically makes the option I mentioned useless. I made 2 small changes to the script (this condition and also got rid of SLSO_shouldrun_SLSO_Animating_GoToStage condition) and managed to make all scenes in my game to keep switching animations until male actors orgasm (which is pretty handy with auto advance stages enabled). 

 

Is there a reason why this SLSO feature doesn't work by default? I think it would be nice to have it finally fixed^^ I'm asking in this thread, because I'm using SexLab Utility Plus and it overwrites SLSO scripts anyway.

This should be reported on the SLSO thread. I can fix it here but probably be rolled back when the next SLSO version be released, since I copy paste it's scripts into my scripts changing only those that are incompatible.

[applesandmayo]

24 minutes ago, OsmelMC said:

The most common reason is that some Mod already force one or more equippable items to stay always equipped in which case the actor get redressed each time one equippable item is added. This case usually isn't related with SexLab but can be related to some Sex Mod adding items to the actor before the scene start.

 

Also you shouldn't be using the BETA 8

I've been running Beta 8 since playing modded SkyrimSE, why shouldn't I be using it? Not going up against you on that, if there is a better version I should be using, I'd like to know, I just want to know why not Beta 8.

I presume the latest stable release of Sexlab would be preferred? I'm just not positive that all my current mods are compatible, even though most if not all are up to date. I think some of my mods state that Beta 8 is required, but those mod descriptions may just be out of date.

 

Also, I'm on SSE 1.5.97.

Edited January 2, 2023 by applesandmayo

[XxX_PrOgAmEr420_XxX]

Hey, necro animations have stopped working since i installed this (latest version). Im on LE. Im using the extra patch.

Not sure whats going on tbh.

I have tried resetting animation registry and cleaning animation cache, didnt work.

[OsmelMC]

1 hour ago, litl_snek said:

Hey, necro animations have stopped working since i installed this (latest version). Im on LE. Im using the extra patch.

Not sure whats going on tbh.

I have tried resetting animation registry and cleaning animation cache, didnt work.

 

Send me the "papyrus.0.log"

[OsmelMC]

9 hours ago, applesandmayo said:

I've been running Beta 8 since playing modded SkyrimSE, why shouldn't I be using it? Not going up against you on that, if there is a better version I should be using, I'd like to know, I just want to know why not Beta 8.

I presume the latest stable release of Sexlab would be preferred? I'm just not positive that all my current mods are compatible, even though most if not all are up to date. I think some of my mods state that Beta 8 is required, but those mod descriptions may just be out of date.

 

Also, I'm on SSE 1.5.97.

The BETA version of any Mod or program is always a incomplete version published to be tested by some users. In this case the test last longer than expected because the development was stopped. But the official version was finally release just before release the v1.64 for AE. 

 

My current version of SLU+ for SE is based on the official v1.63 and for that reason don't include files that are required for a BETA 8 full compatibility. Also the DLL of the official version is different from the BETA 8 and include new functions required by the current version of SLU+.

 

By the way all the Mods based on previous versions of SexLab are still compatible with the current and future versions, except for those Mod like my SLU+ or the SLSO that overwrite script files of the "SexLab Framework".

The mods, tweaks, patches and fixes that overwrite files of the "SexLab Framework" work only with one specific version of SexLab and you will need another version of those mods, tweak's, patches or fixes if you change of SexLab version. If you can't find a version of those Mods, tweak's, patches and fixes for your SexLab version, usually means that the tweak, patch or fix is not longer required.

 

 

In conclusion, if you want to use the last versions of SLU+ or SLSO, you need the official "SexLab Framework v1.63 for SE" that is on the download page.

 

Edited January 3, 2023 by OsmelMC

[Blake81]

Any chance of getting the Aroused Creatures Tweak updated to the latest Aroused Creatures version (v4.10)?

[XxX_PrOgAmEr420_XxX]

10 hours ago, OsmelMC said:

 

Send me the "papyrus.0.log"

I noticed a few of these lines : SEXLAB - NOTICE: ValidateActor(Arvel the Swift) -- FALSE -- He's dead Jim.

Papyrus.0.log

[OsmelMC]

20 minutes ago, litl_snek said:

I noticed a few of these lines : SEXLAB - NOTICE: ValidateActor(Arvel the Swift) -- FALSE -- He's dead Jim.

Papyrus.0.log 698.05 kB · 1 download

If the actor is dead, is dead  

SexLab don't have a good way to deal with dead bodies so they should be processed first by mods like "SexLab Defeat" that include Necro functions able to temporary resurrected the actor until the end of the scene.

 

The Dead bodies can be animated unless be someway resurrected first. The trick is resurrect the actor without leave him too alive.

 

The current version of SexLab Utility Plus prevent the use of dead bodies that aren't being properly treated before, and that's to prevent unwanted Necro scenes. Unwanted because, not you but most of the cases don't want to see Necro scenes so the best way to archive that is letting the Necro scenes be triggered just by the Mods that are made for that and have all the intention.

[OsmelMC]

@litl_snek

For your log seems like you are using a mod with Necro functions that is able to start the scene but something kill the actor before the animation start.

 

The current version of SLU+ stop the animation if detect that some of the actors is killed while the scene is running and in that case stop the scene.

 

Let me know the Mod you are using to start the Necro scene. I will check it's scripts, to find to a way to get compatibility between that Mod and SLU+. 

Edited January 3, 2023 by OsmelMC

[applesandmayo]

19 hours ago, OsmelMC said:

The BETA version of any Mod or program is always a incomplete version published to be tested by some users. In this case the test last longer than expected because the development was stopped. But the official version was finally release just before release the v1.64 for AE. 

 

My current version of SLU+ for SE is based on the official v1.63 and for that reason don't include files that are required for a BETA 8 full compatibility. Also the DLL of the official version is different from the BETA 8 and include new functions required by the current version of SLU+.

 

By the way all the Mods based on previous versions of SexLab are still compatible with the current and future versions, except for those Mod like my SLU+ or the SLSO that overwrite script files of the "SexLab Framework".

The mods, tweaks, patches and fixes that overwrite files of the "SexLab Framework" work only with one specific version of SexLab and you will need another version of those mods, tweak's, patches or fixes if you change of SexLab version. If you can't find a version of those Mods, tweak's, patches and fixes for your SexLab version, usually means that the tweak, patch or fix is not longer required.

 

 

In conclusion, if you want to use the last versions of SLU+ or SLSO, you need the official "SexLab Framework v1.63 for SE" that is on the download page.

 

 

Alright, I have the 1.63 release installed, got it up and running, and I'm still hitting the same error. Although, oddly enough, the strip works correctly on occasion, but usually 1/10 times. Every other time, the NPC will strip for a half second, then put their clothing back on, and then the scene will proceed. In the attached papyrus log, the NPC I was with stripped correctly in the first animation test. The second time with the same npc, they did not strip correctly. Maybe there is something I'm missing? I see logs relating to PNS (Pregnancy Normal Swapper), which hasn't seemed to have caused issue in the past, and then this version of Heels Fix (https://www.nexusmods.com/skyrimspecialedition/mods/64442) , which are the only things I see near the 'Equip/Unequip' Sexlab logs. I'm still digging through to see if there is anything I can find, but if you can cast a wise eye over this, I'd greatly appreciate it.

sl strip redress issue Papyrus.0.log

[OsmelMC]

1 hour ago, applesandmayo said:

Alright, I have the 1.63 release installed, got it up and running, and I'm still hitting the same error.

The log said that you have something overwriting the "sslActorAlias" script files of the SLU+ because some functions that are definitely in my version of that file are reported missing and causing errors.

 

The errors on the scripts have unpredictable outcome so first you get rid at least of the errors related with SexLab. By the way my SLU+ don't have errors to report on the papyrus.0.log so any ERROR related with the SexLab is definitely caused by something else, usually some other Mod overwriting my files.

 

Make sure that nothing overwrite my SLU+ and try again.

 

The "Heels Fix" is reporting all the items Equipped and Unequipped, when happen. I don't think be the reason of the problem but definitely will work to know the real reason because whatever get equipped first before the actor get stripped is almost sure related with the issue.

 

You don't say or at least i don't remember which actor is the one with the redress issue. Let me know if are all the actors, few or just one and if the player have the issue.

[applesandmayo]

12 hours ago, OsmelMC said:

The log said that you have something overwriting the "sslActorAlias" script files of the SLU+ because some functions that are definitely in my version of that file are reported missing and causing errors.

 

The errors on the scripts have unpredictable outcome so first you get rid at least of the errors related with SexLab. By the way my SLU+ don't have errors to report on the papyrus.0.log so any ERROR related with the SexLab is definitely caused by something else, usually some other Mod overwriting my files.

 

Make sure that nothing overwrite my SLU+ and try again.

 

The "Heels Fix" is reporting all the items Equipped and Unequipped, when happen. I don't think be the reason of the problem but definitely will work to know the real reason because whatever get equipped first before the actor get stripped is almost sure related with the issue.

 

You don't say or at least i don't remember which actor is the one with the redress issue. Let me know if are all the actors, few or just one and if the player have the issue.

 

Ah I see - there was a Bakafactory SL patch that was overwriting your sslActorAlias in this version of the SLU+ file. I believe that same mod was overwriting my previous version of SLU+, but with the intent to stop SL Approach Redux from having actors try to approach/grope the PC mid-SL animation. At the point in my game where I had installed that patch, it didn't seem to be causing issue. I'd need to go see what that patch is actually attempting to do. I've attached it here in case you're able to see more accurately what it is doing. I've now set this version of SLU+ to overwrite this mod.

Also, the error was with other NPC's with my PC. It seemed to affect anyone in Position 1 in the animation (which I believe for heterosexual animations, is the male position?). It was hit or miss on that if there was a foreplay animation played prior to the main event animation. In either case, the Player never seemed to have an issue with stripping, just NPC's interacting with the player. I can try out to see what combinations of MF, FF, MM, etc, animations have the issue.

 

I am also using an older version of SLSO, version 1.68, so I'll try updating that as well. I do have a number of the Bakafactory mods which have requirements that state the need for SL Aroused v28b Baka Edition. Pretty sure I'm going to fuck up this save royally by updating these major mods mid game, but it's a new save, so I don't really care.

sslActorAlias.psc

Edited January 4, 2023 by applesandmayo

[OsmelMC]

27 minutes ago, applesandmayo said:

Bakafactory SL patch that was overwriting your sslActorAlias

That patch like many other's are made for the SexLab Framework without SLU+. Once you install SLU+, you can't use any of those patch because will be incompatible and will cause errors on the scripts with unpredictable consequence.

 

That patch is for compatibility with "Precision" and is already included on my SLU+ last version.

 

 

 

27 minutes ago, applesandmayo said:

Pretty sure I'm going to fuck up this save royally by updating these

Those Mods are safe to update on middle of the game. And definitely you should keep the SLSO updated to the last SE/AE version released before the SLU+, because that's the version compatible with SLU+.

 

Like i said, when you have mods overwriting files of another Mod, the combination should be very specific or you will have errors on the logs. In those cases the combination is the one suggested by the author and any other combination will have issues.

[applesandmayo]

2 hours ago, OsmelMC said:

That patch like many other's are made for the SexLab Framework without SLU+. Once you install SLU+, you can't use any of those patch because will be incompatible and will cause errors on the scripts with unpredictable consequence.

 

That patch is for compatibility with "Precision" and is already included on my SLU+ last version.

 

 

 

Those Mods are safe to update on middle of the game. And definitely you should keep the SLSO updated to the last SE/AE version released before the SLU+, because that's the version compatible with SLU+.

 

Like i said, when you have mods overwriting files of another Mod, the combination should be very specific or you will have errors on the logs. In those cases the combination is the one suggested by the author and any other combination will have issues.

 

For the sake of my testing at the moment, should I have SLU+ lower than the mods it's affecting in my load order? It's currently at the bottom of my overwrite panel in MO2. Additionally, I'd like to use the SOS -Sexlab Addon 1.1, but I've found it interferes with a number of SL Eager NPC's and Blush When Aroused's SL Aroused integration. I saw that there is a custom version of PapyrusUtil on the description page - should that be used in conjunction with the SL Addon to mitigate those issues? I play with an all-females-are-futa build, but I'd like a 50-50% mix of which ones are SL Male and SL Female just for gameplay purposes.

 

And as the obvious note, I'm not going to mess with the SOS Addon until after I can figure out the stripping issue, just to reduce any variables in the debugging equation.

[Guest]

hi a tough or difficult to check question

 

is there a version of SexLab Utility Plus that works for vr's compatible SL?

[applesandmayo]

I think I found the issue, seems to relate to Pregnancy Normal Swapper, which seemed to have this issue in 1.2.1, but was supposedly fixed in 1.2.2. In this log, Weyna does not have the active effect applied to her, and consistently strips normally. Delphine does have the active effect applied to her, and consistently strips and redresses prior to the animation beginning. Annoying, because I like this mod, but it breaks the act, and additionally the entire reason for having the mod. I know there is the player.removeEffect, or removeSpell mod, but what is the command for removing an active effect from an NPC?

 

Idk how to encapsulate the photos in the dropdown menu, sorry - but here are photos of both Weyna and Delphine during and outside of animations with the effect displayed as active in the console for Delphine, but not present at all on Weyna.

 

To expand on your question though, this error does not occur on the PC or Male NPC's, only on female NPC's, seemingly those with that effect running. Also, I started up a new game just to mitigate other issues, and was pleasantly surprised to see that SOS Sexlab Addon has been integrated, seemed to work perfectly too! It did grey out the option for SOS Integration in Arousal Based Match Maker, but that seems to be a moot point now that SL genders are automatically recognized based on the schlong type globally.

 

Edit: After commenting out the distributed spell in Pregnancy Normal Swappers SPID Distribution file, the issue still occured on Delphine, but not Weyna. Disabling/Enabling Delphine removed the effect and fixed it. Tried it on another female NPC who was having the same problem, fixed her too.

weyna strips but not delphinePapyrus.0.log enb2023_1_4_14_56_09.bmp enb2023_1_4_14_57_14.bmp enb2023_1_4_14_58_39.bmp enb2023_1_4_14_59_36.bmp

Edited January 4, 2023 by applesandmayo

[OsmelMC]

3 hours ago, LoversProton said:

hi a tough or difficult to check question

 

is there a version of SexLab Utility Plus that works for vr's compatible SL?

Not really.

Some VR users are reported be fine using SLU, but the true is that the SexLab for VR is too different from the SexLab for SE so you will end with a lot of errors is you try to use SLU+ on VR.

 

If someone makes a real conversion of the SexLab v1.65 into VR, i can make a SLU+ for VR too. But the current SexLab for VR is too different to be able of make a SLU+ version for it without a lot of personal tests.

 

And I don't have VR.

Edited January 4, 2023 by OsmelMC

[XxX_PrOgAmEr420_XxX]

On 1/3/2023 at 4:23 PM, OsmelMC said:

@litl_snek

For your log seems like you are using a mod with Necro functions that is able to start the scene but something kill the actor before the animation start.

 

The current version of SLU+ stop the animation if detect that some of the actors is killed while the scene is running and in that case stop the scene.

 

Let me know the Mod you are using to start the Necro scene. I will check it's scripts, to find to a way to get compatibility between that Mod and SLU+. 

I think I understand what you mean

I am using Defeat to start the scene, but it seems sexlab matchmaker doesnt work either

[modball]

 

I had to revert to an old version of SLU+ to recompile SL Tools POSSMainScr.psc (I am just changing the list of animation tags).

 

I suspect it might be related to PapyrusUtil 4.0 adding GetDiff() but I am not using AE, so probably cannot update it beyond 3.9. Any suggestions?

 

Spoiler

===================== Starting compiling session 1 ======================
S:\Steam\steamapps\common\Skyrim Special Edition\Data\scripts\source\sslAnimationSlots.psc(102,11): GetDiffString is not a function or does not existS:\Steam\steamapps\common\Skyrim Special Edition\Data\scripts\source\sslFurnitureMarkers.psc(279,27): GetDiffForm is not a function or does not existS:\Steam\steamapps\common\Skyrim Special Edition\Data\scripts\source\sslFurnitureMarkers.psc(279,27): cannot call the member function GetDiffForm alone or on a type, must call it on a variableS:\Steam\steamapps\common\Skyrim Special Edition\Data\scripts\source\sslFurnitureMarkers.psc(280,27): GetDiffForm is not a function or does not existS:\Steam\steamapps\common\Skyrim Special Edition\Data\scripts\source\sslFurnitureMarkers.psc(280,27): cannot call the member function GetDiffForm alone or on a type, must call it on a variableS:\Steam\steamapps\common\Skyrim Special Edition\Data\scripts\source\sslFurnitureMarkers.psc(407,36): GetMatchingString is not a function or does not existS:\Steam\steamapps\common\Skyrim Special Edition\Data\scripts\source\sslFurnitureMarkers.psc(407,36): cannot call the member function GetMatchingString alone or on a type, must call it on a variable
Starting 1 compile threads for 1 files...
Compiling "POSSMainScr"...
No output generated for POSSMainScr, compilation failed.

 

[PippinTom]

@OsmelMC Moving here from the SLF thread - issue with export/import of SL profiles regarding Expressions (but maybe not only)

 

Since you've been rather sceptical about reported issue's origin I did some code inspection on my own. I'm not an expert but what I found is that It looks like EXPORT works fine, its just IMPORT that screwes data.

 

ImportJson() method of SLU+, to be exact SetTags(JsonUtil.StringListToArray(File, "Tags")) :: sslBaseExpression @ line #855 is passing a formally invalid "streamed" array of strings to a function SetTags(string TagList) :: sslBaseObject @ line #64.

 

So setTags gets

<start>["Ahegao", "BeastOnly", "Upset", "Angry", "Mad", "Victim", "Aggressor"]</end>

(note the redundant inner quotes and square brackets that are part of the variable being passed) instead of expected, singular string, looking like

 

<start>"Ahegao,BeastOnly,Upset,Angry,Mad,Victim,Aggressor"</end>

 

Obviously setTags is not ready for it, what results in mess reported before:

 

GetTags() --> ["Ahegao", "BeastOnly", "Upset", "Angry", "Mad", "Victim", "Aggressor", ""Aggressor"]", ""Victim"", ""Mad"", ""Angry"", ""Upset"", ""BeastOnly"", "["Ahegao""]

 

instead of
GetTags() --> ["Ahegao", "BeastOnly", "Upset", "Angry", "Mad", "Victim", "Aggressor"]

 

being embeded in savegame. ...Until another SL clean system reset (which probably cleans thing up, until another (re)IMPORT of user's settings of course).

Another issue that revealed itself in the process is that SLU's IMPORT does not clear existing list(s) of tags before importing new ones, what is also something rather unexpected.

Bottom line: I don't know what is the impact of that code on game features and stability - probably small or even none - it just does not feel right to me to feed function with incompatible garbage data even if that will not cause immediate CTD, so I've reported it?

PS:
    Both files mentioned above (until tonight) were pristine copies from SLF and SLU releases at the time of making report.
PPS:
    In case that issue manifest itself only on my machine (as you implied) because of "some other mod" - I've helped myself and managed to clean my save by adding primitive and slow (I'm not a programmer) yet effective code to importJson method ?
    In case everyone else is victim of it (maybe unaware yet still a victim) - it's up to your discretion what you do with that knowledge ?

 

 

Edited January 5, 2023 by PippinTom
line number corrected

[OsmelMC]

16 hours ago, litl_snek said:

I think I understand what you mean

I am using Defeat to start the scene, but it seems sexlab matchmaker doesnt work either

MatchMaker isn't for Necro scenes. Like i said the Necro scenes required special treatment provide only by few Mods with Necro support.