Search Issue Tracker
Not Reproducible
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b10
6000.3.0a2
6000.4.0a1
6000.5.0a1
Issue ID
UUM-111918
Regression
No
Frame Debugger flickers when a Shader Graph Window is open
Reproduction steps:
1. Open the attached “IN-108543_FrameDebuggerFlicker.zip“ project
2. Create and open a blank shader graph from the Project View (Create > Shader Graph > Blank Shader Graph)
3. Dock the Shader Graph Window next to the Game View
4. Open the Frame Debugger (Window > Analysis > Frame Debugger)
5. Enable the Frame Debugger and observe
Expected result: Frame Debugger functions as expected, no abnormal glitches
Actual result: The Frame Debugger is flickering, glitching
Reproducible with: 6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Reproducible on: M1 Max MacOS 15.5, Windows 11 (Tested by CQA)
Not reproducible on: No other environment tested
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:
Shader Graph renders images as part of its previews, so it is likely that certain configurations of a project may produce the described effect. We struggled to reproduce the issue in a base case environment, so the root cause isn't entirely clear.
We do intend on revisiting Shader Graph's preview rendering solution in the near future and will take this issue into consideration for that.