Search Issue Tracker
Fixed
Votes
0
Found in
2017.4
2019.3.0f1
2020.1
Issue ID
1206399
Regression
No
Detaching child objects of inactive Game Object causes them to appear in root Scene when Additive Scenes are present
How to reproduce:
1. Open the "ParentTest.zip" project
2. Open scenes "SceneA" and "SceneB" additively
3. Repro > Set References
4. Disable the "Parent" GO in SceneB
5. Repro > Detach Children or Repro > Set null Parent
Actual result: The "Child" object appears in SceneA.
Expected result: The "Child" object stays in SceneB.
Reproducible with: 2017.4.36f1, 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18.
Notes:
- The issue is reproducible with both transform.DetachChildren() and transform.SetParent(null) methods.
- The issue only reproduces when the "Parent" object is deactivated and "Child" object is active.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment