• Happy Holidays Guest!

    We want to announce that we will be working at reduced staffing for the holidays. Specifically Monday the 23rd until Jan 2nd.

    This will affect approval queue times and responses to support tickets. Please adjust your plans accordingly and enjoy yourselves this holiday season!

  • Hi Guest!

    Please be aware that we have released a critical security patch for VaM. We strongly recommend updating to version 1.22.0.7 using the VaM_Updater found in your installation folder.

    Details about the security patch can be found here.
Realistic Foreskin & Erection Simulation (Plugins)

Plugins Realistic Foreskin & Erection Simulation (Plugins)

I haven't managed to add video through site.(Got some errors) I've uploated it on mega instead. https://mega.nz/file/iy5EjKJY#DLqcYcnXNgwoLMrEkySN9DcSDmmALfoIufD1jG-4LzM
P.S. I've mostly skipped process of loading scene coz it takes about 3 minutes.
P.P.S. And i've added it to clear female model without penis to show the plugin definetly can recognize model(and it's lack of penis) after lauching.
P.P.S. I hope you'll fix it soon coz it's best plugin for penis control.

I haven't managed to add video through site.(Got some errors) I've uploated it on mega instead. https://mega.nz/file/iy5EjKJY#DLqcYcnXNgwoLMrEkySN9DcSDmmALfoIufD1jG-4LzM
P.S. I've mostly skipped process of loading scene coz it takes about 3 minutes.
P.P.S. And i've added it to clear female model without penis to show the plugin definetly can recognize model(and it's lack of penis) after lauching.
P.P.S. I hope you'll fix it soon coz it's best plugin for penis control.
Thank you! I am investigatimg it, up to now with no success unfortunately. Its really strange, that we get or do not get errors in seemingly the same situation. I think I will try on a clean fresh installation next and see whether it throws any errors. Please have some more patience...Thanks.
 
Hi Josososo
thanks a lot for your video! Could you please check, whether you have the following morph package downloaded in your VAM repository:
- WeebU My_morphs: https://hub.virtamate.com/resources/morphs-repack.2609/
In the male morph list, its called "Penis Height".
This additional morph has been introduced in version 27 on Obtober 4th and is not part of VAM's standard morphs. That would match with the observation that version 26 still works, but from 27 on does not.
Please let me know! Thanks.
“WeebU My_morphs” was downloaded.
It can be seen at 31 seconds into the video. The image is a cutout of the video.
 

Attachments

  • a.jpg
    a.jpg
    471.7 KB · Views: 0
Tested but now I have this three plugins are disable. The Erection null error is gone but I have those three plugins installed already. Is it suppose to do, correct me if I am wrong or setup it up incorrectly because I do have those three plugin install already.
1729106957986.png
 
Tested but now I have this three plugins are disable. The Erection null error is gone but I have those three plugins installed already. Is it suppose to do, correct me if I am wrong or setup it up incorrectly because I do have those three plugin install already. View attachment 420181
Not sure but in case you did not know: You have to actually load these plugins, not just download them. Your plugin screen should look like this if you want full functionality.
Its best to use the enclosed plugin preset to get there. Use the one with "interactive", the other seems broken.

1729116058242.png
 
I have a problem. I've added Realistic Foreskin and relistic erection to the guy. And when i move girls close to dick, her mouth starts deforming. It's like 5 cm between her lips and dick tip, but her lips already deformes. I guess collision problems took place here.
 
I have a problem. I've added Realistic Foreskin and relistic erection to the guy. And when i move girls close to dick, her mouth starts deforming. It's like 5 cm between her lips and dick tip, but her lips already deformes. I guess collision problems took place here.
Did you also add Awas AutoJuice? What happens if you remove this?
 
What is "Awas AutoJuice"? Plugin? No i haven't use it. Only plugin that both girl and dude have - Embody.
Or it's some config from your plugins?
Yes, AutoJuice it a fluid plugin that can interact with my plugin and uses colliders to achieve the cum spray. My plugins however do not change colliders nor do they interact with any morphs of the mouth of other atoms. Could you please a video with step by step how to reproduce the peoblem? I have never seen or heard about similar problems.
PS: Just tested on my side an did not experience any strange mouth morphs, except opening if close enough (which is intended).
 
Last edited:
Regarding your request: Could you please document how this would be used? I cannot see the difference/advantage of using these Joint Drive X angles over the existing sliders yet. Maybe include a screenshot of how it sould look in the end.
This might be purely aesthetic preference. The existing curve up/down slider seems to mostly happen near the tip, while having mid Joint Drive X incorporates the middle a bit more. Having both active together doesn't seem bad either, but I usually end up increasing mid Joint Drive X for erect, then having to return it for flaccid.

I mostly wanted to say thanks a lot for the update. The new version fixed all the issues I was having.
 
This might be purely aesthetic preference. The existing curve up/down slider seems to mostly happen near the tip, while having mid Joint Drive X incorporates the middle a bit more. Having both active together doesn't seem bad either, but I usually end up increasing mid Joint Drive X for erect, then having to return it for flaccid.

I mostly wanted to say thanks a lot for the update. The new version fixed all the issues I was having.
Thanks for reporting back, that helps a lot. And for your kind words on the recent update. I am glad that these errors seem to have stopped. There is more stuff coming in the near future.
 
RunRudolf updated Realistic Foreskin & Erection Simulation (Plugins) with a new update entry:

Fully Customizable Orgasm Sequences

- Orgasm is now configurable in terms of timing of up to four phases, fluid spray sequences and properties, as well as cum cloth type. Upon loading of the plugin, a standard sequence is loaded. Click on 'Customize Orgasm Sequence' to get to the new UI where all the parameters can be set and saved. Check the triggers in the main UI at 'Select Orgasm Trigger'.
View attachment 421106 View attachment 421107

- If you create a great sequence...

Read the rest of this update entry...
 
RunRudolf updated Realistic Foreskin & Erection Simulation (Plugins) with a new update entry:

Bugfixing

- Fixing a bug that prevented from saving fluid101 spray sequences. You can now compose your own orgasms, involving four individually configurable spray and jizz sequences with differing fluid properties and durations. Fluid sequences will now be properly saved.
- More flexibility in defining orgasm sequences: Added a no (cloth) jizz option (just fluids)
- Improved standard sequence with fluid sprays, jizz jets and synced throbbing
- Bugfix: First orgasm sequence not playing

Read the rest of this update entry...
 
Has anyone experience the distorted morph of the male genital when climax? testicle start spinning around and penis randomly increase and decrease?
I left the climax setting to the default one, didn't experience this in version 35.
 
Has anyone experience the distorted morph of the male genital when climax? testicle start spinning around and penis randomly increase and decrease?
I left the climax setting to the default one, didn't experience this in version 35.
I will have a look, but did not get any other similar feedback so far. Did you experience this in a clean default scene?

Add: Cannot reproduce the mentioned problem. Please provide some details about the circumstances, under which this happens.
 
Last edited:
Hi. Thanks for the plugin, it saves a ton of time.

I am having trouble running the last several versions. I'm not sure what the issue is. I believe I have all morphs. I use this on a female person with Stopper AltFuta 28. I did try on a fresh scene, but it happens there too.
The erection script spams this message:

!> RealisticErection.FixedUpdate: System.NullReferenceException: Object reference not set to an instance of an object
at RunRudolf.RealisticErection.GetIntensity () [0x00000] in <filename unknown>:0
at RunRudolf.RealisticErection.FixedUpdate () [0x00000] in <filename unknown>:0

I also have a small feature request.
The Joint Drive X Angle on penisMidControl/TipControl is something I change often, probably maximum up to +30. I know there is a curve up/down slider already included but it behaves a bit different. Having access to those in the plugin would be nice, but I understand if it's not something you plan to include.

Thanks

Hey, sorry to reopen this can of worms but I am unfortunately encountering the same error even with a minimalist setup (meaning no new .vars in Addonpackage folder other than the base VaM ones and those required by your Demo Scenes Dependencies)

this is the exact the error message:
Code:
!> RealisticForeskin.FixedUpdate: System.NullReferenceException: Object reference not set to an instance of an object
  at RunRudolf.RealisticForeskin.FixedUpdate () [0x00000] in <filename unknown>:0

which repeats infinitely every second until I disable "plugin#0_RunRudolf.RealisticForeskin"

Made sure to download the Morphs you suggested in the discussion, even loaded a separated scene to individually load every required plugins, even though I suppose your own demo scenes are already setup accordingly from the get go, and yet this error still persists.
 
Yup. I second that.

I wanted to finally test it and use it in our next collab. It seems compromised, the thing spams the error log all the time.
 
Sorry to bring this up again. After the plugin was working for me I noticed that performance went down a lot.
I'm using the newest version of foreskin script, but I went back to version 22 of erection script which doesn't have much performance impact.

Just a quick comparison for a few seconds of a dance scene:
25-40 fps new version
69-82 fps version 22
 
RunRudolf updated Realistic Foreskin & Erection Simulation (Plugins) with a new update entry:

New Clean UI & More Penis Decals

- Added five different color tones and normal map setups for penis decals, and a new switch to activate them with one click. Thanks to kemenate and bigscar for their decals and normal maps (see links in the credits). The presets can be edited in DecalMaker once loaded.
View attachment 437452
- New clean and structured UI with help for both plugins. The new UI consists of a main menu and contents are mostly on one page if possible.
[ATTACH type="full"...

Read the rest of this update entry...
 
Thank you for fixing (and not answering ;))

Several things:
  • Tabbing (general/erection/...), triggers silent critical errors in the console (erection sub plugin) - Use Acid's Dev tools forward logs to check it out
  • Tabbing (general/foreskin/...), triggers silent critical errors in the console (foreskin sub plugin) - Use Acid's Dev tools forward logs to check it out
  • Tabbing clears orgasm fields for the fluid (I'm not using it, but people might). This might be due to the silent crash above.
  • Loading decal presets crashes (from your plugin preset setup)
  • Loading decal presets crashes (from a clean manual plugin added to the male)
    • more or less, decal maker does not work

Side things (questions/suggestions, not mandatory you can ignore me if you have other things to do or it does not fit your design):
  • Could you make the log messages silent or at least only in edit mode? The choice of the creator NOT to use fluid/auto juice/decal marker does not concern the final user (the player) and creates more questions than it solves for anyone that is not a creator.
  • Would you consider implementing a similar thing as Divining Rod? It would be a blast to reduce the plugin footprint, and it would reduce the dependency count slightly to have all the algorithm handled by one plugin. Also, the plugin is not updated anymore, so maybe you'd have ideas to make it even better : )
  • Considering adding a "disable orgasm phase" to save on lookups... I want to use and configure the fluid myself and don't want the plugin to override it. I have no way to do that atm.
 
Last edited:
Thank you for fixing (and not answering ;))

Several things:
  • Tabbing (general/erection/...), triggers silent critical errors in the console (erection sub plugin) - Use Acid's Dev tools forward logs to check it out
  • Tabbing (general/foreskin/...), triggers silent critical errors in the console (foreskin sub plugin) - Use Acid's Dev tools forward logs to check it out
  • Tabbing clears orgasm fields for the fluid (I'm not using it, but people might). This might be due to the silent crash above.
  • Loading decal presets crashes (from your plugin preset setup)
  • Loading decal presets crashes (from a clean manual plugin added to the male)
    • more or less, decal maker does not work

Side things (questions/suggestions, not mandatory you can ignore me if you have other things to do or it does not fit your design):
  • Could you make the log messages silent or at least only in edit mode? The choice of the creator NOT to use fluid/auto juice/decal marker does not concern the final user (the player) and creates more questions than it solves for anyone that is not a creator.
  • Would you consider implementing a similar thing as Divining Rod? It would be a blast to reduce the plugin footprint, and it would reduce the dependency count slightly to have all the algorithm handled by one plugin. Also, the plugin is not updated anymore, so maybe you'd have ideas to make it even better : )
  • Considering adding a "disable orgasm phase" to save on lookups... I want to use and configure the fluid myself and don't want the plugin to override it. I have no way to do that atm.
Wow, that's quite a list...Thank you for testing and putting this together, I will have to look into it.
Sorry for not responding: I seem to miss new discussions because I do not get notifications althouth I am "watching".
 
Thank you for fixing (and not answering ;))

Several things:
  • Tabbing (general/erection/...), triggers silent critical errors in the console (erection sub plugin) - Use Acid's Dev tools forward logs to check it out
  • Tabbing (general/foreskin/...), triggers silent critical errors in the console (foreskin sub plugin) - Use Acid's Dev tools forward logs to check it out
  • Tabbing clears orgasm fields for the fluid (I'm not using it, but people might). This might be due to the silent crash above.
  • Loading decal presets crashes (from your plugin preset setup)
  • Loading decal presets crashes (from a clean manual plugin added to the male)
    • more or less, decal maker does not work

Side things (questions/suggestions, not mandatory you can ignore me if you have other things to do or it does not fit your design):
  • Could you make the log messages silent or at least only in edit mode? The choice of the creator NOT to use fluid/auto juice/decal marker does not concern the final user (the player) and creates more questions than it solves for anyone that is not a creator.
  • Would you consider implementing a similar thing as Divining Rod? It would be a blast to reduce the plugin footprint, and it would reduce the dependency count slightly to have all the algorithm handled by one plugin. Also, the plugin is not updated anymore, so maybe you'd have ideas to make it even better : )
  • Considering adding a "disable orgasm phase" to save on lookups... I want to use and configure the fluid myself and don't want the plugin to override it. I have no way to do that atm.
@hazmhox: The one with Decal Maker is a bit strange, since I tested the hub version on a clean character too and it worked. But I will anyways expand the decals section with the next update (I will add more decal textures - working on them now - to get more variety and a flexible combination system including normals) and also move the entire decal stuff to the foreskin plugin (where it makes more sense).
Out of interest: Do you have a full step by step debug environment setup to catch those nasty missing references, or how do you do your bugfixing?
 
Sorry for not responding: I seem to miss new discussions because I do not get notifications althouth I am "watching".

Yeah I have that too, I've reported it to Ash.


Out of interest: Do you have a full step by step debug environment setup to catch those nasty missing references, or how do you do your bugfixing?

Nothing crazy:
  • 1 working/playing VAM (everything is in there)
  • 1 clean VAM (only required vars to test new content, cleaned over time)
  • HZMDemos which includes all the demo scenes for my content
  • Acid's dev tools + forward log always loaded
From there after I pack a .var
  • Full test of the asset/plugin in my working VAM. One test clean (manually use of content or plugin). One test with existing scenes or demos if there are some. Test of most critical features ( preset systems, save system, multi-dependencies interactions etc )
  • Full test of the asset/plugin in my clean VAM. Same process.
I also tend to test a "download" process in the clean VAM without installing manually. I suspect the error reported above I had (the fixedupdate error) was due to you forgetting to mention a required dependency, which is fixed in the new one and tells you it's required.

I'd ensure that a content used in the plugin is always considered a hard dependency (not soft/sub-dep) to avoid that sort of stuff. Even with the background I have with VAM, I did not realize I was missing a sub-dependency. So imagine a noob : )

Btw, critical errors "you're missing this, it's mandatory to have it"... use SuperController.singleton.Alert if the user is in edit mode. It is critical, the plugin will not work... so it's not really a problem to popup a big window instead of a short log that disappears before you could even read the full message.
 
Yeah I have that too, I've reported it to Ash.




Nothing crazy:
  • 1 working/playing VAM (everything is in there)
  • 1 clean VAM (only required vars to test new content, cleaned over time)
  • HZMDemos which includes all the demo scenes for my content
  • Acid's dev tools + forward log always loaded
From there after I pack a .var
  • Full test of the asset/plugin in my working VAM. One test clean (manually use of content or plugin). One test with existing scenes or demos if there are some. Test of most critical features ( preset systems, save system, multi-dependencies interactions etc )
  • Full test of the asset/plugin in my clean VAM. Same process.
I also tend to test a "download" process in the clean VAM without installing manually. I suspect the error reported above I had (the fixedupdate error) was due to you forgetting to mention a required dependency, which is fixed in the new one and tells you it's required.

I'd ensure that a content used in the plugin is always considered a hard dependency (not soft/sub-dep) to avoid that sort of stuff. Even with the background I have with VAM, I did not realize I was missing a sub-dependency. So imagine a noob : )

Btw, critical errors "you're missing this, it's mandatory to have it"... use SuperController.singleton.Alert if the user is in edit mode. It is critical, the plugin will not work... so it's not really a problem to popup a big window instead of a short log that disappears before you could even read the full message.
Thanks, that is helpful for me. I debug and release essentially the same way as you, I also keep a clean VAM to test for missing references bugs and also try both the packaged .var and the downloaded .var usually.

How do I ensure some morphs used by the plugin (out of a morph repack) are considered a hard dependency? Do I need to add them manually to the dependencies file? I was not aware of this (still being quite a noob myself :)
Yeah I have that too, I've reported it to Ash.




Nothing crazy:
  • 1 working/playing VAM (everything is in there)
  • 1 clean VAM (only required vars to test new content, cleaned over time)
  • HZMDemos which includes all the demo scenes for my content
  • Acid's dev tools + forward log always loaded
From there after I pack a .var
  • Full test of the asset/plugin in my working VAM. One test clean (manually use of content or plugin). One test with existing scenes or demos if there are some. Test of most critical features ( preset systems, save system, multi-dependencies interactions etc )
  • Full test of the asset/plugin in my clean VAM. Same process.
I also tend to test a "download" process in the clean VAM without installing manually. I suspect the error reported above I had (the fixedupdate error) was due to you forgetting to mention a required dependency, which is fixed in the new one and tells you it's required.

I'd ensure that a content used in the plugin is always considered a hard dependency (not soft/sub-dep) to avoid that sort of stuff. Even with the background I have with VAM, I did not realize I was missing a sub-dependency. So imagine a noob : )

Btw, critical errors "you're missing this, it's mandatory to have it"... use SuperController.singleton.Alert if the user is in edit mode. It is critical, the plugin will not work... so it's not really a problem to popup a big window instead of a short log that disappears before you could even read the full mess
 
Back
Top Bottom