• Hi Guest!

    We are extremely excited to announce the release of our first Beta for VaM2, the next generation of Virt-A-Mate which is currently in development.
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
Bone Control

Plugins + Scripts Bone Control

Download [0.03 MB]
Whoa. You are a mad genius!
Screenshot 2025-04-29 005427.png

lol
 
This plugin saves me so much trouble.

I have one request and one comment.

When you select a pose through the trigger "Saved Poses", it applies immediately. In my case this causes an issue. On the poses I've set up, I apply the tail pose with the person pose. But since the bone pose is applied immediately, the person might not have settled yet from snapping to the pose. And a little hip rotation goes a long way when you have a ~1.30 meter tail. It's better the tail tries to follow the person first, and then after a short delay, the pose is applied with a trigger. I've set it up this way with a delay but it currently means the pose is applied twice, often causing a bit of physics mayhem before the delay and always looking janky.
I could fix this with logicbricks but it'd be another layer of triggers per pose, where just the delayed call of apply pose wouldn't. So I'm hoping you'll consider. 🙏

The pose numbering gets a bit messy with no way to create/maintain a system. If you delete one in the middle that number is gone forever. And the dropdown list and slider select order is sorted like 1,11,12.. 2,21,22..
I did end up finding a workflow where I didn't have to keep track of the numbers though.



Almost done transitioning my scene to use this instead. With this and your CUA clothing plugin I've been able to cut out so many complicated workarounds and make it much nicer for end users. Feels like a convuluted mess of wires and landmines have been removed from the backstage.
 
This plugin saves me so much trouble.

I have one request and one comment.

When you select a pose through the trigger "Saved Poses", it applies immediately. In my case this causes an issue. On the poses I've set up, I apply the tail pose with the person pose. But since the bone pose is applied immediately, the person might not have settled yet from snapping to the pose. And a little hip rotation goes a long way when you have a ~1.30 meter tail. It's better the tail tries to follow the person first, and then after a short delay, the pose is applied with a trigger. I've set it up this way with a delay but it currently means the pose is applied twice, often causing a bit of physics mayhem before the delay and always looking janky.
I could fix this with logicbricks but it'd be another layer of triggers per pose, where just the delayed call of apply pose wouldn't. So I'm hoping you'll consider. 🙏

The pose numbering gets a bit messy with no way to create/maintain a system. If you delete one in the middle that number is gone forever. And the dropdown list and slider select order is sorted like 1,11,12.. 2,21,22..
I did end up finding a workflow where I didn't have to keep track of the numbers though.



Almost done transitioning my scene to use this instead. With this and your CUA clothing plugin I've been able to cut out so many complicated workarounds and make it much nicer for end users. Feels like a convuluted mess of wires and landmines have been removed from the backstage.
Hmm.. that's weird bc i have tested the pose application delay and it worked in sync with person pose settling delay aswell, for now the solution is to use logicbricks Delayed Trigger. i fine tuned the pose freeze delay to be exactly like the person pose delay so i don't understand why it isn't working well for you, maybe because the tail you're using has collision? (it shouldn't if it is clipping through the person).

Yes i'm aware of the pose sequence issue, to avoid it you have to replace poses instead of deleting them. for now i'm not knowledgeable enough to know how to make it better unfortunately

Maybe in the future once i have some spare time i'll try to make this a bit better, for a coding newbie like me 3000+ lines of codes just gives me headaches at this point 😅
 
Hmm.. that's weird bc i have tested the pose application delay and it worked in sync with person pose settling delay aswell, for now the solution is to use logicbricks Delayed Trigger. i fine tuned the pose freeze delay to be exactly like the person pose delay so i don't understand why it isn't working well for you, maybe because the tail you're using has collision? (it shouldn't if it is clipping through the person).

Yes i'm aware of the pose sequence issue, to avoid it you have to replace poses instead of deleting them. for now i'm not knowledgeable enough to know how to make it better unfortunately

Maybe in the future once i have some spare time i'll try to make this a bit better, for a coding newbie like me 3000+ lines of codes just gives me headaches at this point 😅
Understandable. Incredible you've been able to do as much as you have as a newbie.
Yeah the tail has collision. The clipping is due to the space between the colliders on the tail, person and other object colliders sometimes get wedged inbetween. There's some strange behavior in VAM where the collision tick doesn't work on CUAs with rigidbodies. So to avoid person collision temporarily I have to disable collision for the person.
Maybe it's not loading the bone pose immediately that's the problem. I just see that once it's applied a second time after the delay it rests like it should. I'd just love if I could get rid of the jitters.
GIF 23-05-2025 13-51-23.gif

I cannot stress enough though, how much better this is than setting up poses with timeline.
 
Understandable. Incredible you've been able to do as much as you have as a newbie.
Yeah the tail has collision. The clipping is due to the space between the colliders on the tail, person and other object colliders sometimes get wedged inbetween. There's some strange behavior in VAM where the collision tick doesn't work on CUAs with rigidbodies. So to avoid person collision temporarily I have to disable collision for the person.
Maybe it's not loading the bone pose immediately that's the problem. I just see that once it's applied a second time after the delay it rests like it should. I'd just love if I could get rid of the jitters.
View attachment 491188
I cannot stress enough though, how much better this is than setting up poses with timeline.
you can truly disable all colliders with physics manager plugin but i don't think that's going to fix this, i think before saving the CUA pose you have to wait for everything to settle down with the bench & person colliders first. probably that should do the trick
 

Similar threads

Back
Top Bottom