What causes LOD popping with no cross-fade transition?

Without a transition mode, an LOD group swaps meshes instantly at the screen-size threshold, so the silhouette change pops in a single frame instead of fading.

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 LOD Popping With No Cross-Fade Transition

Quick answer: Enable LOD cross-fade (animated or speed-tree dither), widen the transition by adjusting screen-size thresholds, and ensure the shader supports the dither clip the cross-fade needs.

LOD popping with no blend means the group is set to snap. Turning on cross-fade and spacing the screen-size thresholds turns the hard swap into an unnoticeable dither transition.

How to fix it

1. Enable LOD cross-fade

Set the LOD group's fade mode to Cross Fade so the engine dithers between the old and new mesh over a short range instead of switching in one frame.

2. Tune screen-size thresholds

Adjust the percentage thresholds so LOD swaps happen when each level is small enough that the change is hard to see, spacing them to avoid back-to-back pops.

3. Confirm shader cross-fade support

Cross-fade relies on a dither clip in the shader; verify the LOD materials support LOD_FADE_CROSSFADE or the fade will be ignored and popping returns.

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.

A crash you can name from its stack trace is a crash you can usually fix in minutes.