What causes light probe lighting popping on a moving character?

Probe lighting is interpolated across the tetrahedral cells between probes, and when probes are sparse or span a sharp lighting boundary the interpolated value jumps as the object crosses a cell edge.

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 Light Probe Interpolation Popping as a Character Moves

Quick answer: Add more probes around lighting transitions, avoid spanning a wall with a single tetrahedron, and use a probe anchor so the sample point does not whip between cells.

Popping lighting on a moving character means the probe field is too sparse where light changes fast, so each tetrahedron boundary produces a visible step. Densifying probes near transitions smooths the blend.

How to fix it

1. Densify probes at lighting transitions

Place probes closely on both sides of doorways, light cones, and shadow edges. Wide gaps force a single interpolation step to cover a large lighting change, which reads as a pop.

2. Do not let a tetrahedron cross a wall

Add probes hugging both faces of thin walls so no tetrahedron spans interior and exterior. A cell that straddles a wall blends bright outdoor light into the dark room.

3. Stabilize the sample point

Assign a Light Probe Anchor (or equivalent sample offset) at the character's mid-body so the lookup point moves smoothly instead of snapping with the pivot.

4. Rebake after every placement change

Probe coefficients are baked, so re-run the lighting bake after adjusting placement and walk the path again to confirm the popping is gone.

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