Search Issue Tracker
By Design
Votes
0
Found in
5.3.0f2
Issue ID
748334
Regression
No
Scene is not being unloaded in Awake using SceneManager.UnloadScene
Steps to reproduce:
1. Download and import attached project.
2. Drag and drop "SceneA" and "SceneB" into a hierarchy view.
3. Select "SceneA" and press play.
4. Notice that both scenes are still loaded into Hierarchy view.
Expected result: SceneB should be unloaded when started.
Actual result: SceneB is not being unloaded.
Reproduced on: 5.4.0a4, 5.3.0f3, 5.3.0f2, 5.3.0f1
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on mono_log_write_logfile when more than one copy of bee_backend is running
- NativeList<T>.ParallelWriter.AddNoResize() causes memory corruption when used in a [BurstCompile] IJobParallelFor on Web builds
- Realtime reflection probe changes light strength when removing light sources using URP WebGL
- Objects near the screen edge are not culled when using GPU Occlusion Culling
- InvalidCastException is thrown when hovering over a Tilemap with a saved Random Brush pick containing empty cells
Zendist
Nov 09, 2016 09:40
The status says By Design, but I could not find a reasoning for it in the documentation. Where is this design choice stated?
kjuanlu
Dec 21, 2015 11:30
SceneManager.sceneCount and SceneManager.GetAllScenes() don't not work as expected in Awake().