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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment