Search Issue Tracker
Fixed
Fixed in 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a5
Votes
1
Found in
6000.0.47f1
6000.1.0f1
6000.2.0a9
6000.3.0a1
Issue ID
UUM-103401
Regression
Yes
Rendering Debugger throws a warning and renders the Scene view in solid black when material debug tools and Path Tracing are used
Steps to reproduce:
- Open the attached project
- Open the OutdoorsScene
- Open Rendering Debugger window
- In the Material section set the 'Common Material Properties' option to Albedo
Actual results: 'Attempting to draw with missing bindings' warning is thrown and the Scene Window is rendered in solid black
Expected results: No Warning or Error is thrown and the Scene view correctly displays objects based on the Debugger mode used
Reproducible with versions: 6000.0.20f1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a9
Not reproducible with versions: 2022.3.61f1, 6000.0.19f1
Tested on (OS): Windows11
Notes:
- The bug does not reproduce when other Rendering Debugger tools are used (Tested with options from Lighting and Rendering tabs)
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 (fix version 6000.2.0b11):
There was a missing buffer when rendering debug views with the path tracing enabled. This is fixed now.
Resolution Note (fix version 6000.1.13f1):
There was a missing buffer when rendering debug views with the path tracing enabled. This is fixed now.