Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
2
Found in
2018.4.0f1
2018.4.6f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1185434
Regression
No
An object created via "Create Empty Child" of Hierarchy panel in Prefab Mode is always a child of the main prefab
How to reproduce:
1. Open attached project "CreateChildInPrefabMode.zip"
2. In Project window, open "Assets" -> "Parent" prefab
3. In Hierarchy window, highlight "Child2" object
4. In Hierarchy window, press on "Create" -> "Create Empty Child"
5. Observe newly created child position in the hierarchy
Expected result: the newly created object is a child of "Child2" object
Actual result: the newly created object is a child of "Parent" object
Reproducible with: 2018.4.9f1, 2019.2.7f2, 2019.3.0b4, 2020.1.0a5
Could not test with 2017.4 (old prefab system)
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a24
Resolution Note (fix version 2019.3):
Verified in: 2019.3.8f1
Resolution Note (fix version 2018.4):
Verified in:
Version 2018.4.23f1