Search Issue Tracker
Fixed
Fixed in 6000.4.0a1
Votes
0
Found in
2022.3.64f1
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
6000.4.0a1
Issue ID
UUM-112096
Regression
No
Frame Debugger docked with the Game View can still be enabled when Game View is maximised and minimised
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open the Frame Debugger window (Window > Analysis > Frame Debugger)
- Dock the Frame Debugger window with the Game View
- Maximise the Game View
- Unmaximise/minimise the Game View
- Click on the Frame Debugger window
- Click the "Enable" button
- Observe the Frame Debugger window
Actual results: The Frame Debugger becomes enabled with no data, just an empty window
Expected results: The "Frame Debugger can not be docked with the Game Window when trying to debug the editor." error is thrown and the Frame Debugger is not enabled
Reproducible with versions: 2022.3.64f1, 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3
Not reproducible with versions: 2021.3.51f1 (due to different functionality/behaviour)
Tested on (OS): macOS Silicon Sequoia 15.5
Notes:
- There is an error thrown "Frame Debugger can not be docked with the Game Window when trying to debug the editor." when trying to enable the Frame Debugger before reproduction, stating that this is not the intended behaviour and it should not work, however, after maximising and minimising the Game View it allows the user to enable the Frame Debugger.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment