Fix: Unity Decal Projector Not Rendering on Skinned Mesh

A blood splat decal looks great on the floor. Move it onto an enemy and nothing renders. Decals on skinned meshes need explicit opt-in across the URP pipeline, the projector, and the renderer.

The Symptom

DecalProjector renders fine on static geometry. Skinned mesh receivers (characters, enemies) show no decal where the projector overlaps them.

The Required Configuration

1. Decal Renderer Feature on the URP renderer. ProjectSettings → Graphics → URP Asset → Renderer → Add Renderer Feature → Decal. Without this, decals do not render at all in URP.

2. Technique = Screen Space. The Decal Renderer Feature has a Technique dropdown. DBuffer works only with the Deferred path (URP 2022+). Screen Space works with both Forward and Deferred and is the default for skinned mesh support.

3. Decal Layers enabled. URP Asset → Lighting → Decal Layers checkbox. This adds a 32-bit decal layer mask to every renderer. Without it, projector layer settings are ignored and you might still hit silent skips.

4. Receive Decals on the SkinnedMeshRenderer. The SkinnedMeshRenderer Inspector has a Receive Decals checkbox under Additional Settings. Tick it on every character that should accept decals.

Layer Masks

DecalProjector → Decal Layer Mask: a 32-bit dropdown of named layers (Default, plus user-named ones). The receiver’s Rendering Layer Mask must share at least one bit. Both default to “Everything” on creation, so the most common bug is naming layers and forgetting to update one of the two ends.

DecalProjector:
  Decal Layer Mask:        EnemyBlood
  Material:                M_BloodSplatter
  Size:                    (2, 2, 2)

SkinnedMeshRenderer (Enemy):
  Receive Decals:          true
  Rendering Layer Mask:    EnemyBlood, Default

Spawning Bullet Hole Decals on Hit

public class DecalSpawner : MonoBehaviour
{
    public GameObject decalPrefab;

    public void SpawnAt(RaycastHit hit)
    {
        var proj = Instantiate(decalPrefab, hit.point, Quaternion.LookRotation(-hit.normal));

        if (hit.transform.GetComponentInParent<Animator>())
            proj.transform.SetParent(hit.collider.transform, true);
    }
}

Parenting under the hit collider keeps the decal moving with the bone, so it tracks animations without needing the screen-space projection to recompute every frame.

HDRP Differences

HDRP has its own Decal Projector with its own Material requirements. The same checks apply: Receive Decals on the renderer, layer mask matched, Decal Projector volume set up. HDRP also has Surface Type and Affect BaseColor / Normal / Mask toggles per material.

Verifying

Frame Debugger (Window → Analysis → Frame Debugger). Step into the rendering of the character. There should be a Draw Decals pass that includes your projector. If absent, the renderer feature is missing or the layer mask excludes you.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

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

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

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

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.

“Renderer feature. Screen Space technique. Decal layers on. Receive Decals on the renderer. Layer masks aligned.”

Related Issues

For decals invisible at distance, see decal distance fade. For Volume effects ignored, see Volume not applying.

Renderer feature. Screen Space. Receive Decals. Decals land.