Search Issue Tracker
By Design
Votes
0
Found in
2022.3.58f1
6000.0.40f1
6000.1.0b8
6000.2.0a5
Issue ID
UUM-98283
Regression
No
Animator "Conditions" tab breaks when the only Parameter is deleted and another one is created
How to reproduce:
1. Open the attached project "Test"
2. Open the "SampleScene" scene
3. Make sure to have the "Animator" tab opened and select the "Test1" GameObject in the Hierarchy
4. Select the transition between the "Test1" and "test1_2" animations
5. Click the "+" button to add a condition
6. In the Animator window, delete the parameter "test" and create another parameter
7. Select the Transition again and observe the Conditions tab
Expected results: The Conditions window shows only "Parameter does not exist in Controller"
Actual results: The Conditions window shows the empty dropdown and the warning at the same time
Reproducible with: 2022.3.58f1, 6000.0.40f1, 6000.1.0b8, 6000.2.0a5
Reproducible on: macOS Sequoia 15.3
Not reproducible on: No other environment tested
Note: When the only Parameter is deleted and another one is not added, the empty dropdown is not displayed
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
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
- Scene View Camera overlay preview goes out of Scene View bounds when the Scene View is resized vertically
Resolution Note:
This is expected when the only existing parameter is deleted and a new parameter with a new name is created. Although not ideal, given the limitations of the current UI used in this tool, it does behave as expected, as the new parameter is not assigned, but available. If you re-created the deleted parameter and create a new one with the same type & name, it will remap it automatically. Closing this issue as designed, since there is nothing “incorrect” or blocking in the current behaviour and changing this comes with an associated risk.