Search Issue Tracker
Fixed
Votes
0
Found in
6000.0.35f1
6000.1.0b3
Issue ID
UUM-93746
Regression
Yes
Selecting and deleting transition in Animator does not add to Undo History when animation is previewed in Inspector
Steps to reproduce:
- Open a Unity Project
- Open Undo History via ctrl + u
- Move the Undo History Window to be somewhere visible during rest of steps
- Create a new Animator Controller via Assets > Create > Animation > Animator Controller
- Open the new Animator Controller in the Animator Window by double-clicking on the asset
- Create two Nodes via right-click > Create State > Empty
- Connect the two nodes together via a transition (right-click > Make Transition)
- Select the transition then delete it with del key
- Observe how both selecting and destroying the object is added to the Undo History. This is expected
- Undo the deletion (Ctrl + Z)
- Add any Animation to both the two states (HumanoidDefault is an animation that is in Unity by default. You will need to toggle package visibility to see this one))
- Ensure that the Inspector Window is visible (so you will be able to see the Animation Preview section) and select the transition
- Press del key to delete the transition
Actual results: Instead of 'Select' being added to the Undo History, it adds 'Add UniversalAdditionalLightData'. 'Delete' isn't added to the Undo History at all, instead it just removed the 'Add UniversalAdditionalLightData'. Pressing Ctrl + Z to Undo will not bring back the deleted transition.
Expected results: Both selecting and deleting the transition should appear in the Undo History when there is an Animation Preview in the Inspector upon selecting
Reproducible with versions: 6000.1.0b3, 6000.1.0b2, 6000.0.35f1
Not reproducible with versions: 7000.0.0a15, 6000.1.0b1, 6000.0.34f1, 2022.3.54f1, 2021.3.45f1
Can't test with versions: -
Tested on (OS): Windows 11
Notes: -
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-92601