Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2018.4
2019.4
2020.2.7f1
2020.3
2021.1
2021.2
Issue ID
1323868
Regression
No
Loading multiple scenes additively loads them in random order than as seen in the Project Window
Reproduction steps:
1. Create a new project and import the attached custom package "Scenes.unitypackage"
2. In the Project Window select all Scenes and load them additively (Right-click -> Open Scene Additive)
3. Compare the loaded order in the Hierarchy Window with imported order in the Project Window
Expected result: Scenes loaded additively in Hierarchy Window have the same order as in the Project Window
Actual result: Scenes loaded additively in Hierarchy Window do not have the same order as in the Project Window (See attached Results.png)
Reproduces on: 2018.4.35f1, 2019.4.26f1, 2020.3.8f1, 2021.1.7f1, 2021.2.0a16
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
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
- Search Field breaks when deleting a Search Expression that has been converted to a Visual Query Block
- Outdated documentation page is linked when clicking on the Help icon for "Virtual Texturing" Module in Profiler Window
- [Linux] No “File already exists” pop-up thrown when saving Shader Variants with an already existing name from Build Profiles or Project Settings window
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a3