What causes a Godot Decal3D not appearing on a moving surface?

The Decal3D only affects meshes within its box whose layers match its cull mask, and Distance Fade or a too-small box can hide it entirely.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Godot Decal Not Appearing on a Moving Surface

Quick answer: Size the Decal box to enclose the target surface, set the Cull Mask to include the target's render layer, and disable or extend Distance Fade.

Decal3D projects only inside its bounding box onto matching layers, so a target that moves out of the box or off the cull mask shows no decal. Adjusting box, mask, and fade fixes it. Here is how.

How to fix it

1. Enclose the surface in the box

The decal projects only within its extents. Grow the Decal's box so it fully contains the surface you want marked; geometry outside the box receives nothing.

2. Match the cull mask

Set the Decal's Cull Mask to include the visual layer of the target mesh. A mismatch means the surface is excluded from projection even when it is inside the box.

3. Check Distance Fade and Albedo

Disable or extend Distance Fade so the decal does not fade out before the camera reaches it, and ensure an Albedo texture with alpha is assigned, or there is nothing to draw.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.