OsmelMC Mod Tweaks

[VahzahVulom]

nevermind

Edited October 4, 2023 by VahzahVulom

[Trickle]

On 10/2/2023 at 5:28 PM, OsmelMC said:

OM "Outfit Manager" 

MCM "Mod Configuration Menu"

 

Not sure if you noticed but the conversation you Quote there, was about the "Outfit Manager" that is one of my Mods on Nexus and Nexus have terrible discussion thread (Forum / Post)

 

I see it now, but I still don't have a clue why the new version messes up AH Hotkey mod. I notice there is a PapyrusUtil dll included in the update that isn't there in the 0603 or 0709Beta. Could that be the difference? I am still on SE.

Edited October 4, 2023 by Trickle

[OsmelMC]

6 hours ago, Trickle said:

 

I see it now, but I still don't have a clue why the new version messes up AH Hotkey mod. I notice there is a PapyrusUtil dll included in the update that isn't there in the 0603 or 0709Beta. Could that be the difference? I am still on SE.

You are still blending things...

 

I suppose you are now talking about the "SexLab Utility Plus" in which case first make sure that nothing is overwriting it files. Even if is some patch for SLU+ old patches usually are incompatible with new versions of the patched Mods.

 

The PapyrusUtil on the SLU+ setup is just for the Skyrim SE version and if different from any other PapyrusUtil. So make sure that nothing be overwriting it, not even the standalone version.

 

Finally the Hotkeys have none issue so you better check on the SexLab MCM if they have key assigned.

 

 

What is "AH Hotkey Mod" ?

[biobay850]

On 10/3/2023 at 8:09 AM, OsmelMC said:

 

1. The FNIS option I was talking about, was the "Skeleton Arm Fix". But was just an example since even when do something like that, is just for the arms. And I didn't remember the name.

 

2. The "High Heels Fix" are Mods that are made specific to fix HH issues when the actor use a bed or chair or include the fix between it's options. If you use High Heels you probably have already at least one Mod for that (maybe more than one)

 

Check if you have some Mod with one of this words on the plugin or folder name (Height, Heels, Furniture or Knees) 

 

 

3. The previous versions of SLU+ probably did something that was bad for some things but help in cases like yours. For example and probably be the reason of the difference: the previous versions use to enabled the FootIK system as consequences of the Default Idle used to reset the animation. The FootIK of Skyrim force the Foot's to keep the contact with the floor. Most of the animation authors like Billy usually disable the FootIK on the first animation stage to prevent issues with Alignment and Physics. But that's not enough so I made sure of also disable the FootIK before some alignment events and probably for that reason the previous versions behave different with your issue but still the problem isn't SLU+.

 

 

4. The Picture on the Nexus link you posted isn't related with SexLab and probably have the same issue than you. More like be also the HH fix used there.

 

 

 

 

 

2. I have High Heels Fix but no any difference.

 

3. So the problem is FootIK? I have tried FootIK off spell or FootIK OFF for SexLabUtil1 before but still not solved. Maybe force enable the footik should solve it?

[Trickle]

1 hour ago, OsmelMC said:

You are still blending things...

 

I suppose you are now talking about the "SexLab Utility Plus" in which case first make sure that nothing is overwriting it files. Even if is some patch for SLU+ old patches usually are incompatible with new versions of the patched Mods.

 

The PapyrusUtil on the SLU+ setup is just for the Skyrim SE version and if different from any other PapyrusUtil. So make sure that nothing be overwriting it, not even the standalone version.

 

Finally the Hotkeys have none issue so you better check on the SexLab MCM if they have key assigned.

 

 

What is "AH Hotkey Mod" ?

AH Hotkeys AH Hotkeys - Skyrim Hotkey Manager SSE at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com) 

 

Yes I am talking of Sexlab Util Plus. I should have been more precise when I jumped in! Thank you for your time.

 

I use MO2 and nothing is over-writing Sexlab Utility Plus 1003. Your mod over-writes everything it should including Sexlab 1.63, papyrus Util SE 3.9, and SLSO. There are no conflicts showing with AH Hotkeys either but for some reason it clashes with the latest version. SLUP 0603 works fine though. 

[OsmelMC]

55 minutes ago, Trickle said:

There are no conflicts showing with AH Hotkeys either but for some reason it clashes with the latest version. SLUP 0603 works fine though. 

You will have to be more specific and maybe send me the file "papyrus.0.log".

 

I just guessing but probably your AH Hotkey isn't loading. This is not a SLU+ issue but can be caused by the update. This Skyrim bug can happen with any Mod at any time after update or install a new mod with Quest or MCM.

Anyway the solution on that case can be change the position of the plugin on the plugin's load list or flag the plugin as Master to force it's priority on the load game event.

 

The plugin's with MCM or Quests shouldn't be flagged as ESL because some user's get problems like this.

[no_way]

Do we still need SL Grass Patch with the latest update to SLU+ or its integrated?

 

[OsmelMC]

17 minutes ago, no_way said:

Do we still need SL Grass Patch with the latest update to SLU+ or its integrated?

 

Not even compatible anymore. Not needed.

[sexcapades]

On 10/4/2023 at 4:30 PM, OsmelMC said:

You will have to be more specific and maybe send me the file "papyrus.0.log".

 

I just guessing but probably your AH Hotkey isn't loading. This is not a SLU+ issue but can be caused by the update. This Skyrim bug can happen with any Mod at any time after update or install a new mod with Quest or MCM.

Anyway the solution on that case can be change the position of the plugin on the plugin's load list or flag the plugin as Master to force it's priority on the load game event.

 

The plugin's with MCM or Quests shouldn't be flagged as ESL because some user's get problems like this.

When the problem occurred on my game - I noticed that suddenly AH1 was asking me if I wanted to disable the default hotkeys for the game (0-9 I think - don't know as I've never used the game default keys)  Clicking disable the game's default keys didn't help as the option remained available and AH1 was useless.  I reverted to the old version of SLUP and all is fine... can't use the update though.

[creepycream]

I still can't let go of controlling NPC scenes. I press the N key on an animating NPC scene to swap positions (player is locked). After that I press N key again to release control of the scene (player is unlocked). As soon as the stage auto advances or if I manually advance the stage with SLTools jumping around still advances the scene, Shift key modifier also works in this state. I was able to control multiple NPC scenes by replicating what I did.

[OsmelMC]

38 minutes ago, creepycream said:

I still can't let go of controlling NPC scenes. I press the N key on an animating NPC scene to swap positions (player is locked). After that I press N key again to release control of the scene (player is unlocked). As soon as the stage auto advances or if I manually advance the stage with SLTools jumping around still advances the scene, Shift key modifier also works in this state. I was able to control multiple NPC scenes by replicating what I did.

Let me see if I understand...

You still can control the scene when you are not longer controlling the scene?

[biobay850]

I tested again about the bent feet problem. If disable the footik before start scene will cause it all the way, no matter what version.

[OsmelMC]

6 hours ago, biobay850 said:

I tested again about the bent feet problem. If disable the footik before start scene will cause it all the way, no matter what version.

I tell you that and also tell you that you have to check your Mods to get rid of those that fix the high heels issues.

 

Actually better send me your Mod list to show you what to do.

[creepycream]

21 hours ago, OsmelMC said:

You still can control the scene when you are not longer controlling the scene?

Correct. Only when advancing or reversing stages. Controls for adjusting position are let go.

[dePog]

Any ideas why one female partner will always make your male player zoom to 200% on SLSO's widget and cum almost immediately.

With all the other females the player's excitement slowly builds and is controllable with the left/right mouse button inputs.

If I start a new game it will be unlikely that the same female will cause the issue, but there will be some other female that causes that same 200%, cum immediately, behaviour.

 

Any ideas why that happens? And how to stop it?
Or is it a feature that some females pop your cork, lol?

 

My build includes:
Sexlab 1.63
SLSO 1.7.4
Sexlab Utility Plus 20230218 (Its not just this build. It happened in previous builds too. Also, I don't think the issue is in SL Utility+)
Sexlab Aroused (Fishburger)

[OsmelMC]

8 hours ago, dePog said:

Any ideas why one female partner will always make your male player zoom to 200% on SLSO's widget and cum almost immediately.

With all the other females the player's excitement slowly builds and is controllable with the left/right mouse button inputs.

If I start a new game it will be unlikely that the same female will cause the issue, but there will be some other female that causes that same 200%, cum immediately, behaviour.

 

Any ideas why that happens? And how to stop it?
Or is it a feature that some females pop your cork, lol?

 

My build includes:
Sexlab 1.63
SLSO 1.7.4
Sexlab Utility Plus 20230218 (Its not just this build. It happened in previous builds too. Also, I don't think the issue is in SL Utility+)
Sexlab Aroused (Fishburger)

 

Even on SLSO the Enjoyment of the actors is calculate from parameters like relationship between the actors and the sex expertise of the actors.

 

Depending of the option selected on the SLSO MCM the Enjoyment function can also include the Arousal of the actors which usually explain why the player start with a high enjoyment.

 

By the way the Enjoyment Bar of the SLSO Widgets is animated and usually start showing the values of the previous scene where was used. The change you see at the start of the scene is the widget cleaning the previous value with a 0 and then setting the value of the current actor enjoyment.

 

[dePog]

7 hours ago, OsmelMC said:

 

Even on SLSO the Enjoyment of the actors is calculate from parameters like relationship between the actors and the sex expertise of the actors.

 

Depending of the option selected on the SLSO MCM the Enjoyment function can also include the Arousal of the actors which usually explain why the player start with a high enjoyment.

 

By the way the Enjoyment Bar of the SLSO Widgets is animated and usually start showing the values of the previous scene where was used. The change you see at the start of the scene is the widget cleaning the previous value with a 0 and then setting the value of the current actor enjoyment.

 

 

Thanks Osmel.

I have a reasonable working knowledge of Arousal and SLSO as I have worked with their functions in my SOA mod (Separate Orgasm Adventures), but as you have worked on them to a higher level than me I thought you may have had some idea why it only happens with one NPC for the entire game, every single time they have sex.

Even if both the female NPC and my male player have an Arousal of zero, he will orgasm within 10 to 15 seconds. All other NPCs work normally.

 

My only guess is that a script gets glitched, because if I start a new game that particular NPC works correctly. However, some other NPC will start showing that issue.

 

Anyway, thanks for the response.

 

Cheers,

dePog

[OsmelMC]

28 minutes ago, dePog said:

My only guess is that a script gets glitched, because if I start a new game that particular NPC works correctly. However, some other NPC will start showing that issue.

Like I said the sex expertise of the actors (the Diary or Jornal page of the SexLab MCM) and they relationship are some of the most relevant parameters of the Enjoyment functions even on SLSO.

 

In theory one actor with a lot of sex skills can make cum faster a less skilled actor. That's the theory because the enjoyment function is native and only Ashal know the details.

Edited October 10, 2023 by OsmelMC

[PippinTom]

On 9/27/2023 at 11:35 PM, PippinTom said:

So simple fix would be to (. . .) re(gex)place all second argument (at least in part referring to key name) in JsonUtil calls, with lowercase conversion.

 

On 9/28/2023 at 12:46 AM, OsmelMC said:

Just in case i will apply your solution to all the Json and storage parameters. (. . .) But if make it lowercase fix it, lowercase will be.

 

I started another game and turns out that even with what I thought was a valid solution, the issue persists. So it's not a solution at all, it was just a coincidence as it turns out, with maybe some impact to outcome but not an significant enough on its own.

 

Bottom line this time seems to be that to actually fix empty outfit names on the list and missing scenarios in PC's profile, one has to just kick and poke OM hard enough with available MCM options to finally put it on the right track, when it stabilizes and works properly from then on. Combination of "import config" + "restart OM"(quest) + re"import (PC) adv profile" in mixed order and repeated once or twice+ actually does the trick.

 

Real source of problem remains mystery to me, I just hope you, on the other hand, already know or will find out what it ma be. Good that it's not a showstopper and for now can be circumvented.

 

Edited October 11, 2023 by PippinTom
typos

[OsmelMC]

4 hours ago, PippinTom said:

 

 

I started another game and turns out that even with what I thought was a valid solution, the issue persists. So it's not a solution at all, it was just a coincidence as it turns out, with maybe some impact to outcome but not an significant enough on its own.

 

Bottom line this time seems to be that to actually fix empty outfit names on the list and missing scenarios in PC's profile, one has to just kick and poke OM hard enough with available MCM options to finally put it on the right track, when it stabilizes and works properly from then on. Combination of "import config" + "restart OM"(quest) + re"import (PC) adv profile" in mixed order and repeated once or twice+ actually does the trick.

 

Real source of problem remains mystery to me, I just hope you, on the other hand, already know or will find out what it ma be. Good that it's not a showstopper and for now can be circumvented.

 

Try this version...

Outfit Manager 20231006.zip

[PippinTom]

48 minutes ago, OsmelMC said:

Try this version...

 

Thanks, will do ASAP, diff looks promising

[PippinTom]

On 10/11/2023 at 10:45 PM, OsmelMC said:

Try this version...

 

what I did (bulletted lines means ISSUE):

-- started new game, (didn't wait for SLF to trigger its install if that matters, didn't change PC's name so this time it was vanilla "prisoner")

-- opened MCM and "imported OM config"

-- checked outfits list but basically nothing mine there, so closed MCM

-- reopened MCM, and oufit list were this time filled with all "mine old" outfits, but:

• "tooltip" (section below main window) didn't show actual content of those mine outfits, while for those preinstalled with OM had tooltip filled properly(*)

-- went to advanced behavior to check PC's scenarios, and:

• nothing was imported - zeroes everywhere

-- so I've hit "import" (without entering any name, because name is not actually stored in 0..14.jsone profile anyway:

• got ERROR in place of IMPORT "button

-- closed and reopened MCM, hit RESTART OM

-- closed MCM and waited for confirmation that it restarted

-- reopened MCM at Advanced Section, and hit IMPORT with the same outcome (second) time, BUT then, afrer hitting that ERROR "button" third or fourth time (counting previous attempts) finally it changed to "WORKING" (or something like that, and Scenarios were not empty anymore, BUT

• there were wrong outfits (mostly not "mine", one or two of them were for/from "vilja" - skunk I've never even met not mention installing) assigned to not the same set of scenarios
• keyboard shortcuts weren't working

-- ALT-TABBED to OS and DIFFed currect 0..14.json with my backup - mainly it was screved up (from my perspective) so I've merged two sections that were important for me in that case "activeoutfit" (AKA scenarios) and "trackedinventoryitems" (things that I no longer wish to craft again and again when starting new game)

-- reopened MCM and and hit IMPORT profile once again - this time I've got proper scenarios with proper outfis, and hotkeys working again

 

Repeated that whole test second time, with my 0..14.json profile partially modified with same/similar enough outcome - some "restart and/or kick and/or poke" still required to make PC's profile working.

 

And that concludes my tests.

 

-----------------------------------

 

After all I've went to check/diff whole config directory, including deeper thinking about changes made in 0..14 one by upgrade, and decided that I prefer to stick with previous version of OM because it was maybe buggy initially, but I've managed to get it working the way I needed. I have no idea if other issue were addressed in that test version,  so my tests ended just on game start, and without knowing what exactly should be tested because has been changed(**) so for the time being I choose to just play and get my PC fucked by some happy entity.

 

However, If you wish me to test something specific, then I'll do it next time, gladly.

 

BTW: thanks for the fucking amazing mod - finally I've got means to utilize all those outfits that usually didn't fit in ridiculously small pool offered by SKY_UI there, with small tweak to both Sky and OM adding CTRL/ALT/SHIFT modifier recognition/support possibilities for hotkeyed presets I have more possibilities than need!

Maybe you should think about incorporating it in OM?

 

_______

*) what in the end is not the big issue for me because I've that part rewritten in my branch(ed) version of OM and was planning to merge it after initial tests, in case they were successful

**) I could try to understand all changes in the code, but that would be kinda painful way and I prefer to avoid it if I can simply ask first

 

[OsmelMC]

2 hours ago, PippinTom said:

"tooltip" (section below main window) didn't show actual content of those mine outfits, while for those preinstalled with OM had tooltip filled properly(*)

The Info displayed for the outfit on the bottom of the window depends of the page. For example the "Supported Outfits" page shows the "Custom Description" of the outfit while the "Advanced Behaviors" page show the items and they amount on the inventory.

 

I think the rest of the errors and issues are related with a fixed bug on the HEX conversion functions. So most of the old JSON files have the wrong names and need to be re exported from your saved game once the OM be updated. 

 

In general if you want to start a new game after update the OM I recommend to open the previous saved game and let it get updated before Export the Configuration, all the Outfits and all the Advanced Behaviors. That's because the update process some times change the structure of the stored values and the Exported JSON files have to be re-exported to make them 100% compatible again.

[PippinTom]

On 10/13/2023 at 4:48 AM, OsmelMC said:

In general if you want to start a new game after update the OM I recommend to open the previous saved game and let it get updated before Export the Configuration, all the Outfits and all the Advanced Behaviors.

 

Well, that makes sense I guess, shame that I didn't know it (nor think about it myself) before test - anyway, will test it again then, yet not tonight.

[OsmelMC]

40 minutes ago, PippinTom said:

 

Well, that makes sense I guess, shame that I didn't know it (nor think about it myself) before test - anyway, will test it again then, yet not tonight.

In first place I assume you be testing in your current gameplay in which case the update is automatic. Then I didn't remember that fix in particular. Happens that I can't remember what fixes I did on each version so before release it I just compare the files of both version's and take notes of the difference for the Nexus Update Log

 

 

At least now I know that I will have to make some warnings on the setup of the next version.