Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
5.6.0b5
Issue ID
875194
Regression
Yes
Undoing transform change of runtime-instantiated prefab causes transform hierarchy it belongs to to get disabled
Steps to reproduce:
1. Open attached project
2. Open scene "repro" and run it
3. Drag "Prefab" prefab to scene as a child of "GameObject"
4. Move created instance
5. Press ctrl+z and notice that prefab gets unparented and "GameObject" is disabled
Note: "GameObject" only gets disabled in Unity 5.6. On older releases object is still active - the unparenting, however, still happens. Also - this doesn't reproduce with "normal" prefab instances created using Instantiate.
Reproduced with: 5.4.0p2, 5.4.4p1, 5.5.1p1, 5.6.0b5
Not reproducible: 5.3.7p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
- Crash on OnDemandScheduler::HandleImportWorkerLogs when performing various Unity operations
Add comment