Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0p4
Issue ID
947402
Regression
No
Loading scene with SceneMode.additive cancels allowSceneActivation = false set for an Async scene
To reproduce:
1. Open attached Unity project "SceneLoadingBugDemo.zip"
2. Open "Scene1" scene
3. Go into Play mode
4. Observe results
5. Observe "TestScript" script
Expected results: Scene3 should be added to Scene1 5 seconds into the game and leave Scene2 90% loaded, waiting to be activated
Actual results: Adding Scene3 to Scene1 ignores allowSceneActivation=false previously set for the Scene2 and so it loads, resulting in active Scene2 and Scene3 as its additional scene.
Reproduced on: 5.6.3p2, 2017.1.1f1, 2017.2.0b10, 2017.3.0a7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Expendable property in Inspector Window collapses when an item is added to the property's list
- Unity Editor Preferences window menu labeled "Settings" on macOS devices
- Default value in the Script is not assigned when applying the UI Toolkit ObjectField
- Private field value assignment via Script is not applied when you enter the Play Mode for the first time after the change
- There is an ability to switch to VisionOS module even though the installation of the module has failed
Add comment