Fix: Unreal DecalComponent Not Rendering on Translucent Surface

Here is how to fix Unreal DecalComponents that show up on every solid surface but go missing the moment you try to project them onto glass, water, or any other translucent material. The decal is correctly placed, the bounding box overlaps the surface, but the surface renders unaffected. The deferred renderer’s decal pass simply does not see translucent geometry.

The Symptom

A DecalComponent works on walls, floors, and characters. Aim it at a window, an aquarium, or a puddle — nothing. The decal projects past the translucent surface onto whatever opaque geometry is behind it (the wall behind the window, the pool floor under the water).

What Causes This

Translucent rendering happens after decals. The deferred decal pass runs against GBuffer data, which contains only opaque geometry. Translucent materials are forward-rendered later and decals never reach them.

Surface material domain wrong. If the surface material’s Blend Mode is Translucent or Additive, it cannot participate in the deferred decal pass.

Decal Blend Mode incompatible. Some decal blend modes only target specific GBuffer channels. A Stain decal on a non-base-color surface contributes nothing visible.

Receives Decals flag off. Each Primitive Component has a Receives Decals checkbox. If unchecked, no decals project on it regardless of material.

The Fix

Step 1: Confirm Receives Decals is on. Select the surface mesh in the level. In Details, under Rendering, ensure Receives Decals is checked.

Step 2: For glass-like surfaces, use Opaque + refraction. Open the surface material. Set Blend Mode to Opaque. In the shader graph, multiply BaseColor by 0.05 (mostly invisible) and add Refraction via the Refraction input on the master node. The result looks like glass but participates in the GBuffer.

// Glass-like material wired up:
BaseColor    = small dark tint
Metallic     = 0
Roughness    = 0.1
Specular     = 1
Refraction   = IoR-based refraction node
Blend Mode   = Opaque  (allows decals)

Step 3: For water, place a receiver plane. Below your water surface, place an invisible plane with an opaque material that captures decals. Set its visibility for shadows and decals only:

StaticMeshComponent (DecalReceiver):
    bRenderInMainPass = false
    bReceivesDecals = true
    bAffectIndirectLightingWhileHidden = false
    bRenderInDepthPass = false

This object exists just to catch decals. Players cannot see it directly, but the decals it receives become visible through the translucent water on top.

Step 4: Pick the right Decal Blend Mode. For full-color projections (blood, paint), use Translucent. For only normals (raised emboss), use Normal. For only darkening (dirt, scorch), use Stain. The blend mode determines which GBuffer channels the decal writes to.

Step 5: For surfaces that must be true translucent, use a forward decal mesh. Skip DecalComponent entirely; use a flat StaticMeshActor with a translucent material that resembles the decal art. It renders at the same depth as the translucent surface and looks like a decal. Less efficient but works on water/glass.

Sort Order For Overlapping Decals

If multiple decals overlap, set Sort Order on the DecalComponent. Higher values render last (on top). Useful when blood splatter and footstep decals stack at the same spot — usually footsteps below blood.

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 Unreal. 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

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

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

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 Unreal-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 Unreal, 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.

“Decals are a deferred opaque feature. Translucent surfaces ignore them. Make the surface opaque or fake the decal with a flat mesh.”

Related Issues

For URP decal issues, see URP Decal On Skinned Mesh. For other Unreal rendering issues, see Niagara Not Rendering in PIE.

Opaque + refraction for glass. Hidden receiver plane for water. Sort Order for stacks.