Quick answer: Compute an edge band between the dissolve threshold and threshold plus a width, then tint that band with an HDR emissive color so it glows as the surface dissolves.

A clean clip dissolve has no burn ring because nothing highlights the boundary. Adding an edge band driven by the same noise and emitting on it produces the glowing burn. Here is how.

How to fix it

1. Clip by noise threshold

Sample a noise texture and clip(noise - threshold) to carve away the surface as the threshold rises from 0 to 1, which gives the basic dissolve.

2. Build an edge band

Compute edge = smoothstep(threshold, threshold + edgeWidth, noise) so a thin band near the cut is isolated; pixels in this band are about to be clipped.

3. Emit on the edge

Multiply the edge band by an HDR emissive color and add it to the output so the boundary glows. With bloom enabled this reads as a burning rim that follows the dissolve front.

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.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.