Search Issue Tracker
Fixed
Fixed in 6000.0.56f1, 6000.2.1f1, 6000.3.0a5
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.4f1
6000.2.0b2
Issue ID
UUM-107494
Regression
No
Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Steps to reproduce:
- Open any Project
- Create an Animator and open it
- Create a Blendtree and double click it
- Select the Parent Blendtree State
- In the Inspector click the "+" icon near the Motion list and add a Motion
- Now make sure "Automate Thresholds" is checked and add a couple more Motions and observe Thresholds
- Remove Motion entries until only the first one with a Threshold of 0 is left
- Add more Motions
Actual results: After removing all Motions except the first Motion with a Threshold of 0 and then adding new Motions new Thresholds are not automatically calculated when "Automate Thresholds" is checked
Expected results: Motion Thresholds are automatically calculated whenever "Automate Thresholds" is checked, no matter the amount of entries in the Blendtree Motion list
Reproducible with versions: 2022.3.62f1, 6000.0.50f1, 6000.1.4f1, 6000.2.0b2
Tested on (OS): Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Open” button in Inspector does not function for certain Assets
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
Add comment