Lumion Animation and Walkthrough Rendering for Film, Not Just Stills
A still frame from Lumion can look finished. However, if you send a camera move through the same scene, issues immediately appear. For instance, the sky starts to pulse. In addition, shadows shiver and colors shift between clips. None of that shows up in a still render because a still has no next frame to compare itself against.
Flickering light comes from Global Illumination recalculating. Specifically, this happens as the sun or an object moves. To fix this, Lumion recommends rendering at 4-star quality. Furthermore, you should keep the sun and moving objects still.
Shaky shadows come from model coordinates far from the scene center. Because GPUs store position values with limited precision, errors occur. Therefore, moving the model back to 0,0,0 solves the issue.
Finally, for delivery, export an image sequence. Editors and colorists prefer this format because it avoids video compression. Render time depends on frame rate, resolution, and quality. As a result, for 4K movies, Lumion requires a minimum 8GB VRAM floor.
Table of Contents
What Changes When the Camera Moves

Image Source: Lumion
A still image only needs to be correct once. A movie must be correct across thousands of frames. Every frame must agree on light, shadow, and color.
Motion surfaces three main failure types:
- Color mismatches between separately rendered clips.
- GI flicker from light probes recalculating.
- Shadow jitter caused by precision loss far from origin.
Common Motion-Only Errors and the Fix
| Symptom on the clip | Cause, per Lumion | Fix |
| Light or shadow flickers, especially indirect light | Global Illumination recalculating as the sun or an animated object moves | Render at 4-star quality, keep the sun and animated objects still, lower the Wind effect |
| Shadows jitter or edges crawl | Model sits far from the scene center, 0,0,0 | Group the model and move the group back to 0,0,0 |
| Foliage shakes erratically | Wind effect | Lower Wind on clips that need to stay stable |
| Render takes too long | Frame rate, resolution, quality level and heavy effects stacked together | Set frame rate per clip, strip heavy effects from clips that do not need them |
Fix the Flicker Before You Render
Check your model coordinates first. Models from CAD software often use real-world coordinates. This setup triggers shadow jitter. Group the model and move it toward 0,0,0 before doing anything else.
Next, decide if the sun needs to move in the shot. Lock the sun if movement is unnecessary. Finally, render a short 4-star test clip. Test the area with the heaviest GI and dense foliage. Flicker always shows up there first.
Delivering to an Edit: Image Sequences, Frame Rate, Resolution
Export through Render Clip or Render Movie, the Image Sequence tab, and Frame Range, which lets you render either a single clip or the entire movie as a numbered sequence of stills instead of one compressed file.
Choosing the Right Frame Rate
Lumion recommends 60fps mainly for fast camera movements or fast objects. Switching from 60fps to 30fps cuts render time roughly in half. You can set frame rates per clip instead of globally. This approach saves render time on slower clips. For film work, match your project timeline rate rather than rendering speed.
VRAM and Resolution Requirements
Lumion states that 4K movies require at least 8GB of VRAM. This memory threshold is mandatory for high-resolution exports.
Render Time and GPU Hardware Limits
Lumion relies on a single GPU only. It uses the card connected to your primary monitor. Installing extra GPUs will not speed up rendering. Technologies like SLI, NVLink, or Crossfire offer no performance gain.
VRAM Guidelines by Project Size
- Simple projects: ~6GB VRAM (PassMark score near 8,000).
- Complex scenes: ~10GB VRAM (PassMark score near 14,000).
- Detailed interiors with HD textures: 16GB VRAM or more.
- City or stadium scale projects: 32GB VRAM on professional cards.
- 4K video exports: 8GB VRAM minimum.
Managing Heavy Effects
The heaviest render effects include Sky Light, Hyperlight, Reflection Planes, dynamic shadow spotlights, 3D grass, and video textures. Strip these heavy effects per clip. Wide establishing shots can handle effects that tight interior shots cannot.
Cloud Rendering Options for Lumion
Lumion does not support traditional file-upload render farms. The software must be driven live on an active desktop. The best way to scale performance is renting a remote cloud workstation.
iRender offers Windows cloud machines with single RTX 4090 (24GB) or RTX 5090 (32GB) GPUs. You can install Lumion with your own license on the remote machine. Let the cloud server render your image sequence while your local PC stays free.
Maximum Speed – Absolute Freedom. Take control of your VFX workflow with iRender’s dedicated GPU servers. Render with iRender →
FAQ
1. Why does my Lumion movie flicker?
Movie flicker in Lumion is most often caused by Global Illumination recalculating itself as the sun or an animated object moves through the scene. GI places light probes near lit surfaces to simulate bounced light, and those probes get rearranged as the sun and any moving objects change position across frames, which shows up as flickering light or shadow. Lumion’s own fix is to render the clip at 4-star output quality, keep the sun and any animated objects static where you can, and lower the Wind effect so foliage is not adding extra motion into the same frames.
2. Why do shadows flicker in Lumion animations?
A different cause from lighting flicker: shaky or jittering shadows usually come from a model sitting too far from the center of the scene, position 0,0,0. The underlying reason is that the graphics card stores position values with limited precision, roughly eight digits, so a model placed at real-world site coordinates imported from CAD software can end up far enough from the origin that small rounding errors show up visually as shadow jitter. The fix is to group the affected model and move the group back toward 0,0,0.
3. Can Lumion export an image sequence?
Yes. Through Render Clip or Render Movie, the Image Sequence tab and the Frame Range setting, Lumion can export either a single clip or an entire movie as a numbered sequence of still images rather than one compressed video file. For a film delivery, a sequence is usually the better handoff to an editor or colorist, since it is a set of individual files rather than a single compressed stream.
4. How much VRAM do I need to render a 4K Lumion movie?
Lumion states that rendering a movie in 4K resolution requires a minimum of 8GB of graphics card memory. That is a floor for the resolution alone, not a guarantee for every scene at that resolution. Lumion’s broader VRAM guidance scales with scene complexity: around 6GB for a simple project, around 10GB for a more complex one, 16GB or more for a highly detailed interior with many models and HD textures, and at least 32GB on a professional card for city, airport or stadium-scale work. A dense 4K scene with heavy foliage or reflective surfaces will want more than the 8GB floor, not less.
See more: Redshift Out-of-Core in Houdini and Why VDB Ignores It
No comments