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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2020.2):
Fixed in: 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b5