Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.1.0f3
Issue ID
964482
Regression
No
When using CommandBuffer.DrawRenderer() the shader stencil state leaks and affects subsequently rendered objects
Steps to reproduce:
1. Download and open the attached project
2. Observe the scene's gameobjects in the Game view
Expected result: objects in front rendered normally
Actual result: object behind's stencil state leaks
Reproduced on 5.6.4p1, 2017.1.2p1, 2017.2.0p1, 2017.3.0b8, 2018.1.0a3
Notes:
- Workaround provided: checking the "Do stencil workaround" on the camera's attached script solves the issue by forcing an additional object to be rendered in the command buffer using a shader that sets stencil back to a default state.
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
Add comment