Quick answer: Increase the SDFGI ray count and frames-to-converge, raise the probe and normal bias to reduce self-lighting noise, and lower the camera speed of cascade scrolling if possible.

SDFGI flicker is cascades reconverging as the camera moves. More rays, more convergence frames, and higher bias smooth the indirect lighting during motion.

How to fix it

1. Raise rays and convergence frames

Increase the SDFGI rays-per-probe and the number of frames it accumulates over so newly streamed cascade regions resolve before they show as noise.

2. Increase probe and normal bias

Raise the SDFGI probe bias and normal bias to cut self-lighting and leaking, which removes much of the sparkle that reads as flicker on flat surfaces.

3. Reduce reaction speed

Lower how aggressively cascades update if the engine exposes it, trading a touch of latency for far more stable GI while the camera is in motion.

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