Why Your Arch-Viz Animation Flickers (Denoiser and Sampling Explained)

Arch-viz animation flickers because each frame is rendered independently, so its leftover noise and global illumination errors differ from the frame before. Three sources cause most of it. Light noise that is invisible in a still becomes visible motion at 25 or 30 frames per second. A denoiser applied to each frame separately can produce what Chaos calls swimming patterns, which is why Chaos offers a standalone denoiser that processes the whole sequence using neighbouring frames. A GI cache such as the light cache, recalculated for every frame, adds shifting errors to indirect light. For camera-only walkthroughs, calculate the cache once for the whole camera path and reuse it, render with a little less leftover noise than for stills, and denoise the sequence temporally.

You just sent a 40-second walkthrough video to your client, and their immediate response is, “Why is the ceiling flickering?”

Every 3D artist has been there. A still frame looks perfectly clean on its own, but as soon as you sequence those frames into a full animation, flat walls start boiling, soft shadows dance around furniture, and indirect lighting pulses with every camera step. In this article, Radar Render breaks down why this frame-to-frame flickering happens and explores the three main causes behind it: leftover rendering noise, per-frame denoiser artifacts, and recalculated global illumination caches. We will also walk through practical solutions to fix each issue so your animation renders remain smooth and stable.

 

Why do frames that look clean as stills flicker in motion?

Source: chaos

A still image and an animation frame handle noise differently. When you render a single architectural image, a small amount of grain on a dark wall or under a sofa easily blends into the texture and goes unnoticed.

However, when you string 30 of those frames together into one second of video, that grain stops being static. Because path tracers use different random sampling seeds for every frame, a pixel that is dark on frame 1 might turn bright on frame 2, and dark again on frame 3. Your eyes perceive this constant frame-to-frame shift as an annoying “boiling” motion.

In architectural visualization, this issue shows up most often on:

• Large flat walls or plain drywall
• Ceilings illuminated by indirect bounce light
• Soft contact shadows beneath furniture

To eliminate this artifact, animations require a lower noise threshold than still renders, along with proper handling of denoisers and global illumination calculations across consecutive frames. 

 

How do I find out what is causing the flicker?

Finding the cause of a flicker requires a quick test. Do not waste time re-rendering your entire video at full resolution. Instead, pick a short 20 to 30 frame clip where the flickering looks worst, and test one setting at a time.

Turn off your denoiser completely and render the test clip. If the flickering stops and turns into simple, steady grain, your denoiser was causing the problem by smoothing each frame differently.

If the raw render still flickers in large light patches, lock your global illumination cache. Calculate one GI cache file for the entire camera move and force your render engine to reuse that file for all frames. If the light stops pulsing, your GI settings are recalculating light differently on every frame.

If you still see fine, fast-moving pepper noise across dark areas even with a locked GI cache, your render noise threshold is simply set too high for video.

Always run these test clips at your final render resolution. Low-resolution previews hide fine noise and make denoisers act differently than they do on full 4K images.

 

Is my denoiser causing the flicker?

Denoisers are a primary cause of animation flicker. When a denoiser cleans each frame on its own, it creates slightly different patterns from one frame to the next. Chaos calls these shifting spots “swimming patterns.”

V-Ray Denoising

To fix this in V-Ray, render your sequence with the denoiser render elements turned on, but run Chaos’s standalone tool after the render finishes. This tool looks at frames before and after the current frame to blend noise smoothly over time.

NVIDIA AI Denoiser

NVIDIA AI Denoiser works great for fast viewport previews, but Chaos warns against using it for final animations because it cleans every frame differently.

Corona Denoising

Intel AI Denoiser in Corona also lacks frame-to-frame stability. For clean Corona animations, use Corona’s built-in temporal denoising options or render with lower noise limits without heavy AI smoothing.

Using a standalone denoiser after rendering also lets you tweak smoothing levels without re-rendering your scene.

 

Why does indirect light flicker, and what does the light cache have to do with it?

Global illumination engines speed up rendering by estimating light bounces instead of calculating every light ray manually. Tools like V-Ray’s Light Cache or Corona’s UHD Cache build a quick map of these lighting estimates. When your engine recalculates this map for every single frame, tiny mathematical differences cause indirect light to pulse and shift from one frame to the next.

For camera-only walkthroughs where geometry, lights, and materials do not move, you can stop this flickering by baking a single light cache for the entire camera move. In V-Ray, set the Light Cache mode to calculate along the camera path (such as Fly-through mode or reading from a pre-saved file), save that file to your drive, and set every render node to read from that single file.

During a hotel lobby project, a plaster ceiling seemed to “breathe” with light shifts every few frames. Doubling the samples did not fix it. Once we calculated the Light Cache once for the entire camera trajectory and locked it to disk, the ceiling light stayed completely solid.

If your scene has moving objects like opening doors, walking people, or swaying trees a static camera cache will create ugly light halos around those moving parts. For scenes with dynamic objects, use per-frame GI modes built for motion, or rely on native path tracing with enough samples to keep lighting steady.

 

Should I just raise the samples?

Lowering your noise threshold is necessary for clean animation output, but blindly increasing sample counts without fixing your GI cache or denoiser settings is inefficient and expensive.

Path tracing noise reduction follows an inverse-square relationship. To cut render noise in half, your engine needs roughly four times as many samples per pixel, which quadruples your render times.

Before increasing sample counts across the board:

1. Fix your GI cache workflow (use locked or temporal caches).
2. Switch to a temporally balanced, post-render denoiser.
3. Clamp sub-pixel highlights to eliminate “fireflies” (isolated bright pixels caused by high-intensity light reflections on metallic or glass surfaces).

Once those three elements are configured correctly, lower your noise threshold just enough to eliminate residual grain.

 

Does rendering the animation on several machines make the flicker worse?

Splitting an animation sequence across multiple render machines can introduce sudden lighting jumps if the nodes are not configured identically. If Machine A runs a different plugin build than Machine B, or if each node calculates its own local GI cache on the fly, the frame rendered at the boundary (such as moving from Frame 150 on Node A to Frame 151 on Node B) will show a visible shift in lighting or noise distribution.

To maintain complete consistency across a distributed render:

• Install matching versions of your 3D application, rendering engine, and active plugins on every node.
• Use the exact same project file and texture paths across all systems.
• Force every render node to read from the same pre-calculated GI cache file on a shared network path.

Real-time arch-viz tools like Lumion, Enscape, Twinmotion, and D5 Render experience flickering due to different real-time mechanics, such as temporal anti-aliasing (TAA) shifts, shadow map resolution limits, and dynamic auto-exposure adjustments. 

 

Ready to Render Your Walkthrough Without Flicker?

Once your GI cache is locked and temporal denoising is configured, rendering a long animation sequence locally can still take days on a single workstation.

If you need to meet a tight deadline without compromising render quality, iRender provides high-performance cloud GPU workstations equipped with the latest NVIDIA RTX 5090 (32GB VRAM). Thanks to the IaaS model, you get full desktop control to install your exact 3D software version, set up custom plugins, and point all render jobs to a single pre-calculated GI cache file.

For multi-machine setups, you can also rent identical RTX 4090 nodes to split your frame ranges while maintaining 100% visual consistency across every boundary.

> Claim Your 100% Bonus & Test RTX 5090 GPUs on iRender

 

FAQ

1. Why does my V-Ray animation flicker when stills look fine?

Animations flicker because each frame is rendered independently with its own random sampling pattern and global illumination calculations. While slight noise remains unnoticed in a single still image, playing those frames sequentially at 25 or 30 frames per second turns that variance into visible motion. The primary causes are per-frame denoising artifacts, recalculated light caches, and noise thresholds that are too high for video delivery.

2. Does the denoiser cause flicker in animation?

Yes. Applying a denoiser independently to each frame can cause what Chaos calls “swimming patterns,” where smoothed details shift unnaturally from frame to frame. Chaos recommends using their standalone denoising tool (vdenoise) on the completed frame sequence. This tool evaluates neighboring frames to generate a temporally balanced result without motion artifacts.

3. How do I stop light cache flicker in a walkthrough?

For camera-only walkthroughs where scene objects remain static, pre-calculate the Light Cache along the entire camera path once, save it as a file, and configure your render settings to load that static cache file for every frame. This ensures that every frame uses identical indirect lighting estimates. If your scene contains moving objects, use per-frame animation GI modes instead.

4. Will more samples fix animation flicker?

Increasing sample counts reduces raw noise, but it will not fix flickering caused by per-frame denoiser calculations or shifting GI light caches. Because reducing noise by half requires roughly four times as many samples, raising sample counts is the most time-consuming fix. Fix your GI cache strategy and temporal denoising workflow before lowering your noise threshold.

See more: Why Lumion Render Quality Drops on Animation vs Stills