Search Issue Tracker
By Design
Votes
0
Found in
2017.1
2018.1
2019.1
2019.2
2019.3
2020.1
2020.2
2020.2.0a5
Issue ID
1230836
Regression
No
[Animation] Compute Thresholds parameter does not get selected in Blend Tree
BlendTree is completely broken when changing the compute Threshold parameter. Unable to select any value from Compute Thresholds dropdown.
Steps to repro:
1. Open the attached project.
2. Open Cube Animator > Double click on "Test" Blend Tree.
3. Select BlendTree and add two motion field from the Inspector.
4. Uncheck Automatic Thresholds checkbox.
5. Select any parameter from Compute Thresholds dropdown.
Actual Result:
Unable to select any value from  Compute Thresholds dropdown.
Expected Result:
Able to select the value from Compute Thresholds dropdown.
Reproducible in:
2020.2.0a5, 2020.1.0b3, 2019.3.3f1, 2019.2.1f1, 2019.1.1f1, 2018.1.0a1, 2017.1.5f1.
Environment:
Occurring on Windows 10 & Mac 10.14.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
Resolution Note:
This pull-down is an action based on assigned clips. If you have no clips assigned, the expected result is null.
The Compute Thresholds drop-down will set the thresholds from data of your choice obtained from the root motions in the Animation Clips.
See documentation for more detailed explanation… https://docs.unity3d.com/Manual/BlendTree-1DBlending.html