Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.3.3p1
Issue ID
774363
Regression
No
Quitting editor while in play mode will cause scenes loaded additively to persist on editor restart
Steps to reproduce:
1. Open attached project
2. Open scene "TestScene1"
3. Run it and press "A". This will additively add "TestScene2"
4. While still in play mode exit Unity
5. Reopen Unity and notice that both scenes are loaded although "TestScene2" was loaded in play mode
Reproduces with using both, Application.LoadLevelAdditive and SceneManager.LoadScene in additive mode.
So there are 2 workarounds:
1. Do not close the editor while in Play mode
2. If you do, remove the extra scenes when you restart the Editor
Reproduced with: 5.3.0b1, 5.3.3p1, 5.4.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment