OsmelMC Mod Tweaks

[Spyro84]

SLSO just got updated again recently just so you know @OsmelMC

[PippinTom]

13 hours ago, OsmelMC said:

Nobody seems to know the reason of that CTD. Seems to be related with the PapyrusUtil but apparently only happens with one function of the PapyrusUtil that is called at the end of the Clean System or Setup process. Only happens on few computers

 

Actually I recall more than few reports of same issue, what means than unreported numbers are probably greater. I refer to a CTD happening at moment when line containing following phrase appears in the log

 

SEXLAB - CleanActorStorage

 

Anyway - it never happened to me, until few weeks back, when I got lazy and didn't follow my usual routine when using clean system. So I got pissed, and figured out a workaround, that works for me, but maybe will work for others. 

 

@achilles255057

  So:

-- enable debug in SL (so it will feed console with data that you need to monitor progression)

-- after starting clean system close MCM

-- from time to time open console to check at which phase cleanup routine is at the moment

-- if you see that SL starts (re)registering animations, do not close the console and wait until last animation is registered and nothing else going on - it may take a long time if you have plenty of animations

-- close the console for a moment and reopen it to check if SL resumed and if so - close it and wait for final popup confirming SL reset to be succesfull (I can't recall now if that's right phase for that popup but one way or another SL should inform user that it finished whatever there was to be done)

 

and that's it.

 

@OsmelMC

I'm layman but to me CTD seems to happen due to lost synchronization of threads and/or timeout implemented in one of them that abandon waiting for other to finish if it takes "too long" in opinion of code writer.

 

DISCLAIMER: I can't be sure if I remember exactly workaround described above, but I'm sure that there is connection between avoiding CTD and using console to interrupt clean system which while opened helps by halting one of SL threads until another one (one unaffected by console, probably one from another mod, like SL anim loader) properly finishes.

 

 

[OsmelMC]

42 minutes ago, PippinTom said:

 

Actually I recall more than few reports of same issue, what means than unreported numbers are probably greater. I refer to a CTD happening at moment when line containing following phrase appears in the log

 

SEXLAB - CleanActorStorage

 

Anyway - it never happened to me, until few weeks back, when I got lazy and didn't follow my usual routine when using clean system. So I got pissed, and figured out a workaround, that works for me, but maybe will work for others. 

 

@achilles255057

  So:

-- enable debug in SL (so it will feed console with data that you need to monitor progression)

-- after starting clean system close MCM

-- from time to time open console to check at which phase cleanup routine is at the moment

-- if you see that SL starts (re)registering animations, do not close the console and wait until last animation is registered and nothing else going on - it may take a long time if you have plenty of animations

-- close the console for a moment and reopen it to check if SL resumed and if so - close it and wait for final popup confirming SL reset to be succesfull (I can't recall now if that's right phase for that popup but one way or another SL should inform user that it finished whatever there was to be done)

 

and that's it.

 

@OsmelMC

I'm layman but to me CTD seems to happen due to lost synchronization of threads and/or timeout implemented in one of them that abandon waiting for other to finish if it takes "too long" in opinion of code writer.

 

DISCLAIMER: I can't be sure if I remember exactly workaround described above, but I'm sure that there is connection between avoiding CTD and using console to interrupt clean system which while opened helps by halting one of SL threads until another one (one unaffected by console, probably one from another mod, like SL anim loader) properly finishes.

 

 

Very interesting...

I usually keep the console open while the update or clean system is running and never leave the room until all the animations are installed.

 

Keep the console open don't interrupt the Clean System but actually stop a lot of Mod process that use the OnUpdate event, so in theory will prevent the actor scanner of some heavy mods to start. Also I don't know what does the PapyrusUtil function that is reported as cause of the CTD but the name of the function included "DEBUG" so probably is related with the console.

 

By the way the "Clean Actor Storage" is what everyone can see but is not the reason, the function with the issue is executed just after the Clean Actor Storage was finished.

[achilles255057]

5 hours ago, PippinTom said:

 

Actually I recall more than few reports of same issue, what means than unreported numbers are probably greater. I refer to a CTD happening at moment when line containing following phrase appears in the log

 

SEXLAB - CleanActorStorage

 

Anyway - it never happened to me, until few weeks back, when I got lazy and didn't follow my usual routine when using clean system. So I got pissed, and figured out a workaround, that works for me, but maybe will work for others. 

 

@achilles255057

  So:

-- enable debug in SL (so it will feed console with data that you need to monitor progression)

-- after starting clean system close MCM

-- from time to time open console to check at which phase cleanup routine is at the moment

-- if you see that SL starts (re)registering animations, do not close the console and wait until last animation is registered and nothing else going on - it may take a long time if you have plenty of animations

-- close the console for a moment and reopen it to check if SL resumed and if so - close it and wait for final popup confirming SL reset to be succesfull (I can't recall now if that's right phase for that popup but one way or another SL should inform user that it finished whatever there was to be done)

 

and that's it.

 

@OsmelMC

I'm layman but to me CTD seems to happen due to lost synchronization of threads and/or timeout implemented in one of them that abandon waiting for other to finish if it takes "too long" in opinion of code writer.

 

DISCLAIMER: I can't be sure if I remember exactly workaround described above, but I'm sure that there is connection between avoiding CTD and using console to interrupt clean system which while opened helps by halting one of SL threads until another one (one unaffected by console, probably one from another mod, like SL anim loader) properly finishes.

 

 

First thanks for helping me, both you and @OsmelMC

And @PippinTom I follow your step and still got CTD, at least this time I have some clearly message in Papyrus.0.log.

Here are logs.

Papyrus.0.logCrash_2022_5_17_23-7-17.txt

Edited May 17, 2022 by achilles255057

[achilles255057]

Well I just stated a new game, and still got CTD when installing sexlab :((
Papyrus.1.log

Crash_2020_6_20_15-15-52.txt

[OsmelMC]

7 hours ago, achilles255057 said:

Well I just stated a new game, and still got CTD when installing sexlab :((
Papyrus.1.log

Crash_2020_6_20_15-15-52.txt 24.74 kB · 6 downloads

Try install the SexLab with the SLU+ but without the rest of the Sex Mods

[crococat]

Tested SLU+ with FurnitureSex mod. After 1 day playing and many sex scenes had no problems. Seems all is compatible.

 

On 5/17/2022 at 1:09 AM, OsmelMC said:

You should use the SE version of SLSO and make sure that SLU+ be overwriting the SLSO files

I had problems in LE. On SLSO SE page is said that it is not compatible with LE. Just wouldnot use SLSO.

In SE i have no problems.

[OsmelMC]

3 hours ago, crococat said:

I had problems in LE. On SLSO SE page is said that it is not compatible with LE. Just wouldnot use SLSO.

In SE i have no problems.

SLSO for SE by itself is incompatible with LE because like I said each version is made in compatibility with just one SexLab.

 

But once you use my SLU+ you are not longer using the your original SexLab Framework. My SLU+ convert your SexLab Framework into a new and very different versions that is more like the SE and for that reason my scripts include patches or to be more specific, is mixed with the SLSO scripts and few others.

The same way SexLab Framework is not longer your original version, SLSO is also a very different version once my SLU+ is installed and should behave on LE same as on SE if my setup recommendations are being followed.

 

 

[Nymra]

Hmm, 

 

Problem 1:

i cannot get this to work:

 

Sexlab.AddCum(cfgqst.PlayerRef, true, true, true)

 

log says (see attached)

 

[05/19/2022 - 07:23:39AM] Error: Cannot call AddCum() on a None object, aborting function call
stack:

 

cfgqst.PlayerRef is used in thousands of other lines of code without issues o_O 

 

Problem 2:

And OnOrgasmEnd Event is VERY unreliable. It sometiems fires at the START of the final stage and sometimes at the end...

there are three Solo Male scenes in the log and the OrgasmEnd was sent at the start of the final stage. 
And Since AnimationEnd and AnimationEnding always fire too late, I currently have no way of reliably catch the actual real end of  Sexlab Scene, hmm. 

Papyrus.0.log

[crococat]

21 hours ago, OsmelMC said:

SLSO for SE by itself is incompatible with LE because like I said each version is made in compatibility with just one SexLab.

 

But once you use my SLU+ you are not longer using the your original SexLab Framework. My SLU+ convert your SexLab Framework into a new and very different versions that is more like the SE and for that reason my scripts include patches or to be more specific, is mixed with the SLSO scripts and few others.

The same way SexLab Framework is not longer your original version, SLSO is also a very different version once my SLU+ is installed and should behave on LE same as on SE if my setup recommendations are being followed.

 

 

Tried install SLSO for SE on my LE game. Now all is working ok. Thanks for advice.

But Cum and Inflation was not work before i check "bodymorph" option in FillHerUp mod, which was told not to check in LE.

If anyone would follow FHUp MCM instructions, he will not have this effects. From mod description it is not quite understandable that with SLU+ mod Sexlab had be treated as SE mod even in LE game.

[Nymra]

I also seem to be unable to equip the tongues...

 

- I did not yet try to revert on older version of SLU+ but with the current the tongues do not show up, get not equiped at the start of sex in inventory and I cannot select tongues for my Custom 1-5 animation sets.

Edited May 19, 2022 by Nymra

[Talesien]

Small problem ... ok medium sized.
While your Outfit Manager works fine with my current  load order and save I can't get it to work on the new setup I'm working on. Right after starting a new game the MCM shows the title image, but no menu entries. If opened again even the title image is missing. Tried to move it up or down in the load order to no avail. Tried removing The Luxury Suite (on the off chance that the outfit manager option of it collides with your outfit manager somehow ... but no dice). Can't find anything in the log either, but perhaps that's just because I've no real idea what to look for, so I attached it.

Papyrus.0-outfit_manager_bug.log

[OsmelMC]

On 5/19/2022 at 1:33 AM, Nymra said:

Hmm, 

 

Problem 1:

i cannot get this to work:

 

Sexlab.AddCum(cfgqst.PlayerRef, true, true, true)

 

log says (see attached)

 

[05/19/2022 - 07:23:39AM] Error: Cannot call AddCum() on a None object, aborting function call
stack:

 

cfgqst.PlayerRef is used in thousands of other lines of code without issues o_O 

 

Problem 2:

And OnOrgasmEnd Event is VERY unreliable. It sometiems fires at the START of the final stage and sometimes at the end...

there are three Solo Male scenes in the log and the OrgasmEnd was sent at the start of the final stage. 
And Since AnimationEnd and AnimationEnding always fire too late, I currently have no way of reliably catch the actual real end of  Sexlab Scene, hmm. 

Papyrus.0.log 396.49 kB · 2 downloads

 

 

Instead of "CfgQst.PlayerRef" better use the "Game.GetPlayerRef()"

 

The OrgasmEnd event is very reliable and always happen at the end of the standard animation event if the actor don't have orgasms. But also can be used to force the orgasm on all the actors so probably some Mod is using it for that and interfering with the rest of the mods that relays on the event.

[OsmelMC]

On 5/19/2022 at 12:08 PM, crococat said:

From mod description it is not quite understandable that with SLU+ mod Sexlab had be treated as SE mod even in LE game.

Is not specified but since one of my objectives was bringing to LE the improvements of SE is implied that you should be able of do the same as with the SE version. Almost the same, because the oral, vaginal and Anal count are exclusive of the SE DLL and I don't know the details to make it work on LE that probably is possible.

[OsmelMC]

9 hours ago, Talesien said:

Small problem ... ok medium sized.
While your Outfit Manager works fine with my current  load order and save I can't get it to work on the new setup I'm working on. Right after starting a new game the MCM shows the title image, but no menu entries. If opened again even the title image is missing. Tried to move it up or down in the load order to no avail. Tried removing The Luxury Suite (on the off chance that the outfit manager option of it collides with your outfit manager somehow ... but no dice). Can't find anything in the log either, but perhaps that's just because I've no real idea what to look for, so I attached it.

Papyrus.0-outfit_manager_bug.log 427.26 kB · 0 downloads

That's for the log. That was reported already and I trying to figure out but without the logs is very hard.

 

 

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

Ok the logs show nothing about the Outfit Manager so isn't a error at least.

 

But is showing a lot of other error related with the Player Load Game event on some Mods that are not supposed to happen unless be a new game or the save be corrupted.

 

One more thing is that your papyrus looks really busy until last second before close the game, apparently installing DDi objects and animations.

 

Check the saved game with the ReSave too and wait until the rest of the mod setup's be finished.

 

Even before the first release i know the Outfit Manager MCM won't be showed until his Main Quest be started and that quest have low priority compared with the setup of the rest of the Mods so won't be started until the end of the setups but once started all will be fine.

 

I'm thinking on some solution or at least some information on the MCM.

Edited May 20, 2022 by OsmelMC

[OsmelMC]

On 5/19/2022 at 1:45 PM, Nymra said:

I also seem to be unable to equip the tongues...

 

- I did not yet try to revert on older version of SLU+ but with the current the tongues do not show up, get not equiped at the start of sex in inventory and I cannot select tongues for my Custom 1-5 animation sets.

Revert it probably solve nothing. I already noticed the mistake few weeks ago developing the Outfit Manager. In some point I enable one parameter on the equip function that prevent it to be replaced until be unequipped. Is already fixed.

[dePog]

Quick question about MFF threesomes and how they work with SL Separate Orgasms

 

I have 8 animations that are available when my PC is male and has two female partners,

but only two of them (in red outline below) allow the females to orgasm.
In the others, the females get to 200% and just stay there. I have to switch the animation over to either Femdom 2 or Femdon 3 to allow them to cum.

 

Even Anub's first Femdom animation (the one at the bottom of this list) won't let them orgasm.

 

 

I have even loaded the Jason files and made the "tags" of the other animations match the tags of Femdon 2 & 3, but it still doesn't fix it.

 

Any thoughts?

 

PS: In SLSO's MCM I have tried toggling "Female Orgasm Conditions" off and on, but makes no difference

Edited May 21, 2022 by dePog

[Talesien]

22 hours ago, OsmelMC said:

That's for the log. That was reported already and I trying to figure out but without the logs is very hard.

 

 

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

Ok the logs show nothing about the Outfit Manager so isn't a error at least.

 

But is showing a lot of other error related with the Player Load Game event on some Mods that are not supposed to happen unless be a new game or the save be corrupted.

 

One more thing is that your papyrus looks really busy until last second before close the game, apparently installing DDi objects and animations.

 

Check the saved game with the ReSave too and wait until the rest of the mod setup's be finished.

 

Even before the first release i know the Outfit Manager MCM won't be showed until his Main Quest be started and that quest have low priority compared with the setup of the rest of the Mods so won't be started until the end of the setups but once started all will be fine.

 

I'm thinking on some solution or at least some information on the MCM.

 

That log was the first load after initial start. So start new game, wait till the notification spam stops, save, close game, start game, load save. Hence well possible some mods were only then starting to initialize. And yes there are a few things I need to work on, as mentioned it's a new load order that I'm currently working on, so some problems are to be expected (and to be corrected ... hopefully).

Coc'ed around a bit to check for clipping, conflicts and such. Here is a log from inside Aradias. That one might be more interesting (it's certainly somewhat disturbing to me)it got stack dumps ... loads of it, at a steady 60FPS. Most dumps are from the various Toys framework mods, but also some from a: "OM_MainQuest". Can't place that OM makes me think of Outfit Manager perhaps?
 

Papyrus.0_outfit_manager_bug_stack_dumps.log

[OsmelMC]

52 minutes ago, Talesien said:

 

That log was the first load after initial start. So start new game, wait till the notification spam stops, save, close game, start game, load save. Hence well possible some mods were only then starting to initialize. And yes there are a few things I need to work on, as mentioned it's a new load order that I'm currently working on, so some problems are to be expected (and to be corrected ... hopefully).

Coc'ed around a bit to check for clipping, conflicts and such. Here is a log from inside Aradias. That one might be more interesting (it's certainly somewhat disturbing to me)it got stack dumps ... loads of it, at a steady 60FPS. Most dumps are from the various Toys framework mods, but also some from a: "OM_MainQuest". Can't place that OM makes me think of Outfit Manager perhaps?
 

Papyrus.0_outfit_manager_bug_stack_dumps.log 826.65 kB · 0 downloads

The Stack Dumps aren't errors, is just tracked info. I think is related with the logs stored in another files. SexLab, Outfit Manager and some other Mods have his own log files in a folder inside the folder of the papyrus logs. In my case the file "OutfitManager.0.log" show all the logs i track on my Mod, and the "Papyrus.0.log" show only the errors on the scripts but should be none because is the first i look each time I changed something on the scripts.

 

The Stack Dumps show good info but for me is hard to read and since is just info without errors i just check it for curiosity

[OsmelMC]

1 hour ago, Talesien said:

 

That log was the first load after initial start. So start new game, wait till the notification spam stops, save, close game, start game, load save. Hence well possible some mods were only then starting to initialize. And yes there are a few things I need to work on, as mentioned it's a new load order that I'm currently working on, so some problems are to be expected (and to be corrected ... hopefully).

Coc'ed around a bit to check for clipping, conflicts and such. Here is a log from inside Aradias. That one might be more interesting (it's certainly somewhat disturbing to me)it got stack dumps ... loads of it, at a steady 60FPS. Most dumps are from the various Toys framework mods, but also some from a: "OM_MainQuest". Can't place that OM makes me think of Outfit Manager perhaps?
 

Papyrus.0_outfit_manager_bug_stack_dumps.log 826.65 kB · 4 downloads

Are you using a Mod to sort the MCM? Because I reading on your log that you are opening page's on the Outfit Manager MCM but are not my pages and that is not possible.

[Talesien]

I

22 minutes ago, OsmelMC said:

Are you using a Mod to sort the MCM? Because I reading on your log that you are opening page's on the Outfit Manager MCM but are not my pages and that is not possible.

I'm using Menu Maid 2 (and MCM Recorder), but it has no effect if I remove either (or both) of those.

I seem to have found the root of the problem though. Most unexpected too. I was planning to use Redux (https://www.nexusmods.com/skyrimspecialedition/mods/66920?tab=description) for this play through. Turns out though, its alternate start mechanism is a bit unwieldy for initial tests. So I replaced it with my usual: Alternate Perspectives. And just like that Outfit Manager starts working, stack dumps are gone ...

Anyway I included the only OM log that survived from the time I've been using Redux, does not look like it helps much though.

OutfitManager.3.log

[OsmelMC]

2 hours ago, Talesien said:

I

I'm using Menu Maid 2 (and MCM Recorder), but it has no effect if I remove either (or both) of those.

I seem to have found the root of the problem though. Most unexpected too. I was planning to use Redux (https://www.nexusmods.com/skyrimspecialedition/mods/66920?tab=description) for this play through. Turns out though, its alternate start mechanism is a bit unwieldy for initial tests. So I replaced it with my usual: Alternate Perspectives. And just like that Outfit Manager starts working, stack dumps are gone ...

Anyway I included the only OM log that survived from the time I've been using Redux, does not look like it helps much though.

OutfitManager.3.log 2.63 kB · 4 downloads

Help more than expected...

If is really a log with the issue. Show the opening of the configuration and process that are only possible if the Main Quest was started. So the problem is not the main quest.

 

This log together with the last one with the Stack Dumps bring me some ideas for the solution.

Also make me think that installing the Mod after load and save the alternative start, should avoid the issue. If bad not remember some alternative start of Nexus cause issues on more than one Mod.

Edited May 21, 2022 by OsmelMC

[Talesien]

1 hour ago, OsmelMC said:

Help more than expected...

If is really a log with the issue. Show the opening of the configuration and process that are only possible if the Main Quest was started. So the problem is not the main quest.

 

This log together with the last one with the Stack Dumps bring me some ideas for the solution.

Also make me think that installing the Mod after load and save the alternative start, should avoid the issue. If bad not remember some alternative start of Nexus cause issues on more than one Mod.

It is a definitely a log with the issue. That log is from the afternoon, and I only switched the alternate start mod a couple hours later. That the main quest did start fits in with the stack dumps, doubt it would produce those if it hadn't started.

Installing the mod later would require you to make it esl flagged though (yes I noticed it's esl ready, still the flag is not set). At any rate that sounds more like a workaround than a solution. I guess it's fine, since only a few people seem to encounter that problem, but perhaps a trigger to activate the mod later (kinda like sexlab) would work as well?

[sidfu1]

looks like tongues need more work.
1. if you turn on both options for tongues when you have sex it can cause the heel effect to get reapplied even thou they dont have heels on.(still verifying it)
2. if using your outfit manager mod from nexus the  add items to inventory causes them to equip all the items they carry.

[OsmelMC]

15 hours ago, Talesien said:

It is a definitely a log with the issue. That log is from the afternoon, and I only switched the alternate start mod a couple hours later. That the main quest did start fits in with the stack dumps, doubt it would produce those if it hadn't started.

Installing the mod later would require you to make it esl flagged though (yes I noticed it's esl ready, still the flag is not set). At any rate that sounds more like a workaround than a solution. I guess it's fine, since only a few people seem to encounter that problem, but perhaps a trigger to activate the mod later (kinda like sexlab) would work as well?

I did the option to force it but isn't tested under those conditions and for your log seems like is not the expected issue and apparently is something more weird.

 

The next version will come with the ESL flag and one file that should garantice the quest startup