V-Ray Tip: Light Cache Workflow for Flicker-Free, Predictable Animation Renders

Secondary GI caching is the key to flicker-free animation with predictable render times. Here’s how to deploy it efficiently and safely across typical production scenarios.

When to cache secondary GI (Light Cache):

• Camera fly-throughs with static geometry and lights: reuse one cache for the whole path.
• Scenes with mild motion (doors, props, crowds), or animated lights/materials: compute and lock a cache per frame.
• Large interiors/exteriors where GI convergence is costly: precompute once, render many.

Recommended engines:

• Primary GI: Brute Force (stable for animation, no flicker).
• Secondary GI: Light Cache (cached to file for consistency and speed).

Fly-through workflow (static scene):

• Set Primary = Brute Force; Secondary = Light Cache.
• Enable “Use camera path” in Light Cache to sample the entire trajectory in a single prepass.
• Light Cache starting points:
  • Subdivs: 1500–2000 (HD), 2000–3000 (4K+).
  • Sample size: ~0.02–0.03 in world units (adjust to scene scale).
  • Retrace threshold: 2–4 to reduce leaks and dark edges.
  • Prefilter: On for smoother interpolation; Filter: e.g., “Nearest” or “Fixed” based on look tests.
• Save the Light Cache to file and switch mode to “From file” for final renders.
• Do not change geometry, materials, or lighting after caching; if you must, regenerate the cache.

Deforming/animated scenes:

• Keep Primary = Brute Force; Secondary = Light Cache computed per frame.
• Render a Light Cache prepass per frame using “Save to file,” then render with “From file” to lock GI across farm nodes.
• Avoid “Use camera path” when lights/materials/geometry change per frame—prefer per-frame caches.

Practical speed and stability tips:

• Target a consistent noise threshold (e.g., 0.01–0.02) after GI is cached; do not overcrank subdivisions globally.
• If you see GI shimmer:
  • Increase Light Cache Subdivs or lower sample size slightly.
  • Raise Retrace threshold or check flipped normals and thin geometry.
  • Reduce overly glossy materials or clamp highlights to mitigate fireflies.
• Name and version caches per sequence/shot (e.g., show_seq_shot_cam_LC_v003.vrlmap) and store on fast shared storage.
• For GPU renders, ensure enough VRAM headroom for the cache and textures; monitor usage during the prepass.

Irradiance Map note (legacy/if used):

• Use “Animation (prepass)” then “Animation (rendering)” to avoid flicker; keep Secondary = Light Cache “From file.”
• Prefer Brute Force primary for complex animation to minimize risk.

Pipeline hygiene:

• Lock caches before farm submission and use relative paths for portability.
• Embed cache version in the render stamp for traceability.
• For distributed/cloud rendering, export .vrscene with cache references preassigned.

Need help sizing caches for your shot or choosing a license? Talk to NOVEDGE. Upgrading V-Ray or expanding your farm? Check NOVEDGE’s Chaos catalog for options and expert guidance. For volume purchases or workflow audits, reach out to NOVEDGE—they’ll help you tune settings, budgets, and timelines.