Why doesn't my Shader Graph stencil work in URP?

Shader Graph doesn't expose stencil writes directly. URP draws Opaque + Transparent in batched passes; you can override stencil via a Render Objects feature with Stencil State configured.

How do I add a Render Objects feature?

URP Renderer Asset → Add Renderer Feature → Render Objects. Filter by LayerMask. Configure Stencil State (Reference, Compare, Pass operation). Now objects on that layer write the stencil with your settings.

What about reading stencil in a Shader Graph?

Use a Custom Function node + HLSL to sample the stencil texture (URP exposes _CameraStencilTexture in some setups). For complex stencil logic, fall back to a hand-written HLSL shader.

Fix: Unity Shader Graph Stencil Not Writing in URP

Quick answer: Add a Render Objects renderer feature to your URP Renderer. Filter by LayerMask. Configure Stencil State (Reference, Pass = Replace, etc.). Shader Graph itself can’t write stencil; the feature does.

Stencil shader trick (mask out a region, render inside-only) requires writing the stencil. Shader Graph doesn’t expose those toggles. Render Objects feature fills the gap.

The Symptom

Stencil-based effect (portal, mirror, mask) doesn’t mask anything. Either the writer doesn’t set the stencil, or the reader doesn’t respect it.

The Fix

Render Objects feature for stencil writes.

URP Renderer Asset:
  + Render Objects (Mask Writer):
    Render Pass Event: Before Rendering Opaques
    Filter:
      Queue: Opaque
      Layer Mask: MaskGeometry
    Overrides:
      Stencil:
        Override Stencil:    true
        Reference Value:     1
        Compare Function:    Always
        Pass Operation:      Replace
        Fail Operation:      Keep

Objects on the MaskGeometry layer now write 1 to the stencil where they render.

Read the stencil in another feature for the masked rendering.

+ Render Objects (Inside Mask Renderer):
    Filter: Layer Mask: InsideMaskOnly
    Overrides:
      Stencil:
        Override Stencil: true
        Reference Value:  1
        Compare Function: Equal
        Pass Operation:   Keep

Objects render only where stencil = 1.

Verifying

Frame Debugger → Render Objects passes appear in order. Stencil state in the RenderState panel shows your overrides. Final composite shows masked region.

Understanding the issue

Shader bugs manifest visually but trace to invisible state. Triage requires understanding the runtime context as much as the source.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Render Objects feature owns the stencil. Shader Graph just renders.”

Related Issues

For Renderer Feature blit, see blit pass event. For Render Graph URP 17, see Render Graph URP 17.

Feature writes. Feature reads. Mask works.