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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment