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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note:
Addressables is an asynchronous system. Asynchronous implies that the fastest loading scene, loads first.