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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment