Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.5.0f3
Issue ID
606769
Regression
No
BlendTree is completely broken when changing the Compute Threshold parameter
BlendTree is completely broken when changing the Compute Threshold parameter to Speed.
To reproduce:
- Create a new project and import the "Mecanim Example Scenes" project from Asset Store
- Open the "Generic Skeleton Example" scene
- In Project Browser, go to Controllers folder and double-click on "MineBot" Animator Controller
- In the Animator window - double-click on "Locotion"
- Select the BlendTree
- Go to Inspector and un-tick the box for "Automate Thresholds"
- On "Compute Thresholds", select Speed from drop down menu
- Observe that the BlendTree is now in an unusable state
Please see attached screen shot for details.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Reflection Probe" borders disappear when interacting with the UI in the Inspector and one of the Reflection Probe editing tools is selected during the Baking process
- RenderGraph ContextData buffer leaks in IL2CPP when using Native Leak Detection
- Caret in "Add Default Preset" text field is vertically misaligned in Preset Manager
- Unused separation line is present at the bottom of the create GameObject sub menu when right clicking Scene in the Hierarchy
- Text cursor and text highlighting is misaligned and cut off in the search bar when typing something and highlighting text in the "Add Default Preset" window
Add comment