Search Issue Tracker
Fixed in 5.6.0
Votes
1
Found in
5.3.3p3
Issue ID
777936
Regression
No
[BlendTree] Modifying top bound of 1D parameter calculates threshold incorrectly
Steps to reproduce:
1. Download and import attached project.
2. Open scene: main
3. Select obejct in hierarchy: cube
4. In animator window, double click on "new state" to enter its Blend Tree.
5. Select blend tree and in inspector window try to change top bound from 10 to 5. (GIF)
Expected result: Bound changes to 5, and two bottom motion threshold also changes to 5.
Actual result: Bound changes to 5, but there is no motion with threshold of 5 (it is 1.666..), which is incorrect.
Notes: this only happens when we have two motions with the same threshold at top or min bounds.
Reproduced on: 5.4.0b9, 5.3.3p3, 5.2.4f1, 5.1.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][Vulcan] "UNITY_DISPLAY_ORIENTATION_PRETRANSFORM" is always 0 when the render pipeline is URP
- Editor loads for a long time when doing an Undo action in a large Shader Graph
- Memory leak when building AssetBundles
- [Asset Bundle] AudioSource output field not staying connected correctly when loaded from Asset Bundle
- [Android] Duolashock4 controller is not detected after disconnecting and reconnecting controller while the Player is running in the background
Add comment