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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment