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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
Add comment