Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
1
Found in
5.5.0p3
2019.3.0b5
2020.2
Issue ID
895240
Regression
Yes
Copy/Pasting multiple Game Objects to a different Hierarchy level randomizes their pasted order
Steps to reproduce:
1. Open the attached "case_1275324.zip" project and SampleScene scene
2. Select nested Game Objects (Node (1) - Node(9))
3. Copy selected Game Objects
4. Select the parent Game Object WorldGraph
5. Paste the Game Objects
Expected Result: Game Objects are pasted with the same order
Actual Result: The order of the Game Objects is randomized
Reproducible with: 2019.3.0b5, 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
Not reproducible with: 2018.4.27f1, 2019.3.0b4
Comments (1)
-
JohnnyFactor
Aug 29, 2022 05:59
This is still occurring in 2020.3.38
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2021.1):
Verified in: 2020.1.0a1
Resolution Note (fix version 2020.2):
Verified in: 2020.2.0b8
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.10f1
Resolution Note (fix version 2019.4):
Verified in: 2019.4.14f1