Search Issue Tracker
Fixed in 5.4.0
Votes
1
Found in
5.3.4p1
Issue ID
787114
Regression
Yes
[MSE] Entering/exiting playmode makes Active Scene a Scene, which is on top of Hierarchy
Reproduction steps:
1) Open user's attached project
2) Import 2 scenes into hierarchy (SceneA and SceneB)
3) Make SceneB appear under SceneA in hierarchy
4) Make SceneB - "Active Scene"
5) Enter playmode
Expected result:
SceneB should remain "Active Scene"
Actual result:
"Active Scene" switches to SceneA
Note:
If in playmode you will mark "Active Scene" any other Scene (regardless was it done with Script or right mouse click > Set Active Scene) exiting playmode will make "Active Scene" SceneA (Scene which is on top of hierarchy view).
Regression happened from 5.3
Comments (1)
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
- 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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Ziflin
May 06, 2016 15:35
This is a pretty frustrating bug for anyone attempting to have a global/master scene that is loaded first. It also messes with the lighting as the active scene changes.