Search Issue Tracker
Fixed in 2022.1.X
Votes
4
Found in
2018.3.0a6
2018.3.4f1
2019.1.0a1
2019.2.0a1
Issue ID
1127653
Regression
No
Prefab Variant Child has a lower Index than a Prefab Child when editing a Prefab while Prefab Variant is not in the Project
Steps to reproduce:
1. Open the attached Project "case_1127653"
2. Navigate to Project -> Assets
3. Create a Variant of a "Base Prefab" with coloured Image as a child
4. Move the Prefab Variant out of the Project
5. Add a child to the "Base Prefab" that has a coloured image
6. Move the Prefab Variant back to the Project
7. Open the Prefab Variant
8. Notice how the Child of the Prefab Variant has a lower sibling index compared to Original Prefab child
Expected results: Variant of a Prefab has the highest sibling index
Actual results: Child of the Original Prefab has the highest sibling index
Reproducible with: 2018.3.0a6, 2018.3.7f1, 2019.1.0b4, 2019.2.0a6
Note: Improved Prefabs appeared in 2018.3.0a6
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2022.1):
GameObjects added to a prefab instance, which are added after the prefab's children, will remain after the prefab's children even after new children are added to the prefab