Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0p4
Issue ID
972744
Regression
No
Changes to object selection do not invalidate Redo action
To reproduce:
1) Open attached project and scene (You can easily create the scene with two cubes from scratch, but this would ensure that you have nothing in Undo/Redo memory)
2) Select Cube A in hierarchy
3) Change its Transform X to 1
4) Undo this
5) Select Cube B in hierarchy
Expected: Redo invalidates and gets deleted/forgotten
Actual: Redo stays at the same step. If you try redoing, it changes the transform of Cube A back to X = 1, without changing any selections or other things.
Reproduced in 5.3.5f1, 2017.1.0p5, 2018.1.0a7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment