Location: Assets/Plugins/Animancer/Examples/09 Animator Controllers/02 3D Game Kit
Various Pro-Only Features are used in this example: custom Fade durations, custom end times, Controller States. You can try them out in the Unity Editor with Animancer Lite, but they are not available in runtime builds unless you purchase Animancer Pro.
Unfortunately, licensing restrictions (and file sizes) prevent the assets used by this example from being included with Animancer so in order to actually see it in action you will need to:
- Create a new Unity project using Unity 2019.3+ (older versions may also work if you can complete step 3).
- Import the 3D Game Kit Lite.
- Fix any compiler errors you get from the packages it sets up. Often you can just open the Window/Package Manager and update anything causing errors, but you may need to search the errors online to see how other people solve them.
- Import Animancer.
Otherwise you will only be able to read through this documentation and the example scripts.
The example scene contains both the Mecanim character and the Animancer character so you can swap between them for comparison (it starts with Animancer by default).
The Mecanim character is based around a single Animator Controller:
There are 8 main states the character can be in:
The Animator Controller contains a few
StateMachineBehaviours on certain states, but it is mostly controlled by the
PlayerController component. This is a poorly designed setup because even though it uses the concept of a Finite State Machine, it still violates the Single Responsibility Principle by keeping the individual logic of all states in that one huge class instead of separating their concerns into multiple scripts. The practical problems this causes are explained later on in their relevant sections.
Animancer instead uses a code based Finite State Machine with a central
Creature script and a separate
CreatureState class for each of those states like in the State Machines examples. Many of the states directly reference their
AnimationClips while some of them use Mixers or play their own invididual Animator Controllers containing a single Blend Tree each.
The key difference between
Creature is that the former is responsible for managing everything the character can do while the latter is only responsible for things common to multiple states like gravity and turning. For example, if you want to know what is involved in the Animancer's
AirborneState, you can go to that script to see what it does. But if you want to know what is involved in the Mecanim
AirborneSM, you need to examine the Animator Controller and also find the
OnAnimatorMove methods which contain logic for input blocking, attacks, movement, turning, audio, and a time out to idle. Most of those things aren't relevant when the character is in the air, but you cannot be sure of that without going through them all so it would be very much harder than necessary to find and fix any bugs or add new functionality to the character.
|Problems with the Mecanim Character||The character implemented here is directly based on the player character from the 3D Game Kit, but it is not an exact copy because the Mecanim character had several problems which we want to avoid.|
|Respawn||Stand up on startup and after dying.|
|Idle||Stand still and randomly play a selection of other animations if you get bored.|
|Locomotion||Use a Blend Tree with Root Motion to walk around, as well as some additional animations for quick turning.|
|Airborne||Jump and fall using a Blend Tree based on your vertical speed.|
|Landing||When you touch the ground after being Airborne, play a landing animation depending on how fast you are going.|
|Attack||Attack using several different animations to form a combo.|
|Flinch||Getting hurt by an enemy interrupts your other actions and plays an appropriate reaction animation based on the direction of the attack.|
|Die||Taking too much damage causes you to die, then respawn back at the start.|