Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.68f1
6000.3.10f1
6000.4.0b9
6000.5.0a7
Issue ID
UUM-134844
Regression
No
Selected Animation clip in the Animation window changes when the Domain Reload is triggered
Steps to reproduce:
- Create a new project using the Universal 3D template
- Create a new Cube GameObject (GameObject > 3D Object > Cube)
- Select the newly created Cube GameObject in the Hierarchy window
- Open the Animation window (Window > Animation > Animation)
- Dock the Animation window
- Create a new Animation
- Repeat step 6
- Make sure the second created Animation is selected in the Animation window
- Click the "Add Component" button in the Inspector window
- Click the "New Script" button
- Click the "Create and Add" button
- Observe the selected Animation in the Animation window
Actual results: The first created Animation is now selected in the Animation window
Expected results: The previously selected Animation is still selected (second created Animation)
Reproducible with versions: 6000.0.68f1, 6000.3.10f1, 6000.4.0b9, 6000.5.0a7
Tested on (OS): MacOS Silicon Tahoe 26.2, Ubuntu 24.04
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
- GameObjects made using "GameObject.CreatePrimitive" appear pink in the Player when the default material is used
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.