Search Issue Tracker
Fixed
Fixed in 2021.3.39f1, 2022.3.31f1, 6000.0.3f1
Votes
3
Found in
2021.3.37f1
2022.3.24f1
2023.2.18f1
6000.0.0b14
Issue ID
UUM-68642
Regression
No
Duplicates of the previously outgoing transitions are created in the AnimatorController file when duplicating an Animator State
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/AnimatorController“ AnimatorController with a text editor application
3. Search for “AnimatorStateTransition“ in the text editor application
4. Observe the amount of “AnimatorStateTransition“ in the text editor application
5. Open the “Assets/AnimatorController“ AnimatorController in the Editor
6. Copy the “State 2” State in the Animator window
7. Paste the State in the Animator window
8. Save (File > Save)
9. Repeat steps 2, 3, 4
Expected result: The same amount of “AnimatorStateTransition“ is found in the AnimatorController file
Actual result: There is an additional “AnimatorStateTransition“ in the AnimatorController file
Reproducible with: 2021.3.37f1, 2022.3.24f1, 2023.2.18f1, 6000.0.0b14
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Notes:
Deleting the duplicated State in step 7 does not delete the additional “AnimatorStateTransition“ created in the Animator Controller file
Repeating the reproduction steps keeps creating new additional “AnimatorStateTransition“ in the Animator Controller file
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment