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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.