Quick answer: Render Graph culls any pass whose outputs nothing else reads. If your pass writes to a private texture but no later pass samples it, the compiler removes it. Either write to the active camera color (so the final blit picks it up) or call builder.SetGlobalTextureAfterPass so other shaders can sample it.

Here is how to fix Unity URP 17+ Render Graph passes that compile clean, register fine, but never execute on screen. You migrated your custom ScriptableRenderPass from Execute to RecordRenderGraph, your code runs through AddRasterRenderPass, but the SetRenderFunc lambda never fires. Render Graph culls passes whose outputs are never consumed, and many migrations accidentally produce orphan passes.

The Symptom

Your custom Render Feature is in the URP Renderer Data list. RecordRenderGraph is being called (you can verify with a Debug.Log in the override). Inside, AddRasterRenderPass returns a builder, you wire it up — but the SetRenderFunc never fires at runtime. The Render Graph Viewer shows your pass in red, marked “Culled”.

What Causes This

No output is read downstream. Render Graph performs aggressive dead-pass elimination. If you write to a TextureHandle that no later pass declares via UseTexture(handle, AccessFlags.Read) or that does not feed the final present, your pass is removed.

Writing to active color but not declaring it. The active camera color must be declared with UseTextureFragment at AccessFlags.Write or AccessFlags.ReadWrite. Without that declaration, the graph thinks you wrote nothing.

Empty SetRenderFunc. If you allocate the pass but never call builder.SetRenderFunc, the compiler treats the pass as a no-op and culls it.

Conditional injection. If SetupRenderPasses only enqueues the pass under specific conditions (camera tag, debug flag), you may be looking at a frame where the condition was false.

The Fix

Step 1: Make the pass write to the camera color and declare it.

using UnityEngine;
using UnityEngine.Rendering;
using UnityEngine.Rendering.RenderGraphModule;
using UnityEngine.Rendering.Universal;

public class TintPass : ScriptableRenderPass
{
    private class PassData
    {
        public Material material;
        public TextureHandle source;
    }

    public Material tintMaterial;

    public override void RecordRenderGraph(RenderGraph rg, ContextContainer frameData)
    {
        var resources = frameData.Get<UniversalResourceData>();
        TextureHandle camColor = resources.activeColorTexture;

        using (var builder = rg.AddRasterRenderPass<PassData>("Tint", out var data))
        {
            data.material = tintMaterial;
            data.source = camColor;

            builder.UseTexture(camColor, AccessFlags.Read);
            builder.SetRenderAttachment(camColor, 0, AccessFlags.Write);
            builder.AllowPassCulling(false);

            builder.SetRenderFunc((PassData d, RasterGraphContext ctx) =>
            {
                Blitter.BlitTexture(ctx.cmd, d.source, new Vector4(1,1,0,0), d.material, 0);
            });
        }
    }
}

Step 2: Disable culling for debug. builder.AllowPassCulling(false) forces the pass to run regardless of output reads. Useful while diagnosing whether culling is the problem. Remove it after you have the right reads/writes declared.

Step 3: Inspect Render Graph Viewer. Open Window → Analysis → Render Graph Viewer. Pick a frame from the active camera. Find your pass — it should be green (executed). Red means culled. Hovering over a red pass shows the cull reason.

Step 4: Confirm the Render Feature enqueues the pass.

public class TintFeature : ScriptableRendererFeature
{
    [SerializeField] private Material material;
    private TintPass pass;

    public override void Create()
    {
        pass = new TintPass { tintMaterial = material, renderPassEvent = RenderPassEvent.AfterRenderingPostProcessing };
    }

    public override void AddRenderPasses(ScriptableRenderer renderer, ref RenderingData data)
    {
        if (material == null) return;
        renderer.EnqueuePass(pass);
    }
}

If EnqueuePass is gated on conditions, log when those conditions are not met. Common gotcha: only enqueue for game cameras and skip the editor preview camera, which makes testing painful.

Step 5: For samplers in later passes, expose via SetGlobalTextureAfterPass.

builder.SetGlobalTextureAfterPass(myTexture, Shader.PropertyToID("_MyEffectTex"));

This makes the texture available to global shader sampling for the rest of the frame, which counts as a downstream read and prevents culling.

Migration Checklist

Understanding the issue

Render pipelines have ordering: which pass runs when, what state is bound, which targets are written. Bugs at this layer are often invisible in code review and only manifest at runtime.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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 Graph runs only what is reachable. Declare your reads, declare your writes, set the render func, or get culled.”

Related Issues

For URP render features in general, see URP Render Feature Not Executing. For shader-time issues, see Shader Graph Time Node Build Issues.

UseTexture for inputs. SetRenderAttachment for outputs. SetRenderFunc to do work. Disable culling while debugging.