Jump to content

Dripping When Aroused NG


Recommended Posts

Posted

Have a strange issue where my NPCs start blinking in and out of existence (going invisible for a millisecond) when the effect is on, it seems to happen only sometimes tho, no idea how to fix it, just randomly happens 

Posted
On 1/12/2025 at 9:49 PM, R3nko said:

Interesting... This has a virginity system... Sorry for this typical question, but does it interferes with OVirginity Reflowered?

 

You can set it to follow it's own system or SL virginity tracking in the MCM. Same as original mod.

Posted
On 1/13/2025 at 9:13 PM, Prizbiggie said:

Have a strange issue where my NPCs start blinking in and out of existence (going invisible for a millisecond) when the effect is on, it seems to happen only sometimes tho, no idea how to fix it, just randomly happens 

 

Yes, this is a known issue in original mod. Something about the dripping visual effects causes blinking npcs in the blue palace bedroom areas and whiterun breezehome, maybe other places too?

Posted
On 1/13/2025 at 11:09 PM, evil-I-r-n00b said:

This is great. Thanks.  It checks off one of my two wishes for DWA  (the other is pregnancy and pregnancy recovery detection of fertility mode for an MCM option for milk leaking)

 

lol, submit a PR and I'll take a look.

Posted
On 1/21/2025 at 3:59 AM, stnfnk said:

 

Yes, this is a known issue in original mod. Something about the dripping visual effects causes blinking npcs in the blue palace bedroom areas and whiterun breezehome, maybe other places too?

Loads of places, can't even name them all.

Posted (edited)

I installed the mod today.
looks good in the Sex Slaves mod when they masturbate in the chair..
The slaves that are attached to an X also drip.
But when it comes to ostim sex from behind it fails, the breasts flutter like old milk cartons and the amount that then shoots out of the breast in four jets is too much and too long.
Even when pussylicking, something on the stomach bulges out like the schlong is too long.
If it sprayed thinner from the chest it would be more realistic, but it looks like it was poured out of 4 watering cans.
Unfortunately I had to deactivate the mod again.

 

edit: But it could also be in connection with OCUM that the amount is so much that a lot comes from the pussy...

Edited by dschlaqinwe
more information
Posted
4 hours ago, dschlaqinwe said:

I installed the mod today.
looks good in the Sex Slaves mod when they masturbate in the chair..
The slaves that are attached to an X also drip.
But when it comes to ostim sex from behind it fails, the breasts flutter like old milk cartons and the amount that then shoots out of the breast in four jets is too much and too long.
Even when pussylicking, something on the stomach bulges out like the schlong is too long.
If it sprayed thinner from the chest it would be more realistic, but it looks like it was poured out of 4 watering cans.
Unfortunately I had to deactivate the mod again.

 

edit: But it could also be in connection with OCUM that the amount is so much that a lot comes from the pussy...

 

Belly bulge and breast physics are not affected by this mod. Look to your CBPC or SMP settings.

 

The milk leak animation has point of origin hard coded in the nif. It won't look great with some size bodies/physics settings. Original author mentions on original mod page that you can edit the coordinates in the nif to customize. You can always turn off the milk leak effect in MCM.

 

I don't use OCum because of an issue in VR. If it is adding similar effects, you might be seeing both? Maybe turn one of them off.

 

 

Posted (edited)

        Okay, strange bug here, but I was using the Old Drip with SOS, then I switched over to TNG.  At first, Drip seemed to be fine, but I was still building out my mod list, and it suddenly stopped working.  It was complaining about SOS not being installed and telling me that I needed to fix my plugins.  While trying to fix that, I discovered this mod, and rejoiced that all my problems had been solved!  I wasn't sure if this mod needed the Old Drip or not (the mod download page doesn't say either way), so I only disabled Old Drip in MO2 and installed and enabled Drip NG.  Ran a test boot, everything was working, no errors, so, assuming that Drip NG doesn't need anything from Old Drip, I uninstalled it from MO2, and went on modding.  Imagine my surprise on my next test boot when I started getting the same old "No SOS, please fix plugins" error from Drip NG!  Much testing later, and I found a bug that I didn't even know was possible.  So long as I have Old Drip installed, and I have activated it at least once, Drip NG will work (Old Drip is deactivated), but if Old Drip isn't installed, or hasn't been activated at least once, Drip NG won't work...

        So, what files from Old Drip does Drip NG need to work on my setup?!?  And how is it using them when Old Drip is disabled in MO2?!?  Should I have Old Drip installed and activated or not?!  Please clarify this in the requirements on the Mod download page, as I'm sure many others also wonder if Old Drip is needed or not!

 

 

        Update:  Still randomly getting that same "No SOS, please fix plugins" error from Drip NG when installing new mods...  Disabling them, running the game once, then re-enabling them seems to fix it, sometimes?!?  If not, then enabling then disabling Old Drip does...  Oh, and leaving Old Drip Enabled also gives the same error message.  It must be enabled then disabled.  What in the world is going on here???

Edited by 700 Tnega Terces
Posted (edited)
7 hours ago, 700 Tnega Terces said:

        Okay, strange bug here, but I was using the Old Drip with SOS, then I switched over to TNG.  At first, Drip seemed to be fine, but I was still building out my mod list, and it suddenly stopped working.  It was complaining about SOS not being installed and telling me that I needed to fix my plugins.  While trying to fix that, I discovered this mod, and rejoiced that all my problems had been solved!  I wasn't sure if this mod needed the Old Drip or not (the mod download page doesn't say either way), so I only disabled Old Drip in MO2 and installed and enabled Drip NG.  Ran a test boot, everything was working, no errors, so, assuming that Drip NG doesn't need anything from Old Drip, I uninstalled it from MO2, and went on modding.  Imagine my surprise on my next test boot when I started getting the same old "No SOS, please fix plugins" error from Drip NG!  Much testing later, and I found a bug that I didn't even know was possible.  So long as I have Old Drip installed, and I have activated it at least once, Drip NG will work (Old Drip is deactivated), but if Old Drip isn't installed, or hasn't been activated at least once, Drip NG won't work...

        So, what files from Old Drip does Drip NG need to work on my setup?!?  And how is it using them when Old Drip is disabled in MO2?!?  Should I have Old Drip installed and activated or not?!  Please clarify this in the requirements on the Mod download page, as I'm sure many others also wonder if Old Drip is needed or not!

 

 

        Update:  Still randomly getting that same "No SOS, please fix plugins" error from Drip NG when installing new mods...  Disabling them, running the game once, then re-enabling them seems to fix it, sometimes?!?  If not, then enabling then disabling Old Drip does...  Oh, and leaving Old Drip Enabled also gives the same error message.  It must be enabled then disabled.  What in the world is going on here???

 

Your save is likely borked. Once installed, the original mod is notoriously difficult to remove.

 

DWA-NG does not require anything from the original mod, it is a complete package and safer to remove/easy to disable. Use it on a new save without the old mod.

 

See this post on the first page: https://www.loverslab.com/topic/238176-dripping-when-aroused-ng/#findComment-6827569

 

Also, this guy was able to successfully remove the old mod: https://www.loverslab.com/topic/238176-dripping-when-aroused-ng/#findComment-6828423

 

Edited by stnfnk
Posted (edited)
5 hours ago, stnfnk said:

 

Your save is likely borked. Once installed, the original mod is notoriously difficult to remove.

 

DWA-NG does not require anything from the original mod, it is a complete package and safer to remove/easy to disable. Use it on a new save without the old mod.

  I had already thought of that, and so created a new game, but the bug showed up anyways!  Sorry, forgot to mention that...🥲

 

So, does that mean that I'm just gonna have to nuke my entire mod list and start over?!?  I guess that's not to bad, since I just nuked it last week...

Edited by 700 Tnega Terces
Posted
16 minutes ago, 700 Tnega Terces said:

  I had already thought of that, and so created a new game, but the bug showed up anyways!  Sorry, forgot to mention that...🥲

 

So, does that mean that I'm just gonna have to nuke my entire mod list and start over?!?  I guess that's not to bad, since I just nuked it last week...

 

Check my edit above, @modball was able to remove the old mod and get the new one running on an old save.

 

If it bugs out a new game, you probably still have files from the old mod interfering. Get a new game going with no DW at all and no bug, then install DWA-NG.

Posted
5 hours ago, stnfnk said:

 

Check my edit above, @modball was able to remove the old mod and get the new one running on an old save.

 

If it bugs out a new game, you probably still have files from the old mod interfering. Get a new game going with no DW at all and no bug, then install DWA-NG.

 

Okay, so I deleted both Old Drip and Drip NG, made a new save, then re-installed New Drip, and now it seems to be working!  So, yeah, delete Old Drip before installing Drip NG, or it will infect it!

  • 5 weeks later...
Posted (edited)

Hi there, it seems some scripts are still using the ESP address to get the quests from the plugin.

Like DW_SOS uses:

 

DW_CORE CORE = Game.GetFormFromFile(0xD62, "DW.esp") as DW_CORE

 

Instead of 862.

 

It might be better to put them in properties to avoid such errors.

Edited by TrollAutokill
Posted (edited)
4 hours ago, TrollAutokill said:

Hi there, it seems some scripts are still using the ESP address to get the quests from the plugin.

Like DW_SOS uses:

 

DW_CORE CORE = Game.GetFormFromFile(0xD62, "DW.esp") as DW_CORE

 

Instead of 862.

 

It might be better to put them in properties to avoid such errors.

 

Its 0x862 in DW_SOS in version 1.0.8, just checked the current download. Are there other ones?

 

Edit: I looked and I think all the references are 862 now. Do you have something overwriting with an old script?

Edited by stnfnk
Posted (edited)
3 hours ago, stnfnk said:

 

Its 0x862 in DW_SOS in version 1.0.8, just checked the current download. Are there other ones?

 

Edit: I looked and I think all the references are 862 now. Do you have something overwriting with an old script?

I am pretty sure I downloaded it a few weeks ago. I also see that DW_SOS is pretty much empty in my version. Is that a sign it's an older one?

 

I'll check again.

 

EDIT: Downloaded again and it's as you said, perfect. Sorry for the inconvenience, I must have installed an older version.

 

 

Edited by TrollAutokill
Posted
2 hours ago, TrollAutokill said:

I am pretty sure I downloaded it a few weeks ago. I also see that DW_SOS is pretty much empty in my version. Is that a sign it's an older one?

 

I'll check again.

 

EDIT: Downloaded again and it's as you said, perfect. Sorry for the inconvenience, I must have installed an older version.

 

 

 

No worries, I love when its an easy fix.

 

Love your work too, thanks for stopping by TAK!

Posted (edited)
34 minutes ago, stnfnk said:

 

No worries, I love when its an easy fix.

 

Love your work too, thanks for stopping by TAK!

By the way it was really easy to get DW to work with DOM, I just had to set the SLA no update faction and update the arousal faction in DOM. Very nice mod, indeed.

Edited by TrollAutokill
Posted
1 hour ago, TrollAutokill said:

By the way it was really easy to get DW to work with DOM, I just had to set the SLA no update faction and update the arousal faction in DOM. Very nice mod, indeed.

 

Sweet.

 

Is that SLA specific? I use OSL Aroused for OStim compatibility. Will have to look if it respects the no update faction.

Posted (edited)
5 minutes ago, stnfnk said:

 

Sweet.

 

Is that SLA specific? I use OSL Aroused for OStim compatibility. Will have to look if it respects the no update faction.

SLA has 2 control factions: blocked (no arousal) and no update (let other mods handle arousal).

Edited by TrollAutokill
Posted
4 minutes ago, TrollAutokill said:

SLA has 2 factions: blocked (no arousal) and no update (let other mods handle arousal).

 

OSL has a ton of factions, including sla_arousal, sla_exposure, sla_arousal_blocked, and sla_arousal_locked. There are some slave factions in here too with SLAX prefixes.

Posted (edited)
8 hours ago, stnfnk said:

 

OSL has a ton of factions, including sla_arousal, sla_exposure, sla_arousal_blocked, and sla_arousal_locked. There are some slave factions in here too with SLAX prefixes.

Locked is the one I call no update. I will check for OSL in DOM when SLA is out. Thanks.

 

EDIT: So OSL Aroused comes with its own SexLabAroused.esm and is just a drop replacement for SLA. Easy fix.

Edited by TrollAutokill
Posted
14 hours ago, stnfnk said:

 

Its 0x862 in DW_SOS in version 1.0.8, just checked the current download. Are there other ones?

 

Edit: I looked and I think all the references are 862 now. Do you have something overwriting with an old script?

 

I understood what was the problem:

 - First install was just CORE, no SOS, so maybe the D62 is intentional and that explains the empty DW_SOS.

 - Second install I selected "SOS Full" and it's better.

 

Now, the second install still had something weird:  the SL property is not set in DW_SOS virtual machine. That's an easy fix with SSEEdit.

Posted (edited)
3 hours ago, TrollAutokill said:

 

I understood what was the problem:

 - First install was just CORE, no SOS, so maybe the D62 is intentional and that explains the empty DW_SOS.

 - Second install I selected "SOS Full" and it's better.

 

Now, the second install still had something weird:  the SL property is not set in DW_SOS virtual machine. That's an easy fix with SSEEdit.

 

I found it. It's a placeholder script that gets installed if you don't choose SOS/TNG during fomod installation.

 

I think I found the missing property too. Will publish a version with both fixes.

 

Yeah, OSL is a (supposedly) drop-in replacement and tracks both OStim and SL stuff. I've heard some people complain about compatibility at times but I've had a good experience with it so far.

Edited by stnfnk
Posted (edited)

I wanted to do a little investigation on my own to figure out how to properly align the milk leak effect. Bumped into this notification in Outfit Studio.

 

The milk leak effect does indeed work in-game. But I'm curious if the Nifs aren't actually optimized and, if so, whether optimizing them would help us toward fixing the alignment at all.

 

Also, looking into DW_MilkLeakL.nif, I see that it's meant to attach to the NPC L Breast01 bone. However, using the below body as a reference, wouldn't it be better to align the effect to NPC L Breast 02 since it's closer to the nipple? Ofc I'm saying this with no idea how it actually works. But the placement of the node does seem close to where the effect leaks, and I see no actual mesh to morph or transform within the MilkLeak nifs.

Spoiler

 

 

Edited by Nuascura
Removed Attachments

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...