Search Issue Tracker
Fixed in 2022.2.17f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a4
Votes
1
Found in
2022.2.0b12
2023.1.0a15
2023.2.0a1
Issue ID
UUM-17193
Regression
No
[Frame Debugger] Frame Debugger window doesn’t open and throws errors when docked with game window
How to reproduce:
- Open any project
- Open and enable Frame Debugger
- Dock Frame Debugger window near the Game Window
- Try to focus the Frame Debugger tab
Expected result: Frame Debugger tab is opened
Actual result: Frame debugger is not opened, throws error
Error:
ArgumentException: Getting control 5's position in a group with only 5 controls when doing repaint
Reproducible with: 2022.2.0b12, 2023.1.0a15
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
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Resolution Note (fix version 2023.2):
Added a clearer error in the Frame Debugger window.
Frame Debugger is constantly getting data from the source it's trying to debug. When Frame Debugger is on the same tab as the Game Window nothing is being rendered to the Game Window, then the Frame Debugger can't capture anything.