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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment