Search Issue Tracker
By Design
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X
Votes
0
Found in
2022.3.51f1
6000.0.25f1
6000.1.0a2
6000.2.0a1
Issue ID
UUM-85646
Regression
No
"Rendering Debugger" displays incorrect overdraw count when using "Unlit/Texture" shader
Reproduction steps:
1. Open the attached “repro_IN-87031“ project
2. Open the “Assets/Test.unity“ Scene
3. Open the “Rendering Debugger“ (“Window → Analysis → Rendering Debugger“)
4. In the “Rendering“ section, under “Rendering Debug“, find the “Overdraw Mode“ parameter
5. Change the “Overdraw Mode“ parameter to “Opaque“ or “Transparent“
6. Observe the Scene/Game view
Expected result: There’s very little overdraw as there is only a single cube in the Scene
Actual result: There’s a lot of overdraw while there is only a single cube in the Scene
Reproducible with: 2022.3.51f1, 6000.0.25f1, 6000.1.0a2
Couldn’t test with: 2021.3.45f1 - No “Overdraw Mode“ parameter in the “Rendering Debugger”
Reproducible on: Windows 10 (22H2)
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
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
Resolution Note:
Hello.
You are not using the URP Unlit shader in this example, but the old Built-In Unlit shader which does not support SRP debug view. If you switch to 'Universal Render Pipeline/Unlit' things will work as expected.