Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.14f1
2018.4.14f1
2019.2
2019.3
2020.1
Issue ID
1213361
Regression
Yes
Children prefab objects are re-ordered when updating Project from 2018.4.13f1 (the latest) to a newer version
How to reproduce:
1. Open the attached 'project-1213361.zip' project (using 2018.3.14f1)
2. In the Hierarchy window expand 'Environment' > 'BrokenChildrenHere'
3. Observe the order of the children prefabs
4. Open the project using a newer version (from 2018.4.14f1)
5. In the Hierarchy window expand 'Environment' > 'BrokenChildrenHere'
6. Observe the order of the children prefabs
Expected result: prefabs are placed in the same order
Actual result: prefabs are re-ordered
Reproducible with: 2018.4.14f1, 2018.4.16f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a20
Not reproducible with: 2018.4.0f1, 2018.4.13f1
Could not test with: 2017.4.36f1 (Prefab's break)
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
This is a duplicate of issue #1213249