• Hi Guest!

    We are extremely excited to announce the release of our first Beta1.1 and the first release of our Public AddonKit!
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. For access to the Public AddonKit you must be a Creator tier member. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
  • Hi Guest!

    VaM2 Resource Categories have now been added to the Hub! For information on posting VaM2 resources and details about VaM2 related changes to our Community Forums, please see our official announcement here.
Nipple & Pubic Hair Clipping Eliminator

Plugins + Scripts Nipple & Pubic Hair Clipping Eliminator

Download [<1 MB]
I can corroborate what the other person is saying-- this has a very heavy impact on my framerate when active.
Hi, would you mind to test test the newest release in terms of performance - I changed a lot internally with the newest version.
Ideally, compare the script times from within the performance monitor with and without the plugin active under identical conditions.
 
Hi, would you mind to test test the newest release in terms of performance - I changed a lot internally with the newest version.
Ideally, compare the script times from within the performance monitor with and without the plugin active under identical conditions.
Yeah I'll give it a shot when I have the time. I do have a ton of clothing and morphs so I'm expecting the performance will be improved if that was the issue
 
OK, thanks, must be a large list of either morphs and/or clothing items then. I will try to find whats bottleneck, even though I dont experience this (as my AddonPackages is just 7 GB with little morphs). It is however well known that having a lot of morphs just present in AddonPackages will slow down VaM drastically. But thats another point I guess.
Yeah my AddonPackages is a total mess (lots of addons that had tons of random dependencies)
 
I have found where this will set the pubic hair width to zero with clothing on (as it should), but it does not restore the width with clothing off. Instead, width stays at 0. So far, I have only noticed this with MonsterShinkai's recently released pubic hairs, and with Metix's BetterPubes . Most other pubic hairs work as intended, restoring the width.

Edit: I stand corrected, the pubic hair stays at width of 0 after clothing is off with any pubic hair. This occurs after I exit VaM and then relaunch it. It works as expected, restoring width, only when I remain in that session after manually changing the width. If I exit and then come back, width is back at 0 again.
 
Last edited:
I have found where this will set the pubic hair width to zero with clothing on (as it should), but it does not restore the width with clothing off. Instead, width stays at 0. So far, I have only noticed this with MonsterShinkai's recently released pubic hairs, and with Metix's BetterPubes . Most other pubic hairs work as intended, restoring the width.

Edit: I stand corrected, the pubic hair stays at width of 0 after clothing is off with any pubic hair. This occurs after I exit VaM and then relaunch it. It works as expected, restoring width, only when I remain in that session after manually changing the width. If I exit and then come back, width is back at 0 again.
Hi Troho, thanks for your report. I will check this and fix if I can reproduce it. See you in 2026!
 
There seem to be some minor issues. When I put underwear on the character and save it as a new appearance preset, then import this appearance preset into the same scene or another scene, and then remove the underwear, the pubic hair no longer appears. I'm not sure if it's a problem with my operation.
 
There seem to be some minor issues. When I put underwear on the character and save it as a new appearance preset, then import this appearance preset into the same scene or another scene, and then remove the underwear, the pubic hair no longer appears. I'm not sure if it's a problem with my operation.
Sounds like the same problem I stated above, where the width stays at 0 instead of reverting back to the proper width. Is that the case?
 
There seem to be some minor issues. When I put underwear on the character and save it as a new appearance preset, then import this appearance preset into the same scene or another scene, and then remove the underwear, the pubic hair no longer appears. I'm not sure if it's a problem with my operation.
Hi Zilla, thank you, I can reproduce this. Its pretty straightforward - you save the preset with 0 hair width and then load this on a new atom. The plugin cannot "know" the non hidden parameters. My workaround in the context of saving and loading scenes (where we have the same problem, if you save a scene with underwear on) is to briefly restore pubic hair width just before saving, even though the underwear is on. I will try to implement this routine for appearance saving too. But that's not easy. For the time being, just don't save presets with the routine on!
 
Last edited:
RunRudolf updated Nipple & Pubic Hair Clipping Eliminator with a new update entry:

Improved Appearance Preset Saving (Clothes On)

View attachment 554966
Credits: 'Nadjia' by HotlineVam with 'swimwear05' by maru01, 'Ellie' by JackyCracky with 'Sbloomers02' by maru01, 'Light_Rig_05' by n00rp

Bugfix
  • Adding a 'hack' to allow saving of appearance presets with pubic hair not zero even with clothes on. Just before the .vap is created, the pubic hair will be restored to the original width (based on UI button mouse over detection). Thanks @Troho &...

Read the rest of this update entry...
 
Thanks for testing and reporting! I am aware that performance has not been fully optimised yet, but my short tests did not show that much impact. The following screenshot shows a one girl setup with 3 clothing pieces. I have the physics patch installed and not many clothing items in my .var library. In contrary to your observation, I find that the plugin has no measurable, negative impact on the overall performance (right column is averaged values, I compare the 'Script' value):

View attachment 552355

- Do you have a very large .var collection with lots of clothings? Thats something I did not (and cannot) test, and the plugin goes through all clothing items periodically.
- Did you measure fps with closed UI in Play mode? That makes a big difference apparently (but should affect with and without plugin similarly).
I have only 24 VARs in AddonPackages so I think that is small enough.
I tried in Play mode with UI closed but there was no FPS difference.
It is strangely affecting the Physics category pretty hard.
You mentioned a 'physics patch' maybe I am missing. (What physics patch?)
I am using VAM 1.22.0.12 and plugin 8.var
 

Attachments

  • combined.png
    combined.png
    30.4 KB · Views: 0
I have only 24 VARs in AddonPackages so I think that is small enough.
I tried in Play mode with UI closed but there was no FPS difference.
It is strangely affecting the Physics category pretty hard.
You mentioned a 'physics patch' maybe I am missing. (What physics patch?)
I am using VAM 1.22.0.12 and plugin 8.var
Thank you for collecting and sharing this data!
Does "hide neither", " hide xy" mean you activated/deactivated this function?
In any case, you have to reset averages before measuring each case. The individual peaks in the left column are not meaningful, even though peaks can be seen sometimes. In case you did reset, physics are exactly the same in all cases (0.03 s), which is very low. Moreover, the group "physics" should be influenced by PhysX only, this is not related to the code of my plugin. I watch "script". At least that's what I learned.
 
Thank you for collecting and sharing this data!
Does "hide neither", " hide xy" mean you activated/deactivated this function?
In any case, you have to reset averages before measuring each case. The individual peaks in the left column are not meaningful, even though peaks can be seen sometimes. In case you did reset, physics are exactly the same in all cases (0.03 s), which is very low. Moreover, the group "physics" should be influenced by PhysX only, this is not related to the code of my plugin. I watch "script". At least that's what I learned.
Thanks for being so attentive :) (y)

I looked into this more and discovered 2.5 interesting pieces of information:
1) Changing User Preferences -> Physics Update Cap from 3 to 1 tripled my FPS :rolleyes: (screenshot attached)
2) Inserting microsecond measurements into FrameUpdate revealed that function IsDetachedSimClothing is quite slow on my computer taking ~30ms for just two calls (screenshot attached)
2.5) It appears that FrameUpdate is part of category 'Physics' not 'Script' in Performance Monitor numbers 🤷‍♂️

Maybe there is an issue with my library size since you are not seeing performance penalties anywhere close to mine. I use the BrowserAssist session plugin to "offload" (and manage) 300GB of AddonPackages which should be invisible to VaM. Maybe I am mistaken in how that works and there is still some slowness in processing clothing.
 

Attachments

  • preferencesUpdateCap.png
    preferencesUpdateCap.png
    190.3 KB · Views: 0
  • combined-PhysicsUpdateCap1.png
    combined-PhysicsUpdateCap1.png
    24.6 KB · Views: 0
  • elapsedTimeFrameUpdate.png
    elapsedTimeFrameUpdate.png
    513.7 KB · Views: 0
Thanks for being so attentive :) (y)

I looked into this more and discovered 2.5 interesting pieces of information:
1) Changing User Preferences -> Physics Update Cap from 3 to 1 tripled my FPS :rolleyes: (screenshot attached)
2) Inserting microsecond measurements into FrameUpdate revealed that function IsDetachedSimClothing is quite slow on my computer taking ~30ms for just two calls (screenshot attached)
2.5) It appears that FrameUpdate is part of category 'Physics' not 'Script' in Performance Monitor numbers 🤷‍♂️

Maybe there is an issue with my library size since you are not seeing performance penalties anywhere close to mine. I use the BrowserAssist session plugin to "offload" (and manage) 300GB of AddonPackages which should be invisible to VaM. Maybe I am mistaken in how that works and there is still some slowness in processing clothing.
Very cool, thank you for this input! It seems worth to try to optimize the IsDetachedSimClothing function. I will see what I can do. Maybe move stuff from FixedUpdate() to Update() or Coroutines. You are right, FixedUpdate() is done before each fixed time step and counted there.

Its very strange that LOWERING the update cap increased your fps - it should not have an effect on fps at all I think. It should improve physics accuracy if fps drops below physics rate if INCREASED. But the setting with auto and update cap are really trial and error, if you cannot fix fps to 90 or 60 and physics rate to the same.

I will keep you posted and let you know if there is something to test, if you want.
 
Last edited:
I neglected to answer your question... 'hide neither' means both 'enable' checkboxes (nipples and pubes) in your settings menu were unchecked, 'hide nipples' means only nipples 'enable' checkbox in settings was enabled, etc... i should just screenshot instead of trying to speak. :D

One last bit of log spam... I added some logs inside IsDetachedSimClothing and it looks like GetStorableIDs takes 10ms to return a sorted copy of 421 strings and then iterates that list to check all elements taking 6ms... which happens twice in my test because both nipples and pubes were enabled resulting in 32ms (plus 6ms VaM physics) of processing time per frame if Physics Update Cap = 1, or 3x that if Physics Update Cap = 3 (96ms for FixedUpdate + 18ms for VaM physics). I could be wrong but the numbers seem to match what I saw in various experiments. I don't think it is my VAR library size anymore. Maybe the characters I tried are complicated and my Physics Update Cap was too high for my old-ass computer.

1767603959582.png


I'm going to stop thinking about this now. :unsure: I don't think there is much else I can do. 🙃:LOL:
 
Last edited:
Hello, author~

I was genuinely impressed by the design of this plugin. It finally achieves something I wanted back when I was playing Illusion games—the ability to hide nipples and pubic hair. It’s really well done.
However, I’ve noticed that when this plugin is enabled, my FPS drops to around 30–35. Once I disable it, the FPS immediately returns to normal.

Thank you in advance for your time and response.
 
Hello, author~

I was genuinely impressed by the design of this plugin. It finally achieves something I wanted back when I was playing Illusion games—the ability to hide nipples and pubic hair. It’s really well done.
However, I’ve noticed that when this plugin is enabled, my FPS drops to around 30–35. Once I disable it, the FPS immediately returns to normal.

Thank you in advance for your time and response.
Hi there, and thanks for your kind feedback! Its really the new means of using AI to do stuff beyond personal horizons - its good to know however what you want to do and how, but a lot of the work is done by AI.
I am aware of the performance issue and, together with yesferatu, could pin it down to one small function (the one for sim detached clothing state). This alone takes up to 30 ms, which is crazy.

I will now do more caching, and move some things to Update(). It already works, and I will release the new version shortly, just needs some testing and polishing!
 
RunRudolf updated Nipple & Pubic Hair Clipping Eliminator with a new update entry:

Performance Upgrade

View attachment 555655
Credits: 'Hermine' by Vecterror, 'Brian' by sigixxx
  • Huge performance upgrade by moving all main routines from FixedUpdate() to Update(), improving load distribution and caching the (expensive) sim detached state detection. Thanks @yesferatu for the valuable inputs and testing!
  • Please let me know how the plugin performs on your and particularly older systems. I never experienced dramatic...

Read the rest of this update entry...
 
I will try this. Thank you! Though... the fundamental problem is not solved: it continuously spends a lot of time to detect a momentary problem.
 
I will try this. Thank you! Though... the fundamental problem is not solved: it continuously spends a lot of time to detect a momentary problem.
Thank you, I am grateful for an update on whether it changed for good or how bad it still is.
There is certainly more room for improvement, as I think I can limit cache refreshes to active clothing items only. This would speed it up further I guess.
 
RunRudolf updated Nipple & Pubic Hair Clipping Eliminator with a new update entry:

More Performance Improvements

View attachment 556218
Credits: 'Nadjia' by HotlineVam, 'Hermine' by Vecterror, 'Ellie' by JackyCracky, 'Tyler' by PetaZwerga, 'Campfire' fire by Norm, 'Postmagic' by MAcGruber
  • More performance improvements: Now only considering active clothing items for several checks and updates.
  • The script times with version 10 active are only 0.06 ms longer than without the plugin (1 male with 8 clothing items). Version 8 was 0.9 ms slower in Physics time (because...

Read the rest of this update entry...
 

Similar threads

Back
Top Bottom