Search Issue Tracker
By Design
Votes
0
Found in
6000.0.57f1
6000.2.4f1
6000.3.0b1
Issue ID
UUM-116964
Regression
No
Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window and Frame Debugger is Enabled
Steps to reproduce:
1. Open the attached "TestingProject.zip" from provided Google Drive link
2. Make sure that Frame Debugger is enabled
3. Minimize/Maximize Inspector window
4. Observe the Game view window
\\
Actual results: Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window when Frame Debugger is Enabled
Expected results: No rendering artifacts should be visible in the Game view window when maximizing/minimizing Inspector window when Frame Debugger is Enabled
\\
Reproducible with versions: 6000.0.57f1, 6000.2.4f1, 6000.3.0b1
\\
Tested on (OS): Windows 11
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This is an artifact of how the frame debugger works. Resizing the window changes the number of rendering events, moving to a different part of the frame. Manually picking a rendering event from the list in the frame debugger window after resizing should allow to go back to the intended event