Search Issue Tracker
By Design
Votes
1
Found in
5.5.1p2
Issue ID
877706
Regression
No
Can't unload previous Scene, on the same frame when new Scene is Loaded with LoadSceneAsync
To reproduce:
1. Open attached project "UnloadSceneAsyncBug"
2. Open "loaderWorking" scene and Play it.
3. Press "SCENE 1" button in Game window. "loaderWorking" scene is destroyed, because we waited 1 frame.
4. Stop Play mode.
5. Open "loader" scene and Play it.
6. In Game window press "SCENE 1" button. Loader scene is not unloaded.
Expected result: When new scene is loaded asynchronously, other scene can be unloaded.
Actual result: After new scene is loaded asynchronously, previous scene can be unloaded only in the next frame.
Reproducible with: 5.4.4p4, 5.5.1p3, 5.6.0b10
Workaround:
Wait one frame to unload scene.
Notes:
It happens because Unity thinks, that scene which we try to unload is still the only scene.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
Add comment