Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b10
6000.3.0a2
6000.4.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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment