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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment