Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b10
6000.3.0a2
6000.4.0a1
6000.5.0a1
Issue ID
UUM-111656
Regression
No
HD Sample Buffer returns black for Rendering Layer Mask when Custom Pass Volume is not active
Reproduction steps:
1. Open the attached “IN-107319.zip” project
2. Open the “OutdoorsScene”
3. From the Hierarchy, select the “Main Camera” GameObject
4. Disable the “Custom Pass Volume” Component
5. Enter Play mode
6. Observe the Game view
Expected result: The Rendering Layer Mask remains on the GameObjects as before
Actual result: The Rendering Layer Mask disappears from GameObjects and no longer shows different brightness levels for different rendering layers
Reproducible with: 2023.3.0a1, 6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: no other environment tested
Notes:
- After 4th step, if observed in the Frame Debugger in ExecuteRenderGraph > ForwardTransparent > RenderLoop.DrawSRPBatcher the “_RenderingLayerMaskTexture” has the size of 1x1x1.
- Also reported on Discussions: https://discussions.unity.com/t/how-to-use-rendering-layer-mask-buffer-in-shader-graph/1663028
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.