I think Unity wins the ‘worst documentation ever’ prize. I hereby yank it from old Microsoft MSDN documentation, and award it to Unity.
There needs to be instructions such as ‘where is this found in the UI’, ‘what package it is in’, ‘what the namespace is’, ‘what the object hierarchy is.’ In addition to information about each setting itself.
Here’s an example of piss-poor documentation: Unity - Manual: Animation transitions .
All the documentation says, is ‘The following properties can be used to adjust the transition and how it blends between the current and next state (the two states connected by the transition).’
Has Exit Time
Settings
Exit Time
Transition Duration
Transition Offset
Interrupt Source
None
Current State
Next State
Current State then Next State
Next State then Current State
Ordered Interruption
There’s no description of what ANY of those mean - ‘Has Exit Time’, ‘Exit Time’, any of it.
FYI, per Mixamo, here’s what ‘Exit Time’ and ‘Has Exit Time’ means:
Exit Time (Unity 4) The exit time is a percentage of the animation that you want to complete before automatically transitioning to the next animation. For example, you can transition to Animation A, tell the animation to complete 90% (0.90 exit time) and then automatically transition to Animation B.
Has Exit Time (Unity 5) In Unity 5, Mecanim is a little different. Instead of using Exit time as a parameter it has instead “Has Exit Time”. If “Has Exit Time” is true AND no parameter based conditionals are set, then the animation will transition after exit time. If “Has Exit Time” is true and parameter based conditionals are set, Mecanim will wait for the conditionals to become true, then continue playing until the exit time is complete, and then transition. If you want to have your animation transition instantly leave “Has Exit Time” to false and use a parameter based conditional.
Now that’s an example of proper documentation. The time wasn’t in seconds, or milliseconds, or frames, like you may have guessed - it’s percentage of animation you want to complete.
And I’ve found the documentation lacking, for most of the stuff I’ve tried to look up.
The more I use Unity, the more in awe I am. It’s a great product. The documentation is REALLY letting it down, and hurting newcomers to the engine.