Search Issue Tracker
Feature Request
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.10f1
2023.3.0b8
6000.0.0b11
Issue ID
UUM-64493
Regression
No
Overdraw Mode falsely shows high overdraw areas when there are TMP Text and some sprites in the Scene
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene“ Scene
3. In the Rendering Debugger window’s (Window > Analysis > Rendering Debugger) Rendering tab, set Overdraw mode to All
4. Observe the Scene view
Expected result: There are no high overdraw areas
Actual result: Multiple GameObjects are painted white, meaning high overdraw areas
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.10f1, 2023.3.0b8
Reproducible on: Windows 11, macOS 14.2.1 (M1 Max) (by user)
Not reproducible on: No other environments 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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Right now, the overdraw function can only debug URP-internal shaders. Others, like in this case TMP are not supported. For future versions of the rendering debugger, we consider adding support for external shaders.
To use the debug view, disable all objects that use external shaders, or replace the shaders with URP-internal ones