Fix: Unity Particle System Trail Rendering Through Walls

Here is how to fix Unity particle trails that visibly draw through walls and other opaque objects. Your projectile flies behind a column and the head particle is correctly occluded, but the trail tail snakes across the screen as if the column was not there. The trail uses a different material than the head, and that material’s depth-test settings are almost always the problem.

The Symptom

A Particle System with the Trails module enabled emits trails that pass through walls, terrain, or any other opaque geometry. The head particle disappears correctly when occluded; only the trail ribbon ignores depth. The effect breaks readability for projectiles, magic effects, or movement trails.

What Causes This

Trails module uses its own material. The Particle System Renderer has two material slots: Material (for particles) and Trail Material (for trails). Setting the first does not affect the second.

The trail material has ZTest Always. Many premade trail shaders disable depth testing so they can be used as UI overlays. When applied to a world-space trail, this means walls do not occlude them.

Wrong render queue. Materials in queue 4000 (Overlay) draw after everything else and ignore depth. Trails meant for in-world use should be in queue 3000 (Transparent).

Soft Particles disabled with thin geometry. If trails should fade against geometry, soft particles need depth texture access. Without it, the trail clips harshly through anything close.

The Fix

Step 1: Assign a proper trail material. On the Particle System Renderer, drag a new material into the Trail Material slot. Use a duplicate of Particles/Standard Unlit or your URP equivalent.

Step 2: Set ZTest to LessEqual. In the trail material’s shader properties, set ZTest to LessEqual. If using Shader Graph, expose ZTest in the URP Lit/Unlit master node.

// In a custom shader, inside SubShader/Pass:
ZWrite Off
ZTest LessEqual
Blend SrcAlpha OneMinusSrcAlpha
Tags { "Queue"="Transparent" "RenderType"="Transparent" }

Step 3: Adjust the render queue. In the Material Inspector, click the gear icon to switch to Debug mode if needed and set Render Queue to 3000 (Transparent). Avoid 4000 (Overlay) unless you want the trail on top of UI as well.

Step 4: Enable soft particles for fade against walls. In the trail shader, enable Soft Particles and set Near and Far Fade values. The trail then fades smoothly into geometry rather than clipping abruptly. URP requires Depth Texture enabled in the URP Asset.

// Verify URP depth texture for soft particles
// Edit -> Project Settings -> Graphics -> URP Asset -> General
Depth Texture     = true
Opaque Texture    = true  // only if shader needs it

Step 5: Confirm at runtime via the Frame Debugger. Window → Analysis → Frame Debugger. Step until you see the particle trail draw call. The shader name should match your assigned trail material, and the ZTest column should be LEqual.

Common Mistakes to Avoid

Do not use UI/Default as a trail material. It has ZTest Always built in. Do not set the trail material’s queue to Overlay just because that is what the head particle uses; the head and trail should both be in Transparent queue 3000 unless you have a specific reason to differ.

Watch out for material instances. If you assign a material at runtime via renderer.trailMaterial on a copy you forgot to apply changes to, the trail uses the asset version. Always verify with the Inspector or Frame Debugger.

Understanding the issue

Particle systems are stateful machines. Each particle has its own lifetime, and the system has its own configuration. Bugs that involve the lifecycle (creation, death, pool reuse) tend to be timing-sensitive and hardest to reproduce.

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

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

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

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

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

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.

“Two materials, two depth modes. The Trails slot needs the same depth respect as the head particle, or it draws through walls.”

Related Issues

For trails that disappear entirely, see Particle System Not Playing. For trail color glitches, see VFX Graph Particles Not Spawning.

Trail Material slot. ZTest LessEqual. Queue 3000. Walls block the trail again.