Tupper - VRChat Head of Community: consider that parameters can be used to change state settings (normalized time, speed, maybe something else). Having a single parameter for total speed would be much easier than using extra states or blend trees to get the same effect.

Tupper - VRChat Head of Community: I get what you're saying, and I was thinking about using that technique myself, but the only reliable way to have a speed blendtree, which is the use case I had in mind, is to have the magnitude of the vector fed into the animator as you can't do actual math in the animator.

knah: not to mention, the overhead introduced for doing it that way would be quite a bit, and seeing as the team mentioned worrying about the extra overhead in their video, I think this would be a good case to think about. Unfortunately I can't go try those things myself atm as my computer died yesterday while uploading, but I think adding a "Vector3.Magnitude" can just not happen if the parameter isn't there to drive right? Also it would be much more performant that way than attempting to do it in the animator.

Synergiance: Ahh, gotcha. Good point. We'll take this into consideration.

Tupper - VRChat Head of Community: My current usecase is I want a gameobject that becomes active when velocity is above a certain amount. This currently is messy and and inaccurate along diagnols and I don't think it can be done via blend tree.

I suppose one thing would be handy instead would be a IK-sycned Bool for if they're currently locomoting with arrowkeys/sticks.