Search Issue Tracker
By Design
Votes
0
Found in [Package]
0.8.6 - 1.1.10
Issue ID
1182127
Regression
No
Loading order of scenes with Addressables.LoadSceneAsync depends of how they are bundled up
Repro steps:
1. Open user attached project and "startScene"
2. Open Addressables window and set Play Mode Script to "Packed Play Mode" or "Virtual Play Mode"
3. In the same window, select Build and press "Build Player Content"
4. Enter Play Mode
Expected result: Scenes are loaded in the order they were declared (1, 2, 3, 4, 5)
Actual result: Scene1, from a different bundle than the main scene and other scenes, is loaded last (2, 3, 4, 5, 1)
Reproducible with: 2018.4.10f1, 2019.2.7f2, 2019.3.0b5, 2020.1.0a6
Could not test with: 2017.4.32f1 (no Package Manager)
Reproducible with package versions: 0.8.6, 1.1.7, 1.1.10
Could not test with package versions: 1.1.3, 1.1.4, 1.1.5 (errors)
Note: Scenes are loaded in order when the Play Mode Script is set to "Fast Mode"
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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
Resolution Note:
Addressables is an asynchronous system. Asynchronous implies that the fastest loading scene, loads first.