Search Issue Tracker
By Design
Votes
4
Found in
5.4.1p1
Issue ID
833860
Regression
No
SceneManager.LoadSceneAsync and Resources.LoadAsync disrupt one another when allowSceneActivation is set to false
STR:
1. Open "main" scene in the project
2. Play the scene
3. Observe the additive scene is not loading and object not instantiating
4. Switch scene and resource load lines with each other:
From:
m_ao = SceneManager.LoadSceneAsync("Stage", LoadSceneMode.Additive);
m_rr = Resources.LoadAsync<GameObject>("Model");
To:
m_rr = Resources.LoadAsync<GameObject>("Model");
m_ao = SceneManager.LoadSceneAsync("Stage", LoadSceneMode.Additive);
5. Observe the scene loading and object instantiating
Reproduced on: 5.3.6f1, 5.3.6p8, 5.4.1p1, 5.4.2f2, 5.5.0b9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment