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
- Undoing Animator Parameter name change breaks references to it
- Crash on BV4_OverlapBoxAll when moving in play mode
- Custom mesh water surface normal map fades out when Y Position increases
- Sprite renderer does not issue draw calls correctly when using SRP Batcher
- [Android] Flickering artifacts when using "ScriptableRenderer.EnqueuePass(RenderPassEvent.BeforeRenderingPostProcessing)" multiple times
Add comment