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
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.