Search Issue Tracker
Fixed in 2022.3.11f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X
Votes
1
Found in
2022.2.5f1
2023.1.0b2
2023.2.0a1
Issue ID
UUM-26399
Regression
No
Full screen renderer feature does not work with stencil
The Full screen shader graph target that is designed to be used with the full screen renderer feature has properties for setting stencil behaviour. These settings do not seem to have an influence when the shader is drawn using the Full screen renderer feature.
Steps to repro:
- open attached project
- Observe that the renderer is set up to draw the red sphere with stencil value 1 with render objects
- Observe that the "StencilPost" shader graph is set up with "Equal 1"
- Observe that the full screen renderer feature (added to the renderer) renders with the stencil post shader.
- Observe which part of the screen is getting the pattern
Expected: Only the red sphere gets the pattern
Actual: The entire screen is covered
As a sanity check I added a quad in front of the camera with the same material as the full screen renderer feature. This quad will render if "Quad Post" is enabled. The quad behaves as expected (remember to turn off the Draw Stencil Post).
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 2022.3):
Fixed