Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.4.0f3
Issue ID
825237
Regression
No
[MSE] Scene management is not initialized when OnEnable is called for Editor windows on starting Unity
How to reproduce:
1. Open the attached project and notice two scenes are open.
2. Clear the console and close "Windowm8" window if it's opened.
3. Open "Windowm8" window again (Window -> Scene Management) and notice three console logs with the scene count of two.
4. Save the project and exit.
5. Open the project again and notice that three messages in the console now saying only one scene is open.
Expected behavior: Scene management always initialized when OnEnable is called.
Actual behavior: Scene management is not initialized when OnEnable is called for Editor windows on starting Unity.
Reproducible: 5.3.5f1, 5.3.6p3, 5.4.0p2, 5.5.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment