Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.5.X
Votes
0
Found in
6000.4.0a4
6000.5.0a2
Issue ID
UUM-126467
Regression
No
[FrameDebugger] Maximizing and Minimizing the window does not remove the FrameDebugger requirement Error
Steps to reproduce:
- Download attached project and open in Unity.
- Open the Frame Debugger and dock it.
- Maximize the FrameDebugger window.
- Observe: the Error in the Frame Debugger window "Frame Debugger requires at least one available Game/Play Mode window."
- Now, disable "Maximize" the Frame Debugger window.
- Observe: The error stays, unless the Frame Debugger window is refreshed/interacted with the Enable button.
Actual results: The error is displayed, even though the window is not maximized anymore, and the Play window is visible/ open.
Expected results: The Error should disappear once the window is not Maximized anymore.
Reproducible with versions: 6000.4.0a2, 6000.4.0a4, 6000.5.0a2
Could not test with versions: 6000.3.0b9, 6000.4.0a1 (no error appears when maximizing the Frame Debugger window)
Tested on (OS): MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS: 15.5
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note:
Not reproducible in 6000.5.0a5
Resolution Note (6000.5.X):
Not reproducible in 6000.5.0a5