Search Issue Tracker
Fixed in 5.0.1
Votes
0
Found in
5.0.0b21
Issue ID
665452
Regression
No
Content issues in Mecanim FAQ
Content issues in Mecanim FAQ
Unity 5.0.0b21/Editor/Data/Documentation/en/Manual/MecanimFAQ.html
"We are using the legacy animation system for character animations. Should we be using Mecanim instead?
Mecanim is the main animation technology that will be used and developed by Unity from now on. The legacy system will not be updated significantly."
The question is not really answered. Give a decisive answer such as the answer given in section on Legacy animation system:
“Prior to the introduction of Mecanim, Unity used its own animation system and for backward compatiblity, this system is still available. The main reason for using legacy animation is to continue working with an old project without the work of updating it for Mecanim. However, it is not recommended that you use the legacy system for new projects.”
"Is there a way to create AvatarIKGoals other than LeftFoot, RightFoot, LeftHand, RightHand?
This feature is planned for a future release."
We now have also the knee and elbow IK in 5.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment