Search Issue Tracker
Fixed in Entities 0.17
Votes
0
Found in [Package]
0.7.0-preview.7
Issue ID
1266481
Regression
No
[Platforms] Build Configuration ignores Auto Load Scene option and does not load the selected scenes when running a build
How to reproduce:
1. Open user-submitted project (AutoLoadScene.zip)
2. Select either the WindowsClassicBuildConfiguration or the macOSClassicBuildConfiguration
3. Note that both configurations include two scenes, both scenes with Auto Load enabled
4. Build and run either build configuration
Expected result: both scenes are loaded upon running the build
Actual result: only the first scene is loaded upon running the build
Reproducible with: 2019.4.6f1(Platforms preview - 0.2.1, preview.5 - 0.4.0), 2020.1.0f1, 2020.2.0a19(Platforms 0.2.1-preview, 0.7.0-preview.7)
Could not test with: 2018.4.26f1(Platforms package unavailable), 2019.4.6f1, 2020.1.0f1, 2020.2.0a19(Platforms preview.1 - 0.2.0 - Auto Load option unavailable)
Notes:
Tested on macOS
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment