What causes flickering shadows?

The shadow map lacks resolution or stable sampling, so shadow edges crawl and shimmer as the camera moves, and incorrect bias produces flicker or detached shadows.

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 Flickering or Shimmering Shadows in a Game

Quick answer: Increase shadow resolution where needed, stabilize the shadow cascades, and tune the shadow bias to remove acne and peter-panning without introducing flicker.

Shimmering shadows are a shadow-map stability and bias problem. Tuning resolution, stabilization, and bias fixes it. Here is how.

How to fix it

1. Increase and stabilize the shadow map

Low shadow resolution makes edges crawl. Raise it where it matters and enable cascade or texel-snapping stabilization so the shadow map does not shimmer as the camera moves.

2. Tune the bias

Too little shadow bias causes shadow acne (flickering self-shadowing); too much detaches shadows from objects (peter-panning). Tune the bias and normal bias to the sweet spot that removes both.

3. Match settings to the scene

Large outdoor scenes need cascaded shadows tuned for distance; small scenes need higher local resolution. Set the cascade distances and resolution to the scene so shadows are stable across the view.

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 your game 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 errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.