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
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
Add comment