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
- “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