What causes soft particles showing hard edges at geometry intersections?

The particle shader is not fading by scene depth, either because Soft Particles is off or the camera depth texture it needs is not being generated, so quads clip abruptly against solid surfaces.

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 Soft Particles Showing Hard Edges Where They Intersect Geometry in Unity

Quick answer: Enable the depth texture and use a soft-particle fade that compares the particle's fragment depth to the sampled scene depth, fading alpha as the two converge.

Camera-facing particle quads intersect world geometry along a hard line unless the shader softens the edge by comparing its depth to the scene depth behind it. That fade needs the camera depth texture. Here is how to fix it.

How to fix it

1. Enable the depth texture

Soft fading reads the scene depth, so enable Depth Texture in the URP asset (or ensure the camera renders depth in Built-in) so _CameraDepthTexture exists.

2. Fade alpha by depth difference

Compute fade = saturate((sceneDepth - particleDepth) / fadeDistance) in linear eye depth and multiply it into the output alpha so the quad softens as it nears a surface.

3. Tune the fade distance

Adjust the fade distance so the softening covers a believable band; too small reintroduces the hard edge, too large makes particles wash out before they touch anything.

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