Fix Unity Light Probe Flickering on Moving Objects

A character who brightens and dims as they walk down a hallway has a lighting problem, not an animation problem. Unity computes a single spherical harmonic per renderer from the probe tetrahedron it is currently inside, and when the renderer crosses a boundary the SH switches abruptly. Close the gaps in the probe network, smooth the interpolation, and the flicker goes away.

Check probe density along the path

Open the scene and hit the scene-view overlay button labeled Light Probes. You will see the tetrahedralized mesh connecting your probes. Look at where your characters actually walk — corridors, doorways, stairs — and confirm probes are no more than one or two character widths apart. In rooms with strong colored light (red carpets, blue skylights) you want even denser coverage because the SH delta between tetrahedra is larger.

Add probe groups by right-clicking in the Hierarchy and choosing Light -> Light Probe Group. Unity does not auto-place probes; you have to sprinkle them yourself. A spacing rule of thumb is 1.5 meters in interiors and 4–6 meters in open exteriors.

Use a Light Probe Proxy Volume on big renderers

For anything larger than a meter cube — vehicles, bosses, rigid environment props — a single SH per renderer is not enough. The result is obvious popping when the pivot crosses a boundary even though most of the mesh is nowhere near it. Add a LightProbeProxyVolume component on the GameObject and set the MeshRenderer’s Light Probes mode to Use Proxy Volume:

var lppv = vehicle.AddComponent<LightProbeProxyVolume>();
lppv.resolutionMode = LightProbeProxyVolume.ResolutionMode.Custom;
lppv.gridResolutionX = 4;
lppv.gridResolutionY = 2;
lppv.gridResolutionZ = 4;
vehicle.GetComponent<MeshRenderer>().lightProbeUsage =
    UnityEngine.Rendering.LightProbeUsage.UseProxyVolume;

The proxy volume samples the probe network across a 3D grid inside the renderer’s bounds, so lighting varies smoothly across the mesh instead of snapping as the pivot crosses tetrahedra.

Fix the Anchor Override on irregular meshes

If a proxy volume is overkill, at least move the sample point to a stable spot on the character. By default Unity samples at the renderer’s transform position, which may be between the feet of a humanoid and thus under the floor. Assign an Anchor Override to a child transform at chest height:

meshRenderer.probeAnchor = chestBone;

This alone kills most of the visible flicker on characters, because the sample is no longer dipping into a probe located below the floor plane.

Match the lighting mode

Check your lights. A moving character using fully Baked lights will receive no direct illumination at all — the probes are the only thing lighting it, and any spatial change is a flicker. Mixed lights with the Shadowmask or Subtractive mode give the character real-time direct light while still using probes for bounce, which masks probe transitions.

On the MeshRenderer itself, set Light Probes to Blend Probes. The alternative, Off, disables probe lighting entirely, and Use Proxy Volume requires the component above.

Rebake after every probe change

Probe positions are only used at bake time. Moving a probe group and hitting Play without rebaking does nothing. Open the Lighting window and click Generate Lighting; watch the bake status until it finishes. On large scenes consider turning on GPU Progressive Lightmapper to shorten the iteration cycle.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Light probes are a static sampling grid. Moving characters need either a denser grid or a proxy volume — single-sample probes will always pop at some speed.”

Related Issues

For related rendering issues on moving geometry, see Fix Unity raytracing acceleration structure missing, and for a Godot take on bouncy lighting problems, Fix Godot 3D models inside out invisible.

Tip: if probes look right in editor but flicker in play mode, your character probably has a runtime script overriding probeAnchor.