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
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
- [MacOS] NaN value appears in a shader when using the EmissionTint parameter property that is not properly initialized
- Crash on mono_class_inflate_generic_method_full_checked when accessing static properties or methods of a Generic Interface in a Generic Class
- Crash on RendererScene::NotifyInvisible when switching QualitySettings of the HDRP pipeline asset in a specific project
- Compute and graphics queues are not run asynchronously when asynchronous compute shaders are enabled in DX12
Resolution Note:
Addressables is an asynchronous system. Asynchronous implies that the fastest loading scene, loads first.