Mecanim "Any State"

Mecanim's "Any State" state seems to be ideal for implementing things like death sequences, which can start from anywhere.

However, tying the transition to the state of a boolean (or a specific integer or float value, etc) causes the same state transition to be triggered over and over again, and thus the animation restarts repeatedly as long as the boolean has the same value.

Is there a way of preventing retriggering subsequent transitions to the same state? Or is the [simplistic] intended usage pattern simply to quickly revert the boolean to its original value? If so, how quickly? In the same or next frame?

 

Thanks for the reply, it's as I thought, then.

I wouldn't prevent re-entrant state transitions globally. It would be very useful with a checkbox to do so locally, however.

The above code fragment of course works very nicely, but it involves global monitoring of states, which distributes logic while still maintaining coupling. Would a simple

suffice? Or do we need to do

to create an animation event?

Another thing that would be very useful is ping states, i.e. states that after completion always transition back to the previous state. This tends to simplify logic a great deal in many situations.

 

I've bumped into this issue as well. While having an option to be re-entrant would be great, an alternative solution could be found.

Other node based animation systems I've used had a Request feature. Instead of using a bool, you could send "request" for an action. If the request is not present in any of the transition, no transition occur.

Here's a screen of how I imagine it working.