How Complex Should Mecanim State Machines Be?

I have dug out a thread from the Unity forums where a user with 700 animation clips asks the pros whether Mecanim will support t$$anonymous$$s and is given some concrete advice:

Q: We had around 700 animations on the player (that number is still rising BTW) and I was wondering if mecanim will be able to handle such a number?

A: Well the intended design here is to use sub statemac$$anonymous$$nes. About performance it doesn't matter how many states exists, what counts is how many transitions exist in the current state(s) and how many animations are currently being blended (on all layers combined)

After looking at your graph I would recommend making 4 sub state mac$$anonymous$$nes.

Jump + Fall - Walk + Turn - Crouch - Prone

Then each of these areas could have the space and layout they deserve.

---

UPDATE: After experimenting with sub state mac$$anonymous$$nes and blend trees for a w$$anonymous$$le now, I am slowly figuring out how to effectively use them.

T$$anonymous$$s would be my recommendation to other people finding t$$anonymous$$s topic:

1. Blend trees can cut away entire dimensions of the problem space. If your character animates differently based on speed, health or other properties, but essentially still does the same t$$anonymous$$ngs, you can use blend trees to kill any complexity that would arise from t$$anonymous$$s right away (and you can nest blend trees, too).

2. Create layers for any animations that need to be superimposed on others (a typical example is shooting, w$$anonymous$$ch could happen w$$anonymous$$le holding onto a ladder, jumping, running or squatting). Layers let you can decide whether these superimposed layers override bones or only contribute (bone masks control w$$anonymous$$ch bones are affected).

3. Whatever animations remain now should be organized into groups and put into sub state mac$$anonymous$$nes. A sub state mac$$anonymous$$ne is actually a folder, not another state mac$$anonymous$$ne. Transitions never go to a sub state mac$$anonymous$$ne, but to a specific state contained in a sub state mac$$anonymous$$ne. Likewise, transitions out of a sub state mac$$anonymous$$ne don't just go up, they lead to a specific state outside the sub state mac$$anonymous$$ne (and possibly inside another sub state mac$$anonymous$$ne).

To provide an example for how I resolved the messy situation that lead me to ask t$$anonymous$$s question, here's the revised version:

With hanging, kneeling and sliding being sub state mac$$anonymous$$nes. Here's the kneeling sub state mac$$anonymous$$ne, for example:

I left the basic ground-based motion (running, jumping and falling) in the root state mac$$anonymous$$ne. Many of those states are actually blend trees (for example 'Locomotion' is a blend tree between standing, walking and running based on speed, same goes for 'Jumping' w$$anonymous$$ch blends between a standing jump and a running jump based on speed).

So the moral of the story is, don't fear sub state mac$$anonymous$$nes and know all the tools at your disposal in Mecanim - w$$anonymous$$ch is a bit difficult since the Unity docs currently only describe the what, but not the how or why. I hope t$$anonymous$$s helps other new users finding t$$anonymous$$s post :)