Diary Of Mine for Paradise Halls

[TrollAutokill]

6 hours ago, DocClox said:

 

Can do.

 

  Hide contents

 

 

 

 

 

First there is probably a missing mod you have been removed and not cleaned listed as "unknown".

 

Second she has none of the 2 DOM scripts. That's very weird. I will check the alias 30, maybe it is badly set.

 

Third, if this is the Bodil in the camp, what about the one in Breezehome?

 

Edited December 29, 2024 by TrollAutokill

[DocClox]

8 hours ago, TrollAutokill said:

First there is probably a missing mod you have been removed and not cleaned listed as "unknown".

 

Don't think so - I've been fairly careful this time around. Certainly nothing that should spawn or affect NPCs. Still, can't hurt to run the save through a cleaner and see what gets reported.

 

8 hours ago, TrollAutokill said:

Third, if this is the Bodil in the camp, what about the one in Breezehome?

 

This is the one in Breezehome, despite what it says for Location. That's where I captured her: I was in vampire lord form and the stormies took exception. The original version is in Castle Volkihar, I'll take a look at her in a minute.

 

8 hours ago, TrollAutokill said:

Second she has none of the 2 DOM scripts. That's very weird. I will check the alias 30, maybe it is badly set.

 

I've noticed this only ever happens to respawning NPCS. So I think what is happening may be that some of the DoM packages get applied to the ActorBase rather than the actor instance, so when a new version spawns it comes with some (but not all) of the DoM scripts/aliases/packages affecting it. Sort of a variation on the Naked Bandit problem of old.

 

And I'm guessing that accounts for teleporting them to wherever I fast travel to, but they then t-pose because they don't have a complete DoM setup, and the animation that should play has conditions they can't meet.

 

I also seem to remember that if I give them long enough they'll eventually initialize properly and be full fledged NPCs. At least I think this used to happen with the Cronvangr Cave vamps, but it's been a while since that happened and my memory may be playing me false.

[DocClox]

This is the original:

 

Spoiler

 

 

"Unknown" here too.

 

 

Same packages.

 

 

Edited December 29, 2024 by DocClox

[TrollAutokill]

12 minutes ago, DocClox said:

This is the original:

 

  Hide contents

 

 

"Unknown" here too.

 

 

Same packages.

 

 

They don't have the same NPC base form id so they are not a clone of each other and I think we can forget about the working Bodil on slave alias 12.

 

The other one 00039CF8 is a spawned bandit on slave alias 30 without scripts. I'll check it.

[DocClox]

32 minutes ago, TrollAutokill said:

They don't have the same NPC base form id so they are not a clone of each other

 

Good point. Curiouser and curiouser.

[DocClox]

Oh, one more thing: They follow me around.

 

Here's Bodil2 at the entrance to Castle Volkihar. Not sure when she arrived, since I looked when I first arrived and she wasn't there. But she's waiting for me when I'm ready to leave.

 

I may have slept while here, which I'm starting to think is a factor.

 

[TrollAutokill]

33 minutes ago, DocClox said:

Oh, one more thing: They follow me around.

 

Here's Bodil2 at the entrance to Castle Volkihar. Not sure when she arrived, since I looked when I first arrived and she wasn't there. But she's waiting for me when I'm ready to leave.

 

I may have slept while here, which I'm starting to think is a factor.

 

I will try to clean aliases without scripts at startup in next update. Hopefully that will fix her. I didn't find anything weird with alias 30.

[TrollAutokill]

1 hour ago, DocClox said:

Oh, one more thing: They follow me around.

 

Here's Bodil2 at the entrance to Castle Volkihar. Not sure when she arrived, since I looked when I first arrived and she wasn't there. But she's waiting for me when I'm ready to leave.

 

I may have slept while here, which I'm starting to think is a factor.

 

Try version 7.1.9  with check for bad aliases at startup. Check to see if they still both have their package set to DOM's. Alias 30 should be gone. Also check the slave array recovery at startup in the logfile.

 

Edited December 29, 2024 by TrollAutokill

[wower2345]

On 12/23/2024 at 10:57 PM, AnonymousUser007 said:

Yeah, trying to teach slaves how to be good girls or boys is a bad idea with sexlab p+. For me they start scenes and then become unable to do anything. I can interact with them however it doesn't actually do anything and I havent found a way to get them out of that state. Tried resetting, tried deleting them out of the sexlab faction, transferring to pah (where they suddenly just work until you transfer them back), disable/enable, and even releasing and recapturing with no results. Tried ignoring the sex component entirely but I accidentally clicked the rape option while trying to comfort my highest trained slave and now its joever. Hopefully compatibility comes soon TM.

Out of curiosity does this bug occur on DOM version 7.1.4 with your LO?

[TrollAutokill]

6 minutes ago, wower2345 said:

Out of curiosity does this bug occur on DOM version 7.1.4 with your LO?

This bug is happening because p+ doesn't send the same end of sex event as standard SL. It's the same with all versions of DOM and probably PAH.

[wower2345]

12 minutes ago, TrollAutokill said:

This bug is happening because p+ doesn't send the same end of sex event as standard SL. It's the same with all versions of DOM and probably PAH.

Hmm, well, I asked because I personally tested this issue on multiple versions of DOM and p+, and it would seem that the bug doesn't occur on 7.1.4. I just wanted to double-check and make sure that is also the case for others.

For your information, I played with p+ most of the time along with DOM, and this issue is definitely something recent.

Edited December 29, 2024 by wower2345

[TrollAutokill]

8 minutes ago, wower2345 said:

Hmm, well, I asked because I personally tested this issue on multiple versions of DOM and p+, and it would seem that the bug doesn't occur on 7.1.4. I just wanted to double-check and make sure that is also the case for others.

For your information, I played with p+ most of the time along with DOM, and this issue is definitely something recent.

The incompatibilities with p+ are not recent. In 7.1.4 the Sexlab functions were moved to a dedicated interface script DOM_Sexlab.psc, using the good old copy paste method, so nothing to expect from these changes. But the changes were made so it can be more easily adapted to p+ in the future.

[wower2345]

Just now, TrollAutokill said:

The incompatibilities with p+ are not recent. In 7.1.4 the Sexlab functions were moved to a dedicated interface script DOM_Sexlab.psc, using the good old copy paste method, so nothing to expect from these changes. But the changes were made so it can be more easily adapted to p+ in the future.

I'm just sharing my own experiences, there may be more to it that I'm not aware of, I'm happy that you plan on adapting it in the future.

[AnonymousUser007]

3 hours ago, wower2345 said:

Out of curiosity does this bug occur on DOM version 7.1.4 with your LO?

No idea, didnt play 7.1.4 because my I was waiting for my modlist to update. I have been playing 7.1.8 quite a bit and I've noticed that I'm getting the no worky worky (occasionally, havent figured out what changes when it doesnt work) with Lydia and Camilla however whenever I have my companion do the worky worky on them it just works and gives training reasons for both events. I think what is happening is for some reason my companion (Jenassa) isnt able to actually start the animation so it just sends a "Job Done" and it just works cause she only actually goes into the animation maybe 20% of the time. The other times it has sent the "Job Done" event before the animation even started.

[wower2345]

1 hour ago, AnonymousUser007 said:

No idea, didnt play 7.1.4 because my I was waiting for my modlist to update. I have been playing 7.1.8 quite a bit and I've noticed that I'm getting the no worky worky (occasionally, havent figured out what changes when it doesnt work) with Lydia and Camilla however whenever I have my companion do the worky worky on them it just works and gives training reasons for both events. I think what is happening is for some reason my companion (Jenassa) isnt able to actually start the animation so it just sends a "Job Done" and it just works cause she only actually goes into the animation maybe 20% of the time. The other times it has sent the "Job Done" event before the animation even started.

If you have the time you could try testing it out to either concur with my findings or not.

[AnonymousUser007]

1 hour ago, wower2345 said:

If you have the time you could try testing it out to either concur with my findings or not.

No

[Empt1e]

Crying animations play during sexlab scenes and thus stop the sex animations until the end of the scene

[hothot995]

Excuse me, I’d like to ask:

Will the effect of tears disappear automatically?

How long does it take for it to go away?

Or is there a specific way to make it disappear? Thank you!

[Durante]

On 12/26/2024 at 9:23 PM, TrollAutokill said:

Try elephant script latency tester.

 

I've solved all my script lag issues with lossless scaling app, the slavetats are appearing properly now and the game is MUCH smoother lol.

Edited December 30, 2024 by Durante

[Durante]

1 hour ago, hothot995 said:

Excuse me, I’d like to ask:

Will the effect of tears disappear automatically?

How long does it take for it to go away?

Or is there a specific way to make it disappear? Thank you!

 

The tears are supposed to show the emotional state of the captive. It disappears once their mood changes, which you can wait or by interacting with them to comfort them

Edited December 30, 2024 by Durante

[TrollAutokill]

1 hour ago, Durante said:

 

I've solved all my script lag issues with lossless scaling app, the slavetats are appearing properly now and the game is MUCH smoother lol.

So what was the actual solution?

[The Man in Black]

I've finally got my new computer and new setup and am building a new load order based on a Wabbajack modlist. I'm experiencing a weird issue where there's a momentary fade to black whenever DOM does an animation, and I'm trying to figure out what is causing it. Is this something in the new version or do I need to dig deeper into the modlist I'm using as my base?

[TrollAutokill]

16 minutes ago, The Man in Black said:

I've finally got my new computer and new setup and am building a new load order based on a Wabbajack modlist. I'm experiencing a weird issue where there's a momentary fade to black whenever DOM does an animation, and I'm trying to figure out what is causing it. Is this something in the new version or do I need to dig deeper into the modlist I'm using as my base?

Definitely not something new. But you need to know DOM's animations use Sexlab functions to align the actors. I don't know what happens if you switch to p+ for example.

Edited December 30, 2024 by TrollAutokill

[Durante]

1 hour ago, TrollAutokill said:

So what was the actual solution?

 

I think the solution was to reduce script lag. Which I did by changing the game's resolution to a lower one and using a rescale app like the one I mentioned, for a small drop in quality everything is practically lag free now.

[The Man in Black]

34 minutes ago, TrollAutokill said:

Definitely not something new. But you need to know DOM's animations use Sexlab functions to align the actors. I don't know what happens if you switch to p+ for example.

Yep. It's definitely not DOM. Just confirmed it is still happening with a SL scene started through a different mod.