Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.66f2
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133658
Regression
No
Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
Steps to reproduce:
- Open the attached project
- Open the SampleScene
- Enable Frame Debugger (Window -> Analysis -> Frame Debugger)
- Switch to the Project tab (This hides the Frame Debugger window)
- Switch to test Scene
- Observe in the Game view that frame debugging is still active
- Switch back to the SampleScene
Actual results: Frame Debugging is still active, Game view is rendered in a non-finished state (Frame Debugger isn't set to the Final render event)
Expected results: Frame Debugging is disabled when switching Scenes
Reproducible with versions: 6000.0.66f2, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Tested on (OS): macOS 26.2, Windows 11
Notes:
- If the Frame Debugger window is open (Either as a floating window or an active docked window) during the Scene transition, frame debugging will be disabled on Scene switch
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.