Fix: Unity URP Decal Projector Not Projecting on Skinned Mesh

Here is how to fix Unity URP Decal Projectors that show up on terrain and static meshes but completely skip your skinned-mesh characters. Blood splatter on the ground? Yes. Blood on the player? Nothing. The cause is the Decal Renderer Feature’s Technique setting — Screen Space mode, the default, only writes to opaque static geometry.

The Symptom

A DecalProjector looking down at a character renders the decal on the floor below them but not on their body. The same projector works on every static mesh nearby. SkinnedMeshRenderer is unaffected.

What Causes This

Screen Space technique skips skinned meshes. Screen Space decals are accumulated post-opaque, and the URP implementation chose to skip skinned meshes for performance reasons in older versions.

DBuffer technique not enabled. The DBuffer (Decal Buffer) technique writes decal data into intermediate buffers during the GBuffer pass, which all opaque renderers (including skinned) consume. It must be selected explicitly.

Depth texture missing. DBuffer requires the camera depth texture. Without it enabled in the URP Asset, DBuffer cannot reconstruct surface positions to project onto.

Decal Layer mask wrong. The DecalProjector has a Decal Layer mask. The renderer it should affect must include the same layer in its Decal Layer Mask. A bit-mask mismatch silently filters the decal.

The Fix

Step 1: Add the Decal Renderer Feature. Find your URP Renderer Data asset. In the inspector, click Add Renderer Feature and pick Decal.

Step 2: Set Technique to DBuffer. On the Decal feature, set Technique to DBuffer. Set Surface Data to Albedo Normal MAOS for the most flexible projection.

Step 3: Enable Depth Texture. Open the URP Asset. Under General, enable Depth Texture. DBuffer reads it.

Step 4: Match decal layers. On the DecalProjector, set its Decal Layer to (for example) Decal Layer 1. On the SkinnedMeshRenderer’s Renderer component, set Rendering Layer Mask to include Decal Layer 1. Both must overlap.

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

public class DecalSetup : MonoBehaviour
{
    [SerializeField] private SkinnedMeshRenderer body;

    void Awake()
    {
        // Decal Layer 1 (bit 1)
        body.renderingLayerMask |= (uint)(1 << 1);
    }
}

Step 5: For decals attached to moving characters, parent to bones. A world-space DecalProjector projects from a static world location. As the character animates, the decal “slides” across the deforming mesh. To stick a wound to a specific body part, parent the projector to the relevant bone:

var chest = body.GetBone(HumanBodyBones.Chest);
decalProjector.transform.SetParent(chest, false);
decalProjector.transform.localPosition = Vector3.zero;

Performance Note

DBuffer is more expensive than Screen Space — it adds an extra GBuffer-time pass. For mobile, you may need to limit DBuffer to certain cameras (cinematic only) and use Screen Space for ambient world decals on static geometry. Configure two URP Renderer Data assets and switch via camera Renderer index.

Verifying The Setup

Frame Debugger after the change should show a Render DBuffer pass before the opaque pass and DBuffer Sample calls during opaque rendering. The decal’s color and normal should appear in the buffer overlay. If you see no DBuffer pass, the feature is not enabled or Depth Texture is off.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

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

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

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

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

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.

“Screen Space decals are fast and skinned-mesh-blind. DBuffer is slower and universal. Pick the technique that matches the surface you target.”

Related Issues

For URP feature execution issues, see URP Render Graph Pass. For URP decal projector visibility, see URP Decal Projector Not Showing.

DBuffer technique. Depth Texture on. Layer masks match. Skinned meshes accept the decal.