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

Mecanim Animation

-

Steps to reproduce:

  1. Create a new project using the Universal 3D template
  2. Create a new Cube GameObject (GameObject > 3D Object > Cube)
  3. Select the newly created Cube GameObject in the Hierarchy window
  4. Open the Animation window (Window > Animation > Animation)
  5. Dock the Animation window
  6. Create a new Animation
  7. Repeat step 6
  8. Make sure the second created Animation is selected in the Animation window
  9. Click the "Add Component" button in the Inspector window
  10. Click the "New Script" button
  11. Click the "Create and Add" button
  12. 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

  1. 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.

  2. 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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.