Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.0.65f1

6000.3.3f1

6000.4.0b3

6000.5.0a3

Issue ID

UUM-131460

Regression

No

Pasting or duplicating the states in the Animator changes the order on the overlapping states

Mecanim Animation

-

How to reproduce:
1. Create a new Unity project
2. In the Project window, right-click -> Create -> Animation -> Animator Controller
3. Open the created Asset
4. Create many states and make sure some of them overlap
5. Duplicate any of the states multiple times and observe the results

Expected results: The states are not being rearranged
Actual results: The last option is "Copy current StateMachine" without a space

Reproducible with: 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a3

Reproducible on: Ubuntu 24
Not reproducible on: macOS Tahoe 26

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team has decided to not address this issue. Since this issue is purely cosmetic and has absolutely no impact on the current functionality, users are not expected to overlap States in the state machine layout, the legacy Graph GUI presently being used for the State Machine graphs will eventually be replaced and the risk associated in changing this code, we have decided to not address this cosmetic issue. Thank you for your feedback and understanding.

    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 has decided to not address this issue. Since this issue is purely cosmetic and has absolutely no impact on the current functionality, users are not expected to overlap States in the state machine layout, the legacy Graph GUI presently being used for the State Machine graphs will eventually be replaced and the risk associated in changing this code, we have decided to not address this cosmetic issue. Thank you for your feedback and understanding.

    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.