Search Issue Tracker
By Design
Votes
0
Found in
6000.2.4f1
6000.3.0b1
Issue ID
UUM-116968
Regression
Yes
GBuffer5 appears empty/black when blit to screen in Deferred Rendering Path
Reproduction steps:
1. Open the attached “IN-114624.zip” project
2. Open the “RenderingLayerMaskBug” scene
3. From the Project window, select “PC_Renderer” asset
4. In the Inspector, enable the “G Buffer Overlay” Renderer Feature
5. In the “G Buffer” property slider, change the value to “5”
6. Observe the Game view
Expected result: The Cubes and Sphere appear as red silhouettes
Actual result: The Game view is completely black
Reproducible with: 6000.2.0b1, 6000.2.4f1, 6000.3.0b1
Not reproducible with: 6000.0.57f1, 6000.2.0a10
Reproducible on: Windows 11
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:
Hello.
Rendering layers are no longer encoded as floating point values. If you want to debug display them on screen, you must normalize the value in shader manually. The Frame Debugger also cannot display this format, but that is a separate issue which we are aware of.
Rest assured that the Rendering Layers texture is there and functions properly.