Plugins + Scripts Realistic Foreskin & Erection Simulation

[RunRudolf]

Hi kim05, thanks for the explanations and the video. In this case, I agree that the foreskin should definitely move, at least as long as the hand strikes it. It's however codewise somewhat tricky, because you have three potential triggers (hand, vagina, anus) which are all very close to each other. Could you send me the scene .json so that I can debug it properly? I will check which trigger is actually active or if its in transitional state (which sometimes happens). I will then propose a solution and discuss this with you, if you want. Not sure yet whether I will add an option to select/unselect triggers (e.g. deselect anus/vagina in your case), or whether I can improve the overall targeting algorithms.
In any case, thanks for reporting this and your help.

I reproduced it. It seems it really is the vagina target preventing the hand target to act. If you deactivate vagina (and anus) (the switches are there arleady, did not remember) the hand target should start to work. Can you confirm this?

I still think it could make sense to add a slider to let the user control how much dampening there is depending on the trigger. What do you think?

 

[806387023]

Thanks @806387023 for your report. I tried to reproduce it and failed. However, I have recently implemented a few more checks to deal with gender swaps, including an automatic plugin restart after switching from female to male/altfuta and vice versa, which might help to prevent such issues as the one you reported. These changes will be in the next update soon.

One question however remains: Why would you load a plugin preset you saved on a male atom on a female atom? That does not make any sense right now in my opinion. There are a few things you can do on females now (e.g. Clothing and AltFuta tabs are usable), but everyhing in ERection and Foreskin is for AltFuta and Male use only. So you better load the preset on males or AltFuta.

I just wanted to make it easier to load the plugin, so I saved it separately as a preset. It doesn't matter whether it's saved as a male or female version. The important thing is that I can quickly and conveniently load this plugin by loading the preset. I accidentally discovered this error because I have too many var packages in my inventory, so whenever I load a plugin, I need to search for it by name.

 

[kim05]

Hi kim05, thanks for the explanations and the video. In this case, I agree that the foreskin should definitely move, at least as long as the hand strikes it. It's however codewise somewhat tricky, because you have three potential triggers (hand, vagina, anus) which are all very close to each other. Could you send me the scene .json so that I can debug it properly? I will check which trigger is actually active or if its in transitional state (which sometimes happens). I will then propose a solution and discuss this with you, if you want. Not sure yet whether I will add an option to select/unselect triggers (e.g. deselect anus/vagina in your case), or whether I can improve the overall targeting algorithms.
In any case, thanks for reporting this and your help.

Thank you for your swift and professional response.
I'm afraid that won't be productive since I just loaded the scene and it immediately results in physics explosion due to all the janky workarounds I had to do in order to position atoms like so in the first place. Plus what you see in the video was quite possibly the result of me messing with settings and then not resetting everything correctly. I can recreate this pose in an empty scene with no heavy load form CUA and miscellaneous plugins if you're interested and send you that, but then again I think previous video is most likely the result of my fiddling. My issues are not with the fact that it's not working, really, it's with the fact that even if it is working, the impact is too weak. It is also working weird with "quick insert, quick pull out" kind of poses.
Here's an example:

Here you can see it doesn't react to some thrusts an some thrusts it's being pulled up. So the default position of foreskin in this pose is pulled down to the max looking quite circumcized, then after a thrust it pulls upward with the movement of vagina going up.
This time it is default settings on a freshly added plugin (I only edited erection morphs like genital bulge and penis curves), so it can't be my fiddling. However I did fiddle after recording with the offset Y for vagina and disabled Target Activation:

This did yield a limited result as in barely noticeable decrease in foreskin being pulled up by vagina, but it is not solving any primary problems, so I set it back to default.
I added json of this scene if you're interested to see for yourself, but I never shared any scenes and the atom model is probably going require some obscure dependencies.

(By the way, I would highly advise to add option for offset gizmos like what the ExtraAutoGenitals plugin does, if you can. I felt like I was looking for the right placement of the target activation as if it was a sea-mine and I was using derelict sonar in a WW1 U-boat.)

The main problem for me is that what I expect is like what I said earlier "foreskin is moved by the edge of labia majora". Effectively same result as with a handjob where the index finger and thumb are a sort of border beyond which no foreskin is allowed to stay. Not unrealistic at all, if you imagine that the grip of the fingers is not rested on the foreskin itself, but on the glans, so that the index and thumb are sort of peeling the foreskin away. And if you can imagine that, also imagine the same thing, but instead of fingers it is labia majora. That is the effect I am after.
I would never even think to insist that it should be the default effect of the plugin, but I feel vexed that I cannot customize the inner settings of the plugin to make this happen.
That is my primary concern and if sometime in the future you could possibly expand the customization possibilities within the plugin settings, I'd be alight with gratitude.
Detection in my wonky, poorly made poses where there are two or three orifices involved with the same penis is far less of an issue

 

[kim05]

I reproduced it. It seems it really is the vagina target preventing the hand target to act. If you deactivate vagina (and anus) (the switches are there arleady, did not remember) the hand target should start to work. Can you confirm this?

View attachment 495224

I still think it could make sense to add a slider to let the user control how much dampening there is depending on the trigger. What do you think?

I think if I get back to that scene to fix it, it would work, yes.

 

[RunRudolf]

Thank you for your swift and professional response.
I'm afraid that won't be productive since I just loaded the scene and it immediately results in physics explosion due to all the janky workarounds I had to do in order to position atoms like so in the first place. Plus what you see in the video was quite possibly the result of me messing with settings and then not resetting everything correctly. I can recreate this pose in an empty scene with no heavy load form CUA and miscellaneous plugins if you're interested and send you that, but then again I think previous video is most likely the result of my fiddling. My issues are not with the fact that it's not working, really, it's with the fact that even if it is working, the impact is too weak. It is also working weird with "quick insert, quick pull out" kind of poses.
Here's an example:
View attachment 495284
Here you can see it doesn't react to some thrusts an some thrusts it's being pulled up. So the default position of foreskin in this pose is pulled down to the max looking quite circumcized, then after a thrust it pulls upward with the movement of vagina going up.
This time it is default settings on a freshly added plugin (I only edited erection morphs like genital bulge and penis curves), so it can't be my fiddling. However I did fiddle after recording with the offset Y for vagina and disabled Target Activation:
View attachment 495285
This did yield a limited result as in barely noticeable decrease in foreskin being pulled up by vagina, but it is not solving any primary problems, so I set it back to default.
I added json of this scene if you're interested to see for yourself, but I never shared any scenes and the atom model is probably going require some obscure dependencies.

(By the way, I would highly advise to add option for offset gizmos like what the ExtraAutoGenitals plugin does, if you can. I felt like I was looking for the right placement of the target activation as if it was a sea-mine and I was using derelict sonar in a WW1 U-boat.)

View attachment 495287


The main problem for me is that what I expect is like what I said earlier "foreskin is moved by the edge of labia majora". Effectively same result as with a handjob where the index finger and thumb are a sort of border beyond which no foreskin is allowed to stay. Not unrealistic at all, if you imagine that the grip of the fingers is not rested on the foreskin itself, but on the glans, so that the index and thumb are sort of peeling the foreskin away. And if you can imagine that, also imagine the same thing, but instead of fingers it is labia majora. That is the effect I am after.
I would never even think to insist that it should be the default effect of the plugin, but I feel vexed that I cannot customize the inner settings of the plugin to make this happen.
That is my primary concern and if sometime in the future you could possibly expand the customization possibilities within the plugin settings, I'd be alight with gratitude.
Detection in my wonky, poorly made poses where there are two or three orifices involved with the same penis is far less of an issue

Hi kim05, and thanks again for these clarifications. I will try to explain how the forsekin plugin works and, based on this, we can evaluated what's realistically possible to achieve "foreskin is moved by the edge of labia majora".

First of all, the plugin follows this geometrical principles to determine the foreskin (slightly simplified, but still true): The plugin continuously measures the distance of a trigger (e.g. hand, vagina, mouth...) from both penis base and penis tip and compares the sum of these two distances to the penis length. If the sum of distances times 0.7 is larger than the penis length, the trigger is assumed to be out of range of the foreskin and no movement occurs. If the sum of distances times 0.7 is smaller than the penis length, it is assumed the trigger is actively moving the foreskin. The amoutn of foreskin retraction is then calculated by taking the ratio of distance to tip vs. distance to base. This is the very basic method, of course extended with quite a few "tunings", but thats it. Its not any physics simulation involved at all. The hand does not really move the foreskin, this is a mathematical model to approximate physics.

Knowing about the method from above, it becomes clear that it will be difficult to achieve effects like "outer labia will retract foreskin" or the like. This could be done with physical interactions, but is difficult to achieve if dealing with a variety of very different trigger (VR hands, atom hands, feet, chest, anus, vagina) and lots of possible orientations (tit fuck against vagina penetration is really different).

That said, the foreskin movement can be tuned to allow much stronger movement. However, this is something I have reduced over the many updates in the past, particularly in erect state, because the foreskin in erect state would naturally be moved back quite far, and it would only move forward a lot if grasped by a hand. If these strong foreskin movements are generally allowed (in erect state), you will get silly looking effects in other situations.

In order to give you a chance to setup your desired effects, I will briefly test which parameters I would need to add to the UI to allow this. There is a (hidden) dampening factor I could make available, and the (already available) foreskin tension plays an important role. I will experiment a bit and we'll see if it makes sense to add this.

Regarding the idea of somehow making the trigger offsets visible, that's a good input indeed. I'll try to figure out how this is possible.