Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.3.11f1
6000.4.1f1
6000.5.0b1
6000.6.0a1
Issue ID
UUM-138303
Regression
Yes
Game View and Frame Debugger output flicker when Frame Debugging is enabled and the image is converging
Steps to reproduce:
- Open the attached project
- Open the OutdoorsScene
- In the Frame Debugger window, enabled Frame Debugging
- Move the cube in the Scene, to start rendering a new image in the Game view
- While the image is converging, move the mouse cursor between the Game view and the Frame Debugger windows
Actual results: Game view and Frame Debugger windows flicker if Frame Debugging is enabled while the image is converging
Expected results: Game view and Frame Debugger windows don't flicker
Reproducible with versions: 6000.3.0a1, 6000.3.11f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Not reproducible with versions: 6000.0.71f1, 6000.2.15f1
Tested on (OS): Windows 11
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
Add comment