Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.24f1
2023.2.18f1
6000.0.0b14
Issue ID
UUM-68747
Regression
No
GameObject does not get assigned a Parent when Instantiated in Edit Mode
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “<path>/BasicDemo” Scene
3. In the Building Loader window (BuildingManager > Tools > BuildingLoader), paste the PersistedDataLine in Persisted Data text field
4. Set the Parent field to “Map/Buildings“ GameObject from the Hierarchy
5. Open the Container field Object Picker and select “Container_2.5”
6. Press “Load” button
7. In the Hierarchy window, observe the created “Map/Buildings/Building” GameObject and “DemoFloor_2.5(Clone)” GameObject
Expected result: The “DemoFloor_2.5(Clone)” GameObject is created as a child of the “Building” GameObject
Actual result: The “DemoFloor_2.5(Clone)” is created separately, with no parent
Reproducible with: 2022.3.24f1, 2023.2.18f1, 6000.0.0b14
Couldn't test with: 2021.3.37f1 (compilation error because of missing API)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: If step 6 is done while in Play Mode, the results are as expected
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.