Search Issue Tracker
Fixed in 5.1.0
Votes
0
Found in
5.1.0b5
Issue ID
693372
Regression
No
Direct blend tree "Normailze Blend Values" does not normalize
1. What happened
Enabling "Normalize Blend Values" on a direct blend tree, does not normalize blend(s).
2. How we can reproduce it using the example you attached
Select the "AnimController" controller
In the Animator, enter the Blend Tree
you should see 3 motions assigned to the tree
the first set to 0
the second set to 0.5
the third set to 0
select the tree and press play in the Inspector preview... you should see half of the walk motion being applied, as expected.
Now, in the Inspector, enable "Normalize Blend Values"... the motion still represents half the walk motion, bad :(
expected result: The walk motion should be applied at 100% when normalized since the other motions are set to 0.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment