Diary Of Mine for Paradise Halls

[DocClox]

I'm talking about these girls:

 

 

They're not PAH slaves at all. Just a collection of eye candy NPCs.

 

I don't know if they're wearing outfits or where these garments are coming from. I just wondered if you might have missed a condition on a redressing event. If not that's fine - the next most likely candidate is probably something broken loose in my last bashed patch.

[gekker]

4 hours ago, TrollAutokill said:

 

It's very hard to understand what you're trying to achieve.

 

Please answer the 3 following questions as simply as possible:

 

Do you see the same happening with PAH slaves and DoM slaves when initiating sexlab scenes? If no what's the difference? If yes, what would like to be different?

 

What I am trying to achieve is simply for the slave to be captured, have an outfit that I set, and then have it left alone unless *I* change adjust it or Sexlab MCM options temporarily removes whatever I specify in the Sexlab MCM strip options before consensual, aggressive, or foreplay scenes for Male/Female or Victim/Aggressor.

 

With PAHE slaves the slaves only remove items that are specified by Sexlab MCM options, in the appropriate slots. (Head, Body, etc.) 

 

In DOM, when I capture a slave, the slave strips everything, regardless of Sexlab slot options, regardless of what I add or remove to their inventory, regardless of dialogue options. 

 

Once the slave is captured outright with DOM or transferred from PAHE, "something" is done to the items I attempt to add to their inventory and have them equip that causes them to be removed before all Sexlab sex scenes fire.  The only exception was the wig, which seemed to be protected from this, and I highlighted what I thought may be the cause in my previous post with DOM_Actor registering forms "to be stripped", which would explain why stripping happens universally once that script runs. 

 

So there is a difference in what is occurring and to answer the question, "what I would like" is one or more of the following:

 

1) Some way to prevent items from being designating that they be stripped.  There is no apparent way to prevent or reverse this currently. Perhaps being able to set clotihng slots to be "ignored" by the mod when determining what should or should not be stripped.

 

2) The ability to disable this current implementation of inventory management via menu for those that don't need this level of micromanagement from the MOD.  Or deferring to PAHE's method of equipping and unequipping items without these scripts running on them.  These issues seem to have started for me when the new "You should wear clothes/you should be naked/your should equip armor" functionality was added.  Having an option DoM that does nothing but equip or unequip items in inventory, like PAHE, would be nice. 

 

This way if I want a slave to be naked, I don't give them any armor items.  If I want a slave to wear armor/clothes, I put items I deem to be armor or clothes into the inventory. If I have sex with a slave they only remove what is in the appropriate slots via Sexlab MCM.   Currently I cannot make these things, especially the latter, happen in DoM. 

 

[TrollAutokill]

4 hours ago, gekker said:

 

What I am trying to achieve is simply for the slave to be captured, have an outfit that I set, and then have it left alone unless *I* change adjust it or Sexlab MCM options temporarily removes whatever I specify in the Sexlab MCM strip options before consensual, aggressive, or foreplay scenes for Male/Female or Victim/Aggressor.

 

With PAHE slaves the slaves only remove items that are specified by Sexlab MCM options, in the appropriate slots. (Head, Body, etc.) 

 

In DOM, when I capture a slave, the slave strips everything, regardless of Sexlab slot options, regardless of what I add or remove to their inventory, regardless of dialogue options. 

 

Once the slave is captured outright with DOM or transferred from PAHE, "something" is done to the items I attempt to add to their inventory and have them equip that causes them to be removed before all Sexlab sex scenes fire.  The only exception was the wig, which seemed to be protected from this, and I highlighted what I thought may be the cause in my previous post with DOM_Actor registering forms "to be stripped", which would explain why stripping happens universally once that script runs. 

 

So there is a difference in what is occurring and to answer the question, "what I would like" is one or more of the following:

 

1) Some way to prevent items from being designating that they be stripped.  There is no apparent way to prevent or reverse this currently. Perhaps being able to set clotihng slots to be "ignored" by the mod when determining what should or should not be stripped.

 

2) The ability to disable this current implementation of inventory management via menu for those that don't need this level of micromanagement from the MOD.  Or deferring to PAHE's method of equipping and unequipping items without these scripts running on them.  These issues seem to have started for me when the new "You should wear clothes/you should be naked/your should equip armor" functionality was added.  Having an option DoM that does nothing but equip or unequip items in inventory, like PAHE, would be nice. 

 

This way if I want a slave to be naked, I don't give them any armor items.  If I want a slave to wear armor/clothes, I put items I deem to be armor or clothes into the inventory. If I have sex with a slave they only remove what is in the appropriate slots via Sexlab MCM.   Currently I cannot make these things, especially the latter, happen in DoM. 

 

This is not DoM script, Sexlab script is deciding what to strip. There is maybe a Sexlab setting which is different between Dom and PAH, I will check.

 

DoM equipment policy is only applied at the end of the sex scene. But you said it happens at the start. Correct?

Edited June 13, 2023 by TrollAutokill

[gekker]

1 hour ago, TrollAutokill said:

This is not DoM script, Sexlab script is deciding what to strip. There is maybe a Sexlab setting which is different between Dom and PAH, I will check.

 

DoM equipment policy is only applied at the end of the sex scene. But you said it happens at the start. Correct?

 

It happens at the start of the scene, before the sex animation. From what I can see as a user staring at the screen:

 

1) I access inventory, give them items, remove items I don't want in inventory.  Slave equips the items.

2) I initiate sex.  The sexlab pre sex strip animation plays, removing all items, before the actual animation starts playing.

 

Once this happens, it persists whether I initiate sex via DoM or PAHE. 

 

As an experiment I:

 

Capture a slave in PAHE, initiate sex via PAHE to confirm the items are not removed, unless in slots detailed in Sexlab settings. 

 

Next I transfer that slave to DOM.  I initiate sex, to confirm that the items are now stripped during pre sex animation, regardless of me not using any DoM commands regarding stripping, wearing armor/clothing.

 

Next I abduct a slave, only using DoM.  What I describe in steps 1 and 2 above is what happens.

 

My thought is, if Sexlab is controlling the stripping pre sex animation, "something" is flagging the items to be stripped and Sexlab is picking that up, across 2 different mods calling on it to activate sex animations

 

Edited June 13, 2023 by gekker

[ZZW]

18 minutes ago, gekker said:

 

It happens at the start of the scene, before the sex animation. From what I can see as a user staring at the screen:

 

1) I access inventory, give them items, remove items I don't want in inventory.  Slave equips the items.

2) I initiate sex.  The sexlab pre sex strip animation plays, removing all items, before the actual animation starts playing.

 

Once this happens, it persists whether I initiate sex via DoM or PAHE. 

 

As an experiment I:

 

Capture a slave in PAHE, initiate sex via PAHE to confirm the items are not removed, unless in slots detailed in Sexlab settings. 

 

Next I transfer that slave to DOM.  I initiate sex, to confirm that the items are now stripped during pre sex animation, regardless of me not using any DoM commands regarding stripping, wearing armor/clothing.

 

Next I abduct a slave, only using DoM.  What I describe in steps 1 and 2 above is what happens.

 

My thought is, if Sexlab is controlling the stripping pre sex animation, "something" is flagging the items to be stripped and Sexlab is picking that up, across 2 different mods calling on it to activate sex animations

 

Same here. It seems slaves ignore the sexlab stripping option

[TrollAutokill]

1 hour ago, gekker said:

 

It happens at the start of the scene, before the sex animation. From what I can see as a user staring at the screen:

 

1) I access inventory, give them items, remove items I don't want in inventory.  Slave equips the items.

2) I initiate sex.  The sexlab pre sex strip animation plays, removing all items, before the actual animation starts playing.

 

Once this happens, it persists whether I initiate sex via DoM or PAHE. 

 

As an experiment I:

 

Capture a slave in PAHE, initiate sex via PAHE to confirm the items are not removed, unless in slots detailed in Sexlab settings. 

 

Next I transfer that slave to DOM.  I initiate sex, to confirm that the items are now stripped during pre sex animation, regardless of me not using any DoM commands regarding stripping, wearing armor/clothing.

 

Next I abduct a slave, only using DoM.  What I describe in steps 1 and 2 above is what happens.

 

My thought is, if Sexlab is controlling the stripping pre sex animation, "something" is flagging the items to be stripped and Sexlab is picking that up, across 2 different mods calling on it to activate sex animations

 

 

1 hour ago, ZZW said:

Same here. It seems slaves ignore the sexlab stripping option

A simple reason might be Sexlab is looking at keyword substrings. In other words, Sexlab is trying too hard with stripping...

 

I will post an updated version with different DoM keyword names, for you to try.

Edited June 13, 2023 by TrollAutokill

[gekker]

13 minutes ago, TrollAutokill said:

 

A simple reason might be Sexlab is looking at keyword substrings

 

I will post an updated version with different DoM keyword names, for you to try.

Okay sounds good, thanks for looking into it.

[TrollAutokill]

3 hours ago, gekker said:

Okay sounds good, thanks for looking into it.

 

3 hours ago, ZZW said:

Same here. It seems slaves ignore the sexlab stripping option

 

For you to test, if you're using SE and now LE

 

Version 4.7.7 is out, it's a development version, mostly bug fixes.

 

• Changed DOM keyword names to avoid interference with Sexlab stripping (SE and LE).
• Strip ALL should now ignore slots 31, 41, 60 and 61.

 

In need of a backport to LE.

 

Edited June 13, 2023 by TrollAutokill

[gekker]

33 minutes ago, TrollAutokill said:

 

 

For you to test, if you're using SE.

 

Version 4.7.7 is out, it's a development version, mostly bug fixes.

 

• Changed DOM keyword names to avoid interference with Sexlab stripping. (SE only)
• Strip ALL should now ignore slots 31, 41, 60 and 61.

 

In need of a backport to LE.

 

 

I'll need to wait for backport.

[TrollAutokill]

12 minutes ago, gekker said:

 

I'll need to wait for backport.

Let's hope  @The new guy1 is around.

[ZZW]

1 hour ago, TrollAutokill said:

 

 

For you to test, if you're using SE.

 

Version 4.7.7 is out, it's a development version, mostly bug fixes.

 

• Changed DOM keyword names to avoid interference with Sexlab stripping. (SE only)
• Strip ALL should now ignore slots 31, 41, 60 and 61.

 

In need of a backport to LE.

 

The stripping fixed

[TrollAutokill]

2 hours ago, gekker said:

 

I'll need to wait for backport.

Meanwhile try this one: (it's an xedit-ed version) for LE only.

 

If it doesn't work you migth want to download TES5EDit and change the names of the DOM keywords yourself.

DOMAlwaysStrip should be renamed to DOMMarkForStrip and DOMNoStrip to DOMMarkForNotStrip.

 

NOTE: This esp is now included in 4.7.7.

 

DiaryOfMine.esp

Edited June 13, 2023 by TrollAutokill

[gekker]

50 minutes ago, TrollAutokill said:

Meanwhile try this one: (it's an xedit-ed version) for LE only.

 

If it doesn't work you migth want to download TES5EDit and change the names of the DOM keywords yourself.

DOMAlwaysStrip should be renamed to DOMMarkForStrip and DOMNoStrip to DOMMarkForNotStrip.

 

 

DiaryOfMine.esp 1.19 MB · 3 downloads

 

Briefly tested but so far looks like this is a winner.  The slave did not strip anything not set to be stripped in Sexlab Strip options.

 

Looks good! Thanks for looking into it.

 

[MortiferusX]

Everytime i try to give my Slave a potion or set an exemple, I stuck ...

[TrollAutokill]

16 minutes ago, MortiferusX said:

Everytime i try to give my Slave a potion or set an exemple, I stuck ...

Which version? SE, LE, VR? Do you see the correct animation? IS it the just player who is stuck?

Edited June 13, 2023 by TrollAutokill

[MortiferusX]

Just now, TrollAutokill said:

Which version? SE, LE, VR?

 

SE

[TrollAutokill]

28 minutes ago, MortiferusX said:

 

SE

Do you mean the player is stuck after the animation, but the animation is playing normally?

 

Make sure you don't have the 3rd person view on, in the DoM settings.

Edited June 13, 2023 by TrollAutokill

[MortiferusX]

Just now, TrollAutokill said:

Do you mean the player is stuck after the animation, but the animation is playing normally?

 

Exactly. The animation is playing, but after that, I stuck on place and can not move. 

[TrollAutokill]

30 minutes ago, MortiferusX said:

 

Exactly. The animation is playing, but after that, I stuck on place and can not move. 

Unfortunately I can not reproduce this. I know it can happen, certainly some incompatibility with another mod,  but for the moment I have no clue of the cause.

 

You can try to: always sheath your weapon before an animation.

 

If you're stuck: Try to draw weapon or teleport the player to another place.

 

[MortiferusX]

5 minutes ago, TrollAutokill said:

 

If you're stuck: Try to draw weapon or teleport the player to another place.

 

Coc command?

 

Because normal fast travel won't work then i can not Open the map. Not sure i can open the console. Need to try tomorrow. 

[theman123]

The last few versions have killed my main save file. It crashes whenever I try to save the game. I uninstalled DOM and managed to clean the file with resaver and it works now.

[深淵の神]

5 hours ago, MortiferusX said:

Everytime i try to give my Slave a potion or set an exemple, I stuck ...

 

If you mean the animation stuck and the character is not responding anymore I remember this happen when toggle free cam in DOM animations, try disable that

[TrollAutokill]

6 hours ago, theman123 said:

The last few versions have killed my main save file. It crashes whenever I try to save the game. I uninstalled DOM and managed to clean the file with resaver and it works now.

SE? Which version did you come from?

Edited June 14, 2023 by TrollAutokill

[notimportanterik]

13 hours ago, MortiferusX said:

Everytime i try to give my Slave a potion or set an exemple, I stuck ...

 As others have stated, the free cam option did this to me from time to time when animations were finished running, so make sure that is disabled.

are you also running Ostim/Ostim ng? i experienced this when those were in my load order even with the free cam option disabled so i had to remove it from my load order. I would suggest sticking to either Sexlab and its mods, or Ostim/Otsim ng and its mods, but not mixing both...

[MortiferusX]

11 hours ago, サマエル said:

 

If you mean the animation stuck and the character is not responding anymore I remember this happen when toggle free cam in DOM animations, try disable that

Thanks, will try that when i am home.