Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2020.2
2020.2.0b1
Issue ID
1275898
Regression
No
Child GameObject is moved to an active Scene when the child GameObject's parent is set to null
Child GameObject is moved to an active Scene when setting the child GameObject's parent to null and the current parent GameObject is deactivated
How to reproduce:
1. Open the user's attached "transform-parent-repro.zip"
2. Open the "SampleScene" Scene
3. Go to Bug Repro -> This does not work
4. Observe the Hierarchy window
Expected result: One activated GameObject and one deactivated GameObject is created in the "SampleScene" Scene
Actual result: Only the deactivated GameObject is created in the "SampleScene" Scene (Child GameObject was moved into a different Scene)
Reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
Note:
- The issue is not reproducible if the child GameObject is inside an activated parent GameObject
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note (fix version 2020.2):
Fixed in: 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b5