• 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)

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

The way VAM consider you have dependencies is by looking up if you have .var references.
Simply having a full name inside "something" (a preset, a scene, a plugin...) would trigger the dependency system.

I think you would simply add a static string variable with a var name, it would think it's a dependency : )
 
The way VAM consider you have dependencies is by looking up if you have .var references.
Simply having a full name inside "something" (a preset, a scene, a plugin...) would trigger the dependency system.

I think you would simply add a static string variable with a var name, it would think it's a dependency : )
That makes big sense, but: My .cs file does contain a link to a (non base) morph file by WeebU in form of path to the .vmi:
1733507366119.png

and there is also a link to this package:
1733507524711.png

however, this morph is not recognised in the dependencies list by the hub apparently:
1733507301749.png

Do I have to do this differently for morphs to be recognised as a mandatory dependency?
Thanks for your help again.
BWT: Working on your suggestions from above...
 
Do I have to do this differently for morphs to be recognised as a mandatory dependency?
Thanks for your help again.
BWT: Working on your suggestions from above...

Umh! Then It might have been my json databases that produced that effect.

Try this: create a json file, whatever you want as a name in one of the plugin folder (probably hidden in a sub folder to avoid people using it) like "force-dependencies.json" and inside, put a base json like this

Code:
{
    "something.something.3.var/pathtosomething",
    "stuff.stuff.5.var/pathtosomething",
}
 
Btw, you won't do anything with the file. You're just creating it to force the package manager to trigger the hard dependencies.
 
Umh! Then It might have been my json databases that produced that effect.

Try this: create a json file, whatever you want as a name in one of the plugin folder (probably hidden in a sub folder to avoid people using it) like "force-dependencies.json" and inside, put a base json like this

Code:
{
    "something.something.3.var/pathtosomething",
    "stuff.stuff.5.var/pathtosomething",
}
Good idea. This one works (but only with this format with colon):
1733516499779.png

If I pack this into my .var, the morphs are put to the references list.
 
RunRudolf updated Realistic Foreskin & Erection Simulation (Plugins) with a new update entry:

Lots of Bugfixing & Flexible Penis Look Configurator

Expanded Penis Decal System
-Moved penis decal system to foreskin plugin - makes more sense there
- You can now choose from three different penis textures, plus 10 glans/testes color tones, plus 10 normal maps. Combine at will!

View attachment 438627

Lots of Bugs Fixed
- Silent critical errors fixed while changing UI menu tabs (both plugins)
- Orgasm sequences now remain when changing UI menu tabs (erection plugin)
- Fixed penis decal loading from presets...

Read the rest of this update entry...
 
there seems to be a big error with the new update. When orgasm, the "Testes Thick" morph is going crazy. I tested it in several scenes, created even a new, but its always the same occurrence.

1733579467061.png



1733579598866.png


How can I avoid this?

thanks in advance!
 

Attachments

  • 1733579561838.png
    1733579561838.png
    128.1 KB · Views: 0
Last edited:
there seems to be a big error with the new update. When orgasm, the test morph is going crazy. I tested it in several scenes, created even a new, but its always the same occurrence.

View attachment 438645


View attachment 438647

How can I avoid this?

thanks in advance!
It is intended that the "Testes Thick" Morph changes while at orgasm. However, it does usually not go down to -8.7. In my case, it varies between -1 and -2.2. Did you change the config values in the "Morphs" section? These are the standard values:
1733580846020.png
 
I've also tested the new plugin with your demo scene 2, and the same error happens. If I play the original demo scene, its working fine. as soon as i replace the plugin with the new one, the "Testes Thick" morph is going crazy.
 
I've also tested the new plugin with your demo scene 2, and the same error happens. If I play the original demo scene, its working fine. as soon as i replace the plugin with the new one, the "Testes Thick" morph is going crazy.
I can unfortunately not reproduce this problem with .43 and a default scene, however, this does not mean anything.
I will wait and see whether there are other complaints, this will maybe help to narrow down what the problem is. Alternatively, you can send very detailed info including all the settings, so that I can compare them.
 
which type of info do you need? what can I provide?
Maybe a video with starting from fresh vam, loading your default scene and moading the plugins. Plus screens of male morphs and plugin settings. That would be a good start!
 
RunRudolf updated Realistic Foreskin & Erection Simulation (Plugins) with a new update entry:

Smaller File,

- Only packaging modified texture contents, the rest is now linked to the original hub content. This reduces file size from 158 MB to 14 MB. Big thank you to @everlaster who made this possible by providing the necessary code input and helped me again!
- Sorry for the frequent updates. Still learning a lot and trying to improve things.

Read the rest of this update entry...
 
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
I have just been able to achieve considerable optimisations regarding the physics calculation load. See https://hub.virtamate.com/threads/in-a-good-mood-futa-female-camride.60277/post-183207. I hope to release the optimised plugins soon. Stay tuned...
 
RunRudolf updated Realistic Foreskin & Erection Simulation (Plugins) with a new update entry:

Performance Update

- Reduced physics calculation frametimes by -63 % and smoothened physics loads by code optimisations. This can boost FPS in many scenes as physics calculation time is drastically reduced (and might thus not be fps limiting any more).

View attachment 438954 View attachment 438955

- I will update my "In A Good Mood" scene (https://hub.virtamate.com/resources/in-a-good-mood-futa-female-camride.52545/) shortly, as this one will heavily benefit from the...

Read the rest of this update entry...
 
there seems to be a big error with the new update. When orgasm, the "Testes Thick" morph is going crazy. I tested it in several scenes, created even a new, but its always the same occurrence.

View attachment 438645


View attachment 438647

How can I avoid this?

thanks in advance!
I could reproduce it. For now, you should reduce the throbbing factor to 0.7. I will adjust parameters in the next version an prevent the testes thick morph from going over -2. Thanks for reporting!
 
I can unfortunately not reproduce this problem with .43 and a default scene, however, this does not mean anything.
I will wait and see whether there are other complaints, this will maybe help to narrow down what the problem is. Alternatively, you can send very detailed info including all the settings, so that I can compare them.
this is a problem i've been having since version 36. I keep all the default setting. maybe it's the morph of the default male model before attaching the plugin onto the atom?
 
this is a problem i've been having since version 36. I keep all the default setting. maybe it's the morph of the default male model before attaching the plugin onto the atom?
Hi, and thanks for reporting! For the moment, please reduce throbbing and the amount of tested thick morph. It will be fixed in the upcoming version.

BTW: Next release will be a major one, including divining rod functionality plus direct gen skin texture management (thus no more need for decal maker and reducing plugin footprint).
 
Hi, and thanks for reporting! For the moment, please reduce throbbing and the amount of tested thick morph. It will be fixed in the upcoming version.

BTW: Next release will be a major one, including divining rod functionality plus direct gen skin texture management (thus no more need for decal maker and reducing plugin footprint).
I've been hoping the problem would be fixed for the update version.
I've went back to version 35, which work perfectly for me.
Thank you and I appreciate all your work.
 
Is the right testicle missing from the morph tab? Btw you've been making amazing improvements to this plugin recently :) amazing job 😁
 
Back
Top Bottom