Search Issue Tracker
Fixed in 2017.1.X
Votes
2
Found in
2017.1.0b7
Issue ID
917247
Regression
Yes
Stencil 'Comp' operation is ignored when shader is used with SpriteRenderer
Repro steps:
1. Open "SpriteStencilBug" projects "Main" scene
2. Look at "UnlitStencilSprite" and "UnlitStencilMesh" in the Hierarchy window (One has a Mesh renderer and the other has a Sprite renderer)
3. Open the "UnlitStencil" Shader file
4. Change code at line 18 from "Comp Always" to "Comp Never"
5. Go back to the Editor
Expected result: Both of the cubes disappear
Actual result: One of the cubes disappear (The one with the Mesh renderer)
Reproduced with: 2017.1.0a6, 2017.1.0b8, 2017.2.0a1
Regression introduced in: 2017.1.0a6 (00315a6f23c0)
Did not reproduce on: 5.6.1p2, 2017.1.0a2, 2017.1.0a4, 2017.1.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Add comment