3ds Max V-Ray Animation Flicker Between Frames: Stopping the Shimmer

Version note: this guide draws on the V-Ray Next help (an unofficial mirror) and on the current Chaos help. In current V-Ray the Irradiance map engine is marked deprecated and the Light Cache rollout lists only the Single frame and From file modes, so the Fly-through mode, Use camera path and Pre-filter steps below apply to V-Ray Next. The help for the NVIDIA AI denoiser also lists a Temporal mode; we have not tested whether it removes flicker.

What Causes V-Ray Animation Flicker Between Frames

Flicker means a value that should stay steady changes from frame to frame. In V-Ray the likely sources are the GI caches, the noise pattern and the denoiser. The table shows what the V-Ray Next help supports about V-Ray animation flicker between frames.

Fix 1: Find What Moves in the Shot

Decide whether only the camera moves, or objects and lights move too. The V-Ray Next help splits its recommendations on exactly that line: precomputed or fly-through caches for camera-only shots, and per-frame caches or blending for moving objects. Getting this wrong is a common reason a setup that worked in one shot causes V-Ray animation flicker between frames in the next.

Fix 2: Set the GI Caches for Animation

For V-Ray animation flicker between frames, the V-Ray Next help says the irradiance map is a biased solution that can flicker in animation. For long fly-throughs it suggests precalculating the map and reusing it, for shorter animations with a moving camera it suggests Use camera path, and for moving objects and lights it suggests animated maps with frame blending. Relevant modes include Single frame, Multiframe incremental, From file, Animation (prepass) and Animation (rendering).

Animation (prepass) creates one map per frame in its own file, every frame must be rendered, and the final image is not rendered. Animation (rendering) then renders from those maps and blends adjacent maps to reduce flicker. Interp. frames creates twice the value plus one maps, and higher values reduce flicker but can cause lag.

The same page says removing flicker completely may not be possible and that Brute Force as the primary GI engine may be the best option.

For the light cache, the same help says it is biased and can cause flicker. Both caches are places to look for V-Ray animation flicker between frames. Its Fly-through mode computes one cache at the first rendered frame and reuses it, on the assumption that only the camera moves. Use camera path calculates samples for the whole camera path so sample positions on static geometry stay fixed, and the help suggests it for short camera moves with moving objects.

A Chaos staff member wrote in a 2015 forum post, for V-Ray 3.x, that Use camera path reduces flickering from light cache samples landing in different positions but does not fix flicker on moving objects, and that Single frame mode is simpler.

For moving objects, the help gives an example setup with Retrace at 8.0 instead of 2.0 for stills, Pre-filter on with 20 samples, Subdivs at 3000 and Sample size 0.01. Treat those numbers as the documentation’s example, not universal values.

Fix 3: Lock the Noise Pattern

A changing noise pattern can add to V-Ray animation flicker between frames. In V-Ray Next the Global DMC settings include Lock noise pattern (the current help places it in the Image Sampler rollout), which keeps the sampling pattern identical from frame to frame. Turning it off lets the pattern change over time, and re-rendering the same frame gives the same result either way. The denoiser page says enabling Lock noise pattern generally improves animation results. We found no documentation that ties Use local subdivs to flicker.

Fix 4: Denoise With Frame Blending

Denoising can add V-Ray animation flicker between frames when each frame is processed alone. The V-Ray Next help states that the integrated VRayDenoiser processes a single frame and ignores neighboring frames, and recommends the standalone vdenoise tool for animation, which blends frames. Render raw output with the denoiser in the mode that only generates render elements, save .vrimg or multichannel EXR, then run vdenoise. Blend Frames in the interface, or -frameBlend on the command line, sets how many adjacent frames are used, with a default of 1, meaning one before and one after. Higher values reduce flicker but are slower, and all frames must be rendered first.

The help also says the NVIDIA AI denoiser does not blend frames and will likely produce flickering. Chaos’s own blog says animations denoised frame by frame can show swimming patterns between frames. For detail loss from denoising, see denoiser losing detail in animation.

Fix 5: Keep Every Render Node Consistent

On a farm, V-Ray animation flicker between frames can also come from inconsistent nodes, and our inference is that every node must use the same GI cache files and see the same textures, otherwise frames rendered on different machines will not match.

The V-Ray Next help supports the parts: the irradiance map From file mode suits fly-throughs and network rendering, Auto save writes the map when rendering finishes so it can be sent to another machine, and light cache Auto save with %04d in the file name saves one file per frame. In distributed rendering, a missing texture renders as if switched off unless Check for missing files is enabled, in which case the server refuses to render the scene. If you are comparing services for animation, see our top 10 render farms comparison.

Where V-Ray Animation Flicker Between Frames Comes From: Three Sources

V-Ray animation flicker between frames has three documented sources: GI caches that differ per frame, a noise pattern that changes, and a denoiser that treats each frame alone. The figure maps each source to the fix in this guide.

Choosing a GI Cache Mode: Camera-Only Shots Versus Moving Objects

The V-Ray Next help splits its advice on one question: does only the camera move, or do objects and lights move too? Pick the cache mode from that answer instead of copying a setup from a different shot.

Step-by-Step Check for V-Ray Animation Flicker Between Frames

Run these steps on a short range of frames, because flicker is easiest to see in a short loop. Change one setting at a time.

1. Find what moves. Decide whether only the camera moves, or objects and lights move too.
2. Set the GI caches. Use a precomputed or fly-through cache for camera-only shots, and animated maps with frame blending for moving objects.
3. Lock the noise pattern. Enable Lock noise pattern, which the denoiser page says generally improves animation results.
4. Render raw output. Set the denoiser to the mode that only generates render elements, and save .vrimg or multichannel EXR.
5. Denoise with blending. Run the standalone vdenoise tool with Blend Frames, or -frameBlend on the command line.
6. Check the farm. Make sure every node uses the same cache files and sees the same textures, then compare a loop rendered on two machines.

What We Could Not Verify

We could not read Chaos’s current V-Ray 5, 6 or 7 documentation, so we cannot confirm that the setting names and modes above are unchanged. We found no documentation that Progressive path tracing cures GI flicker, that a denoiser mode named Animation exists in the 3ds Max denoiser, or that procedurals, displacement, fur or Light Mix cause flicker. Test one change at a time on a short range of frames, since V-Ray animation flicker between frames is easiest to see in a short loop.

Sources

• V-Ray Next for 3ds Max help, Irradiance Map (unofficial mirror of the Chaos help): vmax-doc-next.vercel.app (checked 2 November 2026)
• V-Ray Next for 3ds Max help, Light Cache (unofficial mirror): vmax-doc-next.vercel.app (checked 2 November 2026)
• V-Ray Next for 3ds Max help, Global DMC Settings (unofficial mirror): vmax-doc-next.vercel.app (checked 2 November 2026)
• V-Ray Next for 3ds Max help, V-Ray Denoiser (unofficial mirror): vmax-doc-next.vercel.app (checked 2 November 2026)
• V-Ray Next for 3ds Max help, Denoiser Tool (unofficial mirror): vmax-doc-next.vercel.app (checked 2 November 2026)
• V-Ray Next for 3ds Max help, Set Up Distributed Rendering (unofficial mirror): vmax-doc-next.vercel.app (checked 2 November 2026)
• Chaos Blog, V-Ray Next denoising in production: blog.chaos.com (checked 2 November 2026)
• Chaos Forums, Use Camera Path explanation (staff post, 2015, V-Ray 3.x): forums.chaos.com (checked 2 November 2026)

FAQ