Search Issue Tracker
Fixed
Fixed in 6000.0.52f1, 6000.1.8f1, 6000.2.0b6, 6000.3.0a1
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.5f1
6000.2.0b4
Issue ID
UUM-107878
Regression
No
Warnings thrown when computing Positions in a 2D BlendTree are not helpful to the user
Steps to reproduce:
- Create a Project and import the attached Asset package
- Open the Animator "v2Animator"
- Double click the BlendTree "Running BlendTree"
- Select child BlendTree "Run" or "Walk"
- In the Inspector, select the option "Speed and Angular Speed" under dropdown menu for "Compute Positions"
Actual results: Warnings like "Can't distribute the motions of 'Walk', they all have the same threshold value.
UnityEditor.GenericMenu:CatchMenu (object,string[],int)" are logged in the Console for each Motion in the BlendTree
Expected results: Users are indicated why the operation cannot be completed, currently they are only informed that the motions "Have the same threshold value", but Thresholds are calculated and set in a 1D Blend Type BlendTree, this does not bring any clarity to our users
Reproducible with versions: 2022.3.62f1, 6000.0.50f1, 6000.1.5f1, 6000.2.0b4
Tested on (OS): Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
Add comment