You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to revert this change? HTC Vive controllers allow you to pull the trigger when you have a Gesture selected. It switches to Gesture=1 fast enough to leave the existing animation untouched, letting you "merge" the previous animation into Gesture=1. Uncertain if other controller types work this way.
I don't know if "vive advanced controls" support was ever implemented in av3 emulator. I think it was forcing weight = 1 when it isn't fist, but yeah you are correct that VRChat advanced controls allow custom weights for other gestures.
For now, you can use the debug inspector to set weight (the little icon at the top right of the inspector panel, where it has add tab) switch Normal -> Debug. However, I think av3 emulator might still ignore the weight even if you do this.
So for now, it's an oversight / missing feature. But I will consider reverting this change thanks to your feedback.
The text was updated successfully, but these errors were encountered:
I'm not sure if it's related to "vive advanced controls" but from what I've observed it just switches fast enough to Gesture=1 ignoring Write Defaults (which is set to on for all states in the layer). The example video attached has a Direct Blend Tree in Gesture=1 using the Weight as parameter to open the mouth.
Originally posted by @GapVR in 403c098
I don't know if "vive advanced controls" support was ever implemented in av3 emulator. I think it was forcing weight = 1 when it isn't fist, but yeah you are correct that VRChat advanced controls allow custom weights for other gestures.
For now, you can use the debug inspector to set weight (the little icon at the top right of the inspector panel, where it has add tab) switch Normal -> Debug. However, I think av3 emulator might still ignore the weight even if you do this.
So for now, it's an oversight / missing feature. But I will consider reverting this change thanks to your feedback.
The text was updated successfully, but these errors were encountered: