Obtaining all AnimatorStateInfo from Mecanim

Is there a way to get all the AnimatorStateInfo so that we can change some of the properties through script ?

It seems that we could only get the current active one by using GetCurrentAnimatorStateInfo() now.
Reference: http://docs.unity3d.com/ScriptReference/Animator.GetCurrentAnimatorStateInfo.html

 

I was thinking to modify the speed of the AnimationStateInfo by script. For example, I have two characters which have a running animation, and they share the same Animator prefab, but
- Character A runs faster, so the speed for the running animation should be set to 2
- Character B runs normal, so its running animation speed is 1
The speed data itself is stored on a another component, (PlayerComponent for example).
Is it possible to do this ? If possible, I don't want to change the speed of the Animator itself though.

Another thing that my colleague is currently thinking is for debugging purposes. He would like to have a combobox displayed during runtime, which consists of all the AnimationStateInfo that a selected character has.
If the value of the combobox is changed, then the selected character should perform the selected animation.
Any ideas how to do this ?

 

I see. Could you please let me know how to query the available states using a script in the editor then ?

 

It's a nightmare. And you'd be solving a problem that shouldn't exist in a counterintuitive hacky way. Resurrecting this thread a bit because I recently wrote up my feelings about the lack of runtime access to the state machine in the current version of Mecanim, with the somewhat antagonistic title: Mecanim is broken and needs to be fixed properly. Posting this here hoping that Mecanim.Dev will see it and weigh in on it

At the end of the day it's a design problem. The state machine itself is not cloned at runtime, so making changes to it at runtime would be problematic, thus they're not exposed to us. This is contrary to most Unity designs, where the object is instanced at runtime, and changes made to an object at runtime have no impact upon the original source object.

As Mecanim.Dev said, there's a solution to this scheduled for 5.1 which allows you to drive the animation speed using an animation parameter. This doesn't really go far enough in my view - it solves this particular problem, and will satisfy me in the short term, but I'd rather we could actually access the guts of the mecanim state machine at runtime and do what we will. Professional game developers don't like having their hands held and being told "no, that's not allowed.", particularly when it seems obvious that it should be.

No disrespect intended though: I love Unity and everything it represents and enables. This one issue with Mecanim does bug me though.

 

Hey @vanmani can you give a couple examples beyond the OP how having access to the state machine would be used in a practical manner?
Or possibly give a couple examples how this restricts the use of mecanim in the current build?

Thanks -
Please use small words - I'm an animator not a programmer.

 

Vanmani, you are 100% correct. I hope Unity fixes this asap!

Is there a timeframe on the release of 5.1?

 

vanmani - I reread your post and now understand the issue you have pointed out, and agree.