V-Ray Tip: Use the V-Ray Log to Identify and Fix Render Bottlenecks

The V-Ray log is your fastest path to understanding where time and noise come from. Read it, fix the bottleneck, re-test.

Open the V-Ray log

• From the V-Ray Frame Buffer (VFB), open the Log panel to watch events in real time.
• Set verbosity to Info (default) or Debug in Render Settings > V-Ray > System > Log level when you need deeper detail.

What to look for in slow or noisy renders

• Scene preparation spikes: Long “Geometry,” “Displacement,” or “Textures” stages indicate heavy pre-processing.
• Displacement explosions: Lines showing massive micro-triangle counts signal over-tessellation.
• Texture I/O churn: Repeated loading and high peak memory usage points to oversized, untiled maps.
• GI prepass taking too long: Light Cache/Brute Force stages dominating time suggest GI settings mismatch.
• Light evaluation overhead: Many complex area or mesh lights can flood shadow rays and create noise.
• GPU out-of-core: Messages about out-of-core memory mean VRAM is exceeded, causing big slowdowns.
• Denoiser cost: If denoising equals or exceeds render time, sampling is insufficient or too many AOVs feed the denoiser.

Fixes mapped to common log clues

• Slow Geometry/Displacement:
  • Switch heavy assets to V-Ray Proxies (.vrmesh); enable “Use Embree” (CPU) or RTX (GPU).
  • Use Adaptive (edge length-based) displacement; cap max subdivs; bake micro-detail into normal maps where possible.
• Texture I/O spikes:
  • Use V-Ray Bitmap with mip-mapping; convert large textures to tiled EXR; remove unused alpha channels.
  • Standardize resolutions by asset LOD and use triplanar for UV-poor assets to reduce oversized maps.
• GI prepass heavy:
  • Interiors: Brute Force + Light Cache with reasonable LC subdivs; avoid tiny LC filter sizes.
  • Exteriors: Consider Progressive with a slightly higher Noise Threshold for look-dev speed.
• Light evaluation slow/noisy:
  • Use Adaptive Lights; consolidate many tiny emitters into larger area lights where possible.
  • Lower reflection/refraction depth where extra bounces don’t affect the shot.
• GPU out-of-core:
  • Reduce texture sizes; prefer tiled EXR; enable mip-mapping; instance repeating assets.
  • Split renders into layers or upgrade VRAM; verify with the log that out-of-core disappears.
• Persistent fireflies/noise:
  • Enable Max Ray Intensity clamp; use realistic roughness; avoid tiny, ultra-bright light sources.
  • Use Denoiser as a final step (Intel OIDN on CPU or OptiX on GPU) after sampling is reasonably converged.

Fast workflow using the log

• Drop resolution and run a 30–60s IPR; read the log to identify the top two time sinks.
• Apply the targeted fix; compare in VFB History; repeat until the log shows time balanced across stages.
• Use a render stamp for versioning (time, sampler, noise threshold) to keep comparisons objective.

Need help tuning a specific pipeline? Connect with NOVEDGE or browse V-Ray options at NOVEDGE’s V-Ray catalog for expert guidance and licensing.