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
- [Android] Texture Compression default texture format is set to PVRTC when building via script BuildPipeline.BuildPlayer
- [Android][GameActivity] APK built with Development Build enabled gets flagged as having Malware
- Default name of manually created Global Light 2D GameObject differs from the one included in the initial project Scene
- Option for "Acceleration Structure Build Flags" cannot be toggled when Lightmaps have been Generated for a Mesh Renderer
- Lights in Batch keep resetting to 0 in the Light Batching Debugger when a new GameObject is created and the mouse cursor is hovered over the Inspector window
Add comment