Search Issue Tracker
By Design
Votes
0
Found in
2017.4.20f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1126855
Regression
No
Frame Debugger is flickering when changing Game View Scale or moving Game View
How to reproduce:
1. Open attached project "case_1126668-LSRD2"
2. Open Frame Debugger and place it near Game View
3. Change Game View Scale -OR- drag line separating two windows
Expected result: Frame Debugger is not flickering and not showing random draw calls
Actual result: Frame Debugger is flickering and randomly showing draw calls
Reproduced with: 2017.4.20f1, 2018.3.6f1, 2019.1.0b3, 2019.2.0a5
Note: the flickering is mostly visible with version 2017.4.
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 expected as the view is re-rendered when interaction is had with the view, this forces a redraw, and the flickering is just seeing the final framebuffer briefly before the frame debugger returns to its prior position.