Search Issue Tracker
Won't Fix
Votes
3
Found in
5.3.1f1
Issue ID
786829
Regression
No
Name set using Undo.SetCurrentGroupName is reset after undoing Undo.DestroyObjectImmediate
Steps to reproduce:
1. Open attached project "786829.zip"
2. Open scene "repro"
3. In top menu, click "Test > Test Undo". This will call Undo.SetCurrentGroupName followed by Undo.DestrayObjectImmediate and will destroy Main Camera
4. In top menu, click "Edit" and notice "Undo Destroying (test)" option. Click it
5. Once again, click "Edit" and this time notice "Redo Destroy Object", click it
6. Click "Edit" again and notice "Undo Create Object", click it
7. Expand "Edit" again and this time "Redo Create Object" option is present
Reproduced with: 5.1.4f1, 5.2.4f1, 5.3.4p2, 5.4.0b14
-
helgewl
Oct 04, 2016 13:51
I am also experiencing this in 5.4.0f3.
The first undo renames the undo group to "Destroy Object", and the following redo renames it again to "Create Object".
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.