Search Issue Tracker
By Design
Votes
2
Found in
2017.1.0f3
Issue ID
995895
Regression
No
Scene.GetRootGameObjects in standalone build returns differently ordered list than in the Editor
To reproduce:
1. Open the project, attached by the user (GetRootGameObjectsBug.zip)
2. Open the "1" scene
3. Enter Play mode and observe the ordering of the list
4. Build the project for PC standalone
5. Open the build and observe the order of the list
Expected: the objects list returned by GetRootGameObjects method is ordered the same in the Editor and in the standalone build
Actual: in the Editor the returned list of the objects is ordered the same as the objects are in the Hierarchy, in the build the returned list of the objects is ordered not the same as they are in the Hierarchy
Reproduced in 5.6.5f1, 2017.1.0f3, 2017.2.1p3, 2017.3.1f1, 2018.1.0b6
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:
DOTS Scene format will address this