Search Issue Tracker
By Design
Votes
0
Found in
2022.3.66f1
6000.0.57f1
6000.2.4f1
6000.3.0b1
Issue ID
UUM-117123
Regression
No
Frame Debugger gets disabled when any Editor window is maximised and minimised
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open the Frame Debugger window by pressing the Frame Debugger button in the Game View toolbar
- Dock the opened Framed Debugger window next to the Game View
- Maximise and minimise any Editor window
- Observe the Frame Debugger
Actual results: Frame Debugger is disabled
Expected results: Frame Debugger remains enabled
Reproducible with versions: 2022.3.66f1, 6000.0.57f1, 6000.1.16f1, 6000.2.4f1, 6000.3.0b1
Tested on (OS): macOS Silicon Sequoia 15.6.1
Notes:
- Reproduces with any Editor window, Game View and Frame Debugger windows included
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Thank you so much for reaching out and taking the time to report this issue. After careful review, we can confirm that the behavior you described is currently expected within the system’s design. However, we understand this may not be ideal in all situations. Thank you again for helping us make Unity better!