Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131787
Regression
No
'EditorSceneManager.sceneCount' reports the wrong count when called by an 'EditorSceneManager.sceneClosed' event
How to reproduce:
- Open the “SceneCountBug.zip“ project
- Open the “SampleScene“ and observe the Console
- Open the “SampleSceneExtra“
- Observe the Console
Actual result: “Scene Closed: 2” is logged
Expected result: “Scene Closed: 1” is logged
Reproducible in: 2023.1.0a1, 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Notes:
- This also happens when an additively added scene is removed
- EditorSceneManager.sceneClosed event should be called after changing scenes. Therefore, the sceneCount should always return “1“
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Create and publish WebGL builds” link leads to “Sorry about that, we can't find the page you're looking for.” page
- " Suspected crash in FXC. " shader compiler errors are thrown in a new project when creating a project in Hub with a very long name but below the maximum character threshold
- Long cloud names stretch the space in Hub when the Project dropdown is opened
- OpenGLES3 Graphics API can be used with the "Linear" Color space on unsupported GPUs resulting the error spam
- [Windows] Recommended and Downloaded Learn tabs are empty and have scrollbar
Add comment