Delayed Lumen lighting updates when a character rotates toward a movable light during a Sequencer cinematic

Development Rendering
,
1

I’m experiencing a lighting update delay in a Sequencer cinematic.

I have a character moving and rotating toward a movable light. When the character rotates and faces the light, the lighting response on the character/environment does not update immediately. Instead, there is a noticeable delay before the new lighting state becomes visible.

The light itself is not fading or being animated with a fade. The issue appears to be related to the lighting/rendering update, because the character rotation happens immediately while the lighting response seems to catch up a few frames later.

My setup:

  • Unreal Engine 5

  • Lumen enabled

  • Movable light

  • Cinematic created in Sequencer

  • Character is rotating/moving during the sequence

I have already tried several approaches to force or improve the Lumen updates, including:

  • Manually controlling Auto Exposure — no improvement

  • Increasing/changing Lumen Final Gather settings — no improvement

  • Increasing/changing Lumen Final Gather Update settings — no improvement

  • Changing Lumen Scene Update settings — no improvement

  • Using console/settings related to forcing Final Gather updates — no improvement

The problem is still present.

I’m looking for a way to make the Lumen lighting response update immediately when the character rotates, without the visible temporal delay.

2

that delay is the lumen surface cache on the character lagging the camera swing. the cache is not rebuilt every frame, each mesh gets re-cached on a shared budget, so a fast rotation toward a bright movable light exposes stale cache frames until the update lands, and it reads as lighting that arrives late.

confirm it in one toggle: enable Lumen Hardware Ray Tracing (project settings plus the post process GI override). hardware ray traced lumen traces real geometry instead of the surface cache, so if the delay disappears it is confirmed cache staleness, not your light or sequencer setup.

to make the cache path behave: give the character a proper distance field (generate mesh distance fields on, check the character’s DF resolution in the stats), raise Lumen Final Gather Quality in the post process volume so each frame pulls more trace samples, and raise Lumen Scene Detail so the cached character is represented better. on the light, “Affect Distance Field Lighting” on helps the far field react. if it still lags, r.ScreenPercentage down a notch frees budget that lumen spends on cache updates.

cinematic specific: movie render queue with the lumen “force update every frame” style console variables on does the whole thing at final quality per frame, which is the right tool for a sequencer render anyway.