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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Add comment