Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.66f1
6000.0.57f1
6000.2.4f1
6000.3.0b1
Issue ID
UUM-117121
Regression
No
The "Open Frame Debugger" button in the Game View toolbar not only opens the Frame Debugger window but toggles between enabling/disabling the Frame Debugger when pressed
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
- Repeat step 2
- Observe the Frame Debugger window
Actual results: The Frame Debugger is disabled by pressing the "Open the Frame Debugger" button in the Game View.
Expected results: The Frame Debugger is 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:
- The Frame Debugger button in the Game View toolbar has a tooltip "Opens the Frame Debugger", but it also toggles between Enabling/Disabling the Frame Debugger when pressed
- Does not reproduce if using the (Window > Analysis > Frame Debugger) toolbar instead of the Game View Frame Debugger button
- If this is intended, the tooltip on the Game View button should be updated
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
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.