Search Issue Tracker
Fixed
Fixed in 6000.0.2f1
Votes
3
Found in
6000.0.0b12
Issue ID
UUM-66760
Regression
Yes
[URP][RG][NRP]"Attempting to render to a depth only surface with no dummy color attachment" warnings are continuously thrown when Game View is visible and Gizmo is activated
Reproduction steps:
1. Open the attached "Bug" project
2. Open the Game View and turn on Gizmo
3. Enable Render Graph by going to "Project Settings" -> "Graphics" -> "URP" -> "Render Graph"
4. Move the mouse over the Game View and the Inspector Window
5. Observe the Console logs
Expected results: No "Attempting to render to a depth only surface with no dummy color attachment" warnings appear in the Console
Actual results: "Attempting to render to a depth only surface with no dummy color attachment" warnings are continuously thrown
Reproducible with: 2023.3.0a13, 6000.0.0b12
Not reproducible with 2021.3.36f1, 2022.3.21f1, 2023.2.14f1, 2023.3.0a12
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Notes:
- When Render Graph is disabled, no warnings are thrown
- The errors thrown in 2023.3.0a12 and 2023.3.0a13 seem to be unrelated as they disappear in later versions
- Could not reproduce with HDRP
Comments (1)
-
sklimenko
Apr 11, 2024 07:47
Same on 6000.0.0b15
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Resolution Note (fix version 6000.0.2f1):
Thanks for catching this one, it has been fixed. No more annoying warning message.