Search Issue Tracker
Fixed
Fixed in 6000.0.57f1, 6000.2.3f1, 6000.3.0a6
Votes
1
Found in
6000.0.55f1
6000.2.0f1
6000.3.0a4
Issue ID
UUM-113762
Regression
Yes
SpriteShapeRenderer overrides stencil settings when a custom shader is used to set stencil values
How to reproduce:
1. Open the “IN-109833_SpriteShapeRenderer“ project
2. Open the “SampleScene”
3. Go to Window > Analysis > Frame Debugger
4. In the Frame Debugger window click “Enable”
5. Expand the “Renderer2D Pass/RenderLoop.Draw”
6. Click on “Draw Dynamic” and observe the Stencil values
7. Click on “Draw Mesh” and observe the Stencil values
Expected result: Stencil values are preserved for the "Closed Sprite Shape" GameObject
Actual result: Stencil values are overwritten for the "Closed Sprite Shape" GameObject
Reproducible with: 6000.0.2f1, 6000.0.55f1, 6000.1.16f1, 6000.2.0f1, 6000.3.0a4
Not reproducible with: 6000.0.1f1
Reproducible on: macOS 15.5 (M1 Max), Windows 11 (by user)
Not reproducible on: no other environments tested
Note: In 6000.0.1f1 the Draw call is named “SRP Batch” and draws both Sprites with Stencil values preserved
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
Add comment