Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0f2
Issue ID
1041899
Regression
No
Blend Trees give non-linear root motion and blending when linearVelocityBlending is set to true using Mecanim
How to reproduce:
1. Download project from OwnCloud and open it ("case_1041899_playables.zip")
2. Select object "Test", set "Mecanim Linear" to true and "Speed" to "0.5".
3. Press play
4. Inspect the velocity of Z axis in "Test" object's inspector.
Mecanim - ~0.5
Animancer - ~0.8 (user's plugin)
Playables - ~0.8
5. Now change the "Speed" to "1".
6. Inspect the velocity of Z axis in "Test" object's inspector.
Mecanim - ~1.6
Animancer - ~1.6 (user's plugin)
Playables - ~1.6
Expected result: Mecanim's Blend Trees give linear root motion.
Actual result: Mecanim's Blend Trees give non-linear root motion.
Reproducible with - 2018.3.0a3, 2018.2.0b10, 2018.1.7f1, 2017.4.6f1
Not reproducible with - 2017.2.3f1, 2017.1.4f1 (errors because of user's plugin Animancer)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
After a long investigation and discussion, the developers decided, sadly, to deprecate LinearVelocity Blending because it had tons of issues and was not working properly.