Plugins BodyLanguage

[CheesyFX]

Custom/Scripts/CheesyFX/BodyLanguage/EmoteTextures//Dicks

This path should exist inside the var. Make sure it is by opening it with e.g. 7zip. If it exists, I have no clue what causes this issue.

 

[n8mi69]

This path should exist inside the var. Make sure it is by opening it with e.g. 7zip. If it exists, I have no clue what causes this issue.

The files are in the VAR. I manually copied them in place an still the same errors. Most of it still works but "ReadMyLips" doesn't load

 

[burim001]

Hello chessy i dont know if this is another bugg or problem but when you save a pose for example handjob and when you jump to different poses and then you jump back at the handjob pose somehow the hand just doesnt go at the place i save it i reset all the finger bends tho and still the same problem,anyway how e can fix that ? or its just me who cant make it work right !?

 

[n8mi69]

The files are in the VAR. I manually copied them in place an still the same errors. Most of it still works but "ReadMyLips" doesn't load

My installation path was directly on a drive that was dedicated to VAM. I moved the full installation inside a folder and the plugins are working now.

 

[CheesyFX]

Hello chessy i dont know if this is another bugg or problem but when you save a pose for example handjob and when you jump to different poses and then you jump back at the handjob pose somehow the hand just doesnt go at the place i save it i reset all the finger bends tho and still the same problem,anyway how e can fix that ? or its just me who cant make it work right !?

The rotation seems to be off in your case. Try to save the pose while "Freeze Motion/Sound" is enabled. The position and rotation you see is not what the controllers dictate - it is highly modified by the forces. If you load the pose it's not guaranteed that you reach the exact same state. Save the pose without forces and make sure it isn't totally off in this case.
v55 will automatically disable all forces while storing the pose.

 

[BStarG2]

Hey there CheesyFX, got some questions regarding the Anus stretching effect, and the Bulging effect.

1) Anus Stretch effect

I'm trying to figure out basically what actually influences how 'much' (or how "far") the Anus can stretch to start with. Is that effect directly related (only, or in part) to the colliders size and position on the Female Anus/Vagina region? (which would determine how much is can stretch?)

I'm asking this because - so far - as I try the plugin on various characters (all custom, I never use the default Female just to be clear, maybe that does have an influence already, because of how differently each characters are morphed, and maybe the colliders aren't positioned exactly the same in each one of them, etc), the actual numerical value of the Stretching seems to never go beyond 0.45 (average seems to stick around 0.43), and I'm wondering if that's actually the plugin's own limits, or if - again - it's related to something else within the receiver character itself.

And the main reason as to why I'm wondering if it can be beyond 0.45 is because I've been trying all manners of dick sizes and I can't tell exactly which dick size is even 'supported', or how much the dick's own colliders may also influence the whole thing; or if it would be recommended to not go beyond a certain size for the dick (or heck, maybe even the actual dick shape/morph has something to do in all of it?). In other words, I'm pretty confident that I've tried dick sizes that "should" stretch the Anus "more" but.... "more" than what I'm not even sure; I don't know if there is an actual limitation.

Do you have maybe a demo-style scene that would show the 'maximums' of the Plugin's capabilities in that regard?

2) Bulging effect (mostly belly, but also could be the throat)

For this one I would like to know if - quite simply - you could increase the effect's current maximums? (depth, 'girth' or 'width' on the belly/stomach/abdomen region, and height I.E. Z axis I think, or how much 'upwards' the stomach can bulge). I'm asking this because I've been using Sakin55's Auto Bulger plugin for the Vagina, but I'm not a fan of that plugin's own belly bulging effect.

I actually prefer how 'smoother' your belly bulging looks (not sure why, maybe you're simply using better morphs to achieve the effect, but it looks better to me). My only 'gripe' is that the current maximum values don't go 'far' enough if you know what I mean there. It's of course based on my personal preferences but, also, it's because when it comes to belly and abdomen bulging I realized that on a technical level it actually creates more 'space' inside, pushing the colliders from next to each others and decreasing the chances of clipping with large sized dicks during penetration.

So this is just my two cents, but yeah maybe more bulging than currently-available would be nice to see happen, in future updates maybe (for the belly mostly, but maybe the throat too).

Thanks for your time, and thank you for all your work.

 

[tonyhawksp]

When I loaded the latest version of the BodyLanguage plug-in, there were multiple sub-scenes in my scene. After I loaded the plug-in, if any sub-scene loaded other sub-scenes, the system animation stopped automatically, and the sub-scenes were not loaded successfully.

 

[AWWalker]

Any chance PoseMe Can be broken out as it's own plugin? It's incredibly useful on it's own. Sometimes i'm loading the whole plugin just for that. (which leads to other issues since you can't disable some of the other options when used with my older scenes)

 

[Rootlus]

The more I dig into this plugin the more I see how powerful it is. The amount of triggers is just a fantastic way to skip having to manually add triggers through timeline. Can't truly explain how much I love this. If I could make one suggestion that may be easy or hard idk. Could you make it so proximity triggers can be based on which atom is in proximity. i.e., Allowing the ability to trigger different atoms plugins like activating mouth targeting for autogensthruster based on which atom is in the throat proximity. This is a great trick when divining rod just doesn't cut it and works perfectly so long as you only have one male/futa atom because there is only one trigger list. But since your plugin already is capable of recognizing the atom that is effecting the trigger, would be awesome to have it so the trigger can be customized based on which atom is triggering. Maybe an IF/THEN trigger to open separate event action menus. Hopefully that makes sense. Not sure If I'm asking a lot or not as I haven't dipped my toes in making plugins. And maybe this is already possible I just haven't found the setting. Also where is your Patreon?! Discord Channel? I would support If I could find one for you.

 

[chako]

Thank you for your great jobs. I love this plugin.
But, I have a trouble with "cam" setting of version 54.
In a pose I press "update cam" and sotre the Cam position. But, the Cam position restored is far below when I restore the pose.

 

[CheesyFX]

Hi

Thank you for your great jobs. I love this plugin.
But, I have a trouble with "cam" setting of version 54.
In a pose I press "update cam" and sotre the Cam position. But, the Cam position restored is far below when I restore the pose.

Hi!
You probably rotated the main controller of the containing person in x or z. This is broken right now, but will be better with the next version.
Fix: Detach the main controller and rotate it back to default (y rotation is ok).

 

[CheesyFX]

Any chance PoseMe Can be broken out as it's own plugin? It's incredibly useful on it's own. Sometimes i'm loading the whole plugin just for that. (which leads to other issues since you can't disable some of the other options when used with my older scenes)

No, probably not. It's already tied to the others and the entanglement keeps getting more instead of less while I continue developing.

Why do you want PoseMe to be present in an older scene that is already complete enough so that you don't need the other modules?

 

[CheesyFX]

The more I dig into this plugin the more I see how powerful it is. The amount of triggers is just a fantastic way to skip having to manually add triggers through timeline. Can't truly explain how much I love this. If I could make one suggestion that may be easy or hard idk. Could you make it so proximity triggers can be based on which atom is in proximity. i.e., Allowing the ability to trigger different atoms plugins like activating mouth targeting for autogensthruster based on which atom is in the throat proximity. This is a great trick when divining rod just doesn't cut it and works perfectly so long as you only have one male/futa atom because there is only one trigger list. But since your plugin already is capable of recognizing the atom that is effecting the trigger, would be awesome to have it so the trigger can be customized based on which atom is triggering. Maybe an IF/THEN trigger to open separate event action menus. Hopefully that makes sense. Not sure If I'm asking a lot or not as I haven't dipped my toes in making plugins. And maybe this is already possible I just haven't found the setting. Also where is your Patreon?! Discord Channel? I would support If I could find one for you.

Yes, some kind of condition system was planed for the triggers. But I stopped working on them because
1) I don't need triggers for myself. If I want something, I code it.
2) People don't seem to use them neither, measured by released scenes.

BUT the big question to me is why in hell do you want to trigger AutoGensThruster with BodyLanguage??? You know that BL does thrusting forces automatically, right? And they look far better than any other thruster, too. At least in my opinion.
I don't get why people keep mixing this up with older stuff...

 

[CheesyFX]

Hey there CheesyFX, got some questions regarding the Anus stretching effect, and the Bulging effect.

1) Anus Stretch effect

I'm trying to figure out basically what actually influences how 'much' (or how "far") the Anus can stretch to start with. Is that effect directly related (only, or in part) to the colliders size and position on the Female Anus/Vagina region? (which would determine how much is can stretch?)

I'm asking this because - so far - as I try the plugin on various characters (all custom, I never use the default Female just to be clear, maybe that does have an influence already, because of how differently each characters are morphed, and maybe the colliders aren't positioned exactly the same in each one of them, etc), the actual numerical value of the Stretching seems to never go beyond 0.45 (average seems to stick around 0.43), and I'm wondering if that's actually the plugin's own limits, or if - again - it's related to something else within the receiver character itself.

And the main reason as to why I'm wondering if it can be beyond 0.45 is because I've been trying all manners of dick sizes and I can't tell exactly which dick size is even 'supported', or how much the dick's own colliders may also influence the whole thing; or if it would be recommended to not go beyond a certain size for the dick (or heck, maybe even the actual dick shape/morph has something to do in all of it?). In other words, I'm pretty confident that I've tried dick sizes that "should" stretch the Anus "more" but.... "more" than what I'm not even sure; I don't know if there is an actual limitation.

Do you have maybe a demo-style scene that would show the 'maximums' of the Plugin's capabilities in that regard?

2) Bulging effect (mostly belly, but also could be the throat)

For this one I would like to know if - quite simply - you could increase the effect's current maximums? (depth, 'girth' or 'width' on the belly/stomach/abdomen region, and height I.E. Z axis I think, or how much 'upwards' the stomach can bulge). I'm asking this because I've been using Sakin55's Auto Bulger plugin for the Vagina, but I'm not a fan of that plugin's own belly bulging effect.

I actually prefer how 'smoother' your belly bulging looks (not sure why, maybe you're simply using better morphs to achieve the effect, but it looks better to me). My only 'gripe' is that the current maximum values don't go 'far' enough if you know what I mean there. It's of course based on my personal preferences but, also, it's because when it comes to belly and abdomen bulging I realized that on a technical level it actually creates more 'space' inside, pushing the colliders from next to each others and decreasing the chances of clipping with large sized dicks during penetration.

So this is just my two cents, but yeah maybe more bulging than currently-available would be nice to see happen, in future updates maybe (for the belly mostly, but maybe the throat too).

Thanks for your time, and thank you for all your work.

1) There is no limit implied by my plugin. For the anus the stretch is measured by how far the 2 anus colliders are stretched apart. The physics engine will only allow for that much stretching, that's where the soft limit comes from. For all the other orifices, the stretch is proportional to the diameter of the penetrator. The value can go as high as you want. Of course you have to fit things in.
But be careful: All changes you make to the penis colliders (through e.g. ColliderEditor) will mess things up. The visuals of the penis are irrelevant, the colliders count.

2) I'll see if I can uncap it

 

[Rootlus]

Yes, some kind of condition system was planed for the triggers. But I stopped working on them because
1) I don't need triggers for myself. If I want something, I code it.
2) People don't seem to use them neither, measured by released scenes.

BUT the big question to me is why in hell do you want to trigger AutoGensThruster with BodyLanguage??? You know that BL does thrusting forces automatically, right? And they look far better than any other thruster, too. At least in my opinion.
I don't get why people keep mixing this up with older stuff...

Lol I agree the thrusting looks way better in your plugin. And to be honest, I posted that before I dug into the forces configure on your plugin. My big thing was the alignment and the magnet config can adjust for that. SO... yeah BL definitely has that covered lol! I guess this kinda explains why people still use old stuff with your plugin, It has so much built into it that it's like an onion with new layers to find every time you dig in and they haven't found everything yet. I would say just give it some time for the big scene creators to start using it to it's full potential, although I know there are some old dogs who don't like new tricks. Still think the condition system for triggers would be huge QOL but Understandable if you decide not to do it. Plugin is packed already. Anyway, thank you for the response and I look forward to seeing more of your work!

 

[CheesyFX]

Lol I agree the thrusting looks way better in your plugin. And to be honest, I posted that before I dug into the forces configure on your plugin. My big thing was the alignment and the magnet config can adjust for that. SO... yeah BL definitely has that covered lol! I guess this kinda explains why people still use old stuff with your plugin, It has so much built into it that it's like an onion with new layers to find every time you dig in and they haven't found everything yet. I would say just give it some time for the big scene creators to start using it to it's full potential, although I know there are some old dogs who don't like new tricks. Still think the condition system for triggers would be huge QOL but Understandable if you decide not to do it. Plugin is packed already. Anyway, thank you for the response and I look forward to seeing more of your work!

Yeah, totally understandable that it's hard to get a grip on all the features, especially since there is no complete documentation. But for the thrusting - just put it in and you'll see them thrust at each other. Is there a way to miss that, lol?

 

[CheesyFX]

Lol I agree the thrusting looks way better in your plugin. And to be honest, I posted that before I dug into the forces configure on your plugin. My big thing was the alignment and the magnet config can adjust for that. SO... yeah BL definitely has that covered lol! I guess this kinda explains why people still use old stuff with your plugin, It has so much built into it that it's like an onion with new layers to find every time you dig in and they haven't found everything yet. I would say just give it some time for the big scene creators to start using it to it's full potential, although I know there are some old dogs who don't like new tricks. Still think the condition system for triggers would be huge QOL but Understandable if you decide not to do it. Plugin is packed already. Anyway, thank you for the response and I look forward to seeing more of your work!

Btw, you can find my discord on my profile page. I don't have a patreon, but thanks for asking

 

[AWWalker]

No, probably not. It's already tied to the others and the entanglement keeps getting more instead of less while I continue developing.

Why do you want PoseMe to be present in an older scene that is already complete enough so that you don't need the other modules?

I love how it works, and sometimes the other aspects of the full plugin go crazy and my model starts sliding out of the the room, or explodes. Don’t get me wrong the entire thin plugin is awesome, but sometimes I just want the ability to change the pose only in a scene

 

[CheesyFX]

I love how it works, and sometimes the other aspects of the full plugin go crazy and my model starts sliding out of the the room, or explodes. Don’t get me wrong the entire thin plugin is awesome, but sometimes I just want the ability to change the pose only in a scene

You definitely have some weird shit going on in your scene then. Never experianced such things. Ther's no way Bl will slide the whole character.
What I meant is if you already hava a scene, there should be poses triggered by some means. If you start adding BL poses none of your timeline animations etc. won't work on them. So I see no reason to try and make them compatible with existing scenes.
For new scenes: If you don't want forces press CTRL+F. From there you can do whatever you want with the pose triggers and e.g. timeline.

 

[AWWalker]

You definitely have some weird shit going on in your scene then. Never experianced such things. Ther's no way Bl will slide the whole character.
What I meant is if you already hava a scene, there should be poses triggered by some means. If you start adding BL poses none of your timeline animations etc. won't work on them. So I see no reason to try and make them compatible with existing scenes.
For new scenes: If you don't want forces press CTRL+F. From there you can do whatever you want with the pose triggers and e.g. timeline.

Yeah, probably something weird.

As far as the pose plugin, i just like your interface, and the ease of storing the poses in the scene, i hardly ever use premade scenes, they are really only good one or two times, then i get tired of them. I get more joy in making a scene. i just make my own depending on my mood, and i thought it would be pretty cool if i could save a bunch of poses in it, w/o all the extra addons. No worries, if it's too integrated in the rest of the code i get it.

 

[chako]

Hi

Hi!
You probably rotated the main controller of the containing person in x or z. This is broken right now, but will be better with the next version.
Fix: Detach the main controller and rotate it back to default (y rotation is ok).

Thank you for your swift reply!
I could understand the reason of my trouble by your reply.
I looked into the rotations of the main controller in x and z. But rotations of x and z were zero.
Anyway, I will look forward to be modified this in next version.

 

[alwaysblue]

can you use this along with timeline?

 

[CheesyFX]

can you use this along with timeline?

Yes.

 

[cnorton76]

I cannot get the person atom parented to a subscene (with custom name) with v54. It refuses to register properly. Following the same steps works without issues in v52.

 

[CheesyFX]

I cannot get the person atom parented to a subscene (with custom name) with v54. It refuses to register properly. Following the same steps works without issues in v52.

Subscenes are not supported. They mess up a lot of things.