Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2020.3
2021.2
2021.2.0f1
2022.1
Issue ID
1385025
Regression
No
Some GameObjects ignore the Default Parent when creating them in the Hierarchy
Reproduction steps:
1. Open the attached project "Case_1385025" and load Scene "SampleScene"
2. In the Hierarchy, right-click the "DefaultParent" GameObject and select "Set as Default Parent"
3. In the Menu Bar select "GameObject -> UI-> Canvas"
4. Observe the Scene's Hierarchy
Expected result: GameObjects are created with the "DefaultParent" as its parent
Actual result: GameObjects with no parent GameObject are created
Reproducible with: 2020.3.24f1, 2021.2.5f1, 2022.1.0b1
Not reproducible with: 2019.4.33f1 (Set as Default Parent not available)
Notes:
- Examples of GameObjects that do not respect the Default Parent option:
- Any GameObject under UI in the GameObject menu
- UI Document
- Terrain
- WindZone
- Tree
- Any GameObjects under Cinemachine in the GameObject menu
- GameObject created in Scripts via "new GameObject()" or "Instantiate()";
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
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
- Artifacts appear on GameObjects when using the WebGL Player on Silicon macOS
- Only the icon of the disabled child GameObject is faded when a parent GameObject is a Prefab
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a17