Plugins Auto Bulger

[jaro]

The belly bulger plugin generates absurd morphs. I use the standard plugin w/o any changes. If something enters the vagina just a little but, the whole belly starts bulging absurdely strong. If i set the multipliers low, it just grows stronger. Any idea how to fix this?

 

[Saking55]

The belly bulger plugin generates absurd morphs. I use the standard plugin w/o any changes. If something enters the vagina just a little but, the whole belly starts bulging absurdely strong. If i set the multipliers low, it just grows stronger. Any idea how to fix this?

Hi jaro! I can try to help if you give me some more information.
Does this happen everywhere or just in a specific scene? Is the "Limit Morphs" option enabled? Is the correct atom being selected as target in the plugin?

 

[jaro]

Hi jaro! I can try to help if you give me some more information.
Does this happen everywhere or just in a specific scene? Is the "Limit Morphs" option enabled? Is the correct atom being selected as target in the plugin?

Hello Saking55, it happens in every scene. "Limit Morphs" is enabled. I have not selected an atom as a target, but it does detect the correct atom - the reaction is only massively too high.

 

[Saking55]

Hello Saking55, it happens in every scene. "Limit Morphs" is enabled. I have not selected an atom as a target, but it does detect the correct atom - the reaction is only massively too high.

The strength of the morphs is controlled by the Belly Multiplier slider, but I assume you've already tried messing with that. By default, the morphing shouldn't be too extreme. I know that when using toys and shape atoms the distance measuring can get a little off. Can you send a screenshot of the problem with the plugin window open?

 

[ferlaron]

Hello! I was using timeline with poses. Seems that autobellybulger crashing on pose select/something like that(might be morphs freezes). Only when i reload cslist it seems to be ok after this. Do you know what can be done in this situation ?
Thanks in advance !

 

[Saking55]

Hello! I was using timeline with poses. Seems that autobellybulger crashing on pose select/something like that(might be morphs freezes). Only when i reload cslist it seems to be ok after this. Do you know what can be done in this situation ?
Thanks in advance !

Hi ferlaron! I'm not very familiar with using timeline with poses. From what I read from the timeline wiki, it does something to prevent physics issues when applying poses, wich may be messing with the autobulger plugin.
I couldn't manage to reproduce the error though. Could you describe some steps to reproduce the crash or maybe copy/paste the error output?

 

[WolfmanVR]

Great plugin! I think I found a bug though. I have the AutoBellyBulger plugin on a female character, and if I check Filter Atom Name and enter "Male" in the dialog box below it, the plugin works fine with my character named "Male". But, it resets to "Person" after a save/load. Then, since I don't have a character named "Person" in the scene, it stops working. Inspecting the scene's .json file, I don't see the custom filter atom name is being stored anywhere in the file. I figured out I can just uncheck Filter Atom Name (since I only have one female and one male in the scene, and it works fine), but figured you'd want to know this was occurring. Seems like it should be an easy fix...

 

[Saking55]

Great plugin! I think I found a bug though. I have the AutoBellyBulger plugin on a female character, and if I check Filter Atom Name and enter "Male" in the dialog box below it, the plugin works fine with my character named "Male". But, it resets to "Person" after a save/load. Then, since I don't have a character named "Person" in the scene, it stops working. Inspecting the scene's .json file, I don't see the custom filter atom name is being stored anywhere in the file. I figured out I can just uncheck Filter Atom Name (since I only have one female and one male in the scene, and it works fine), but figured you'd want to know this was occurring. Seems like it should be an easy fix...

Hi WolfmanVR, thanks for the report! I might've forgot to load/store the string in a JSON variable. I'll take a look at it and make a updated version

 

[Saking55]

Saking55 updated Auto Bulger with a new update entry:

New Update

Changes:

• Fixed Atom name filtering issue.
• Added alternative morphs to AutoBellyBulger.
• Fixed missing male morphs (ThroatBulger).

Read the rest of this update entry...

 

[07171985]

I use this almost every day in my scene, can really tell a difference haven't used plugin in two days, I wonder how lucky someone got to eat

 

[alwaysblue]

does this work for male base atoms?

 

[Saking55]

does this work for male base atoms?

Hi bash32
It should work fine (except the AutoGenExpansion plugin)

 

[ryanxlanford]

Hi bash32
It should work fine (except the AutoGenExpansion plugin)

Hi there,

I've been trying this on male person's lately. The morphs work when I do a manual depth slider, but auto detection (as well as manual mode) fails. I think this is due to:

          private CollisionTrigger triggerVag;
        private CollisionTrigger triggerVagD;
        private CollisionTrigger triggerVagDD;

Obviously the males don't have a Vag, so I was wondering if anal or taint detection was a possibility?

Thanks!

 

[Saking55]

Hi there,

I've been trying this on male person's lately. The morphs work when I do a manual depth slider, but auto detection (as well as manual mode) fails. I think this is due to:

          private CollisionTrigger triggerVag;
        private CollisionTrigger triggerVagD;
        private CollisionTrigger triggerVagDD;

Obviously the males don't have a Vag, so I was wondering if anal or taint detection was a possibility?

Thanks!

Hi ryanxlanford

As far as I remember the "triggerVag" trigger is used on both males and females Atoms. This is due to how the game was implemented/how stuff was named by meshedvr. So the variables names aren't the problem.

I'll have to investigate the problem further to see if I find any solution.

 

[ryanxlanford]

Hi ryanxlanford

As far as I remember the "triggerVag" trigger is used on both males and females Atoms. This is due to how the game was implemented/how stuff was named by meshedvr. So the variables names aren't the problem.

I'll have to investigate the problem further to see if I find any solution.

Hey Saking55,

I have tried everything. So far i can get it to work when there is a male penetrating a female, but if there is a strap-on, dildo, or futa penetrating a male, I get no luck. I've tried everything (including male on male) and my feeble little coding skills are no match.

do you have any suggestions? Maybe I'm doing something wrong?

 

[ouroborolapse]

Hi saking, is it possible to only load gen expression part of the plugin? the belly bulger looks weird with pregnant morph i had on my character

 

[BStarG2]

Hello, I'd like to know if it would be possible to update this plugin in order to achieve the following for penetration detection for the Gens Expansion portion of it: To automatically disable / enable Vagina or Anus expansion morphing based on the detected orifice?

Basically, if the dick penetrates the Anus, then disable the Vagina expansion effect. And inversely, if the penetration is for the Vagina, then disable the Anus expansion effect.

I'm asking this, because - as of now - we have to manually disable one or the other based on which orifice is being 'used' in a scene or any given position and animation. Because more often than not, if for example the Penis penetrates the Anus, then the Vagina expansion effect still happens, so both orifices are opened and it looks rather bad, not to say disturbing. It's especially true for scenes including big penis sizes (I.E. the larger the penis colliders are, the higher the chances for the expansion of the other orifice will not only trigger on, but the expansion itself goes wild as well).

Basically the plugin cannot differentiate (or detect) which orifice is being used, or perhaps worded differently, that it does not automatically disable one of the orifices when not being used.

This is mostly a suggestion mind you, it's not "essential" but I do believe this would be a 'fix' (or perhaps a new capability for the plugin, let's say).

Thank you!