Versions Compared

Old Version 4

changes.mady.by.user Gergana Lilkova

Saved on

compared with

New Version Current

changes.mady.by.user Slavina Nikolova

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page provides some useful tips for rendering volumetric effects.

 

Volumetric vs Volumetric Geometry mode when rendering on the CPU

...

The Volumetric Geometry mode is provided as an option for the following reasons:

...

  1. The Volumetric Geometry mode does not work with Probabilistic Volumetrics.
  2. The Volumetric Geometry mode tends to be slower to render. Ideally, you should work in Volumetric mode all the time and switch to Volumetric Geometry only when generating the Render Element passes.
  3. The Approximate and Approximate+Shadows Scattering options under Volumetric Render Settings → Smoke Color are not supported in Volumetric Geometry mode. It would default to Disabled scattering.
  4. You may need to increase the V-Ray Settings → Global Switches → Advanced toggle → Max.Transparency Levels option which will slow-down rendering. When rendering in Volumetric Geometry mode, procedural geometry made up from multiple transparent layers is generated at render-time. Think of it as sprites used in video games - a sequence of slices facing the camera.
  5. The default 3ds Max Scanline renderer is not supported.

...

UI Text Box
sizemedium
typetip

 When rendering with V-Ray GPU, the Render Mode does not matter - Render Elements are generated and the rendering speed is the same in both the Volumetric and Volumetric Geometry modes.

 

AUR vs VDB Cache Format

...

Section
Column
width40%

VDBs render slower than AUR files.

The VDB layout which makes it possible to render huge sparse-grid volumes makes rendering everyday volumes slower than the dense-grid AUR format.

If you can choose between AUR and VDB, go with AUR when possible. The rendering speed-up with AUR files can go up to 2x depending on the complexity of the setup.

Furthermore, resimulation results when using VDBs as a base usually differ from the results when using AUR files due to differences in the default compression methods.

Column
width60%
Image slider
Panel
borderStylenone


Resimulation stored as AUR , Render TIme: 3m 45 seconds.

Panel
borderStylenone


Resimulation stored as VDB, Render TIme: 6m 28 seconds.

 

Core Volumetric Shader Settings

...

Section
Column
width40%

Rendering roll-out rollout → Step %

The Step % parameter is the main sampling control when rendering volumetric effects. The higher you can set the Step %, the faster the rendering will go. Eventually artifacts will start to appear for very high values, so that is where you must stop increasing the Step %.

The Step % option specifies the ray marching step of the camera rays as a percentage of the cell size. As the renderer traces rays through the volume grid, this value controls how often to get information from the grid. If the Step % is more than 100, some cells will be skipped and artifacts may appear. A lower percentage might be necessary so that fine details are not lost when custom changes are made to the Opacity curves for Fire / Smoke.

Column
width60%
Image slider
Panel
borderStylenone


Step %: 90, Render Time: 4m 58seconds.

Panel
borderStylenone


Step %: 200, Render Time: 2m 01 seconds.

Panel
borderStylenone


Step %: 300 , Render Time: 1m 49 seconds.

...

Section
Column
width40%

Rendering roll-out rollout → Shadow Step %

The Shadow Step % is similar to the Step % in a sense that it is responsible for the sampling quality of the volume but for the shadows cast by the volume over itself and the surrounding objects only. The higher you can set the Shadow Step %, the faster the rendering will go. Eventually the shadows will become washed out for very high values, so that is where you must stop increasing the Shadow Step %.

Column
width60%
Column
width60%
Image slider
Panel
borderStylenone


Step %: 200 , Shadow Step %: 200, Render Time: 2m 02 seconds.

Panel
borderStylenone


Step %: 200 , Shadow Step %: 400 , Render Time: 1m 38 seconds.

Panel
borderStylenone


Step %: 200 , Shadow Step %: 800, Render Time: 1m 36 seconds.

...

Section
Column
width40%

Volumetric Options → Smoke Color → Use Light Cache | Light Cache Speedup

In general, for lower-resolution simulations, the Volume Grid Light Cache will significantly speed up the rendering. As the resolution increases, the benefit from using the Volume Grid Light Cache diminishes. If Use Light Cache is disabled, try enabling it to check if that will speed-up the rendering. You can reduce the render times significantly by increasing the Light Cache Speedup setting. Increasing it from 0.9 to 0.99 to 0.999 should yield a big difference in render speed.

The Light Cache Speedup should be increased until artifacts start appearing in the rendered image. Grid Light Cache artifacts will look like voxel-sized dark and bright spots. They would also flicker in animation. Grid artifacts start appearing when a voxel does not get to cast enough shadow rays – this is usually related to the lighting setup – e.g. the illumination is too dim, there are too many grids in the scene, etc. If you see these artifacts, then your Light Cache Speedup is too high and you have to decrease it. If decreasing it to zero still does not help, disable the Light Cache.

Disable the Use Light Cache option if:

  1. Reducing the Light Cache Speedup option to zero does not help resolve artifacts in the smoke. If you see bright and dark voxels, this means the light cache speedup is too high. If you see pixel sized noise, then it's the sampling - you should adjust the V-Ray settings accordingly (e.g. increasing the Max Subdivs for the Bucket Sampler).
  2. You are rendering an animation and you notice flickering which will not go away after reducing the Light Cache Speedup.
  3. You are using Progressive rendering.
  4. There are multiple grids in the scene - for a large number of grids in the same scene, disabling the Volume Grid Light Cache might speed things up, as opposed to a single grid where it's best to keep it enabled.
Column
width60%
Column
width60%
Column
width60%
Image slider
Panel
borderStylenone


Use Light Cache: disabled , Render Time: 11m 34s.

Panel
borderStylenone


Use Light Cache: enabled , Speed-up: 0.9 , Render Time: 32m 42s.

Panel
borderStylenone


Use Light Cache: enabled , Speed-up: 0.99 , Render Time: 7m 17s.

Panel
borderStylenone


Use Light Cache: enabled , Speed-up: 0.999 , Render Time: 1m 49s.

UI Text Box
sizemedium
typetip

When rendering with V-Ray GPU, the Use Light Cache option is ignored entirely - the Volume Grid Light Cache is a CPU-only 'hack' used to speed up CPU rendering.

...

Section
Column
width40%

Volumetric Options → Fire / Smoke Color / Smoke Opacity roll-outsrollouts.

If using any textures for modulating / replacing the Fire, Smoke Color or Smoke Opacity, disable them to check how the rendering speed compares. Some textures and complex texture networks can be slow to evaluate and render.

Column
width60%
Image slider
Panel
borderStylenone


Smoke Color → Modulate by Texture: enabled , Texture: Gradient Ramp , Render Time: 49 seconds.

Panel
borderStylenone


Smoke Color → Modulate By Texture: disabled , Render Time: 40 seconds.

...

Section
Column
width40%

Volumetric Options → Smoke Opacity → Optimize Big Volumetric Grids

When enabled, an optimization pre-pass over each grid in the scene will be run to speed up the rendering process.

It's best to keep this option enabled unless:

  1. You are low on RAM - this option requires additional memory during rendering, so you could disable it if you don't have enough RAM.
  2. Multiple Volumetric Grids are present in the scene - a pre-pass will be run for each grid - this may delay the rendering start long enough to negate the render speed gains from the optimization.
  3. Progressive Rendering is enabled - the pre-pass will delay the start of the rendering process - you may want to disable it if that behavior is undesirable
UI Text Box
sizemedium
typetip

This parameter only affects the rendering speed - the quality of the rendered image is not affected.

Column
width60%
Image slider
Panel
borderStylenone


Optimize Big Volumetric Grids: disabled , Render Time: 3m 31s.

Panel
borderStylenone


Optimize Big Volumetric Grids: enabled, Render Time: 2m 21s.

...

Section
Column

Volumetric Options → Fire → Create Fire Lights

Enabling Create Fire Lights simulates Global Illumination by placing light sources in the bright parts of the fire, which produces similar results and renders much faster. It can be used in with both GI on and off as well, because it would help in cases where large environments need to be illuminated by very small, very bright Fire Lights.

Disable Create Fire Lights - if this speeds up the rendering significantly then you can experiment with the options in the Fire Lights section.

UI Text Box
sizemedium
typetip

When rendering with V-Ray GPU, the Fire Lights options are ignored entirely. Global Illumination should be enabled from the V-Ray Settings if you need the Smoke and/or the scene to be illuminated by the fire.

Column
width60%
Image slider
Panel
borderStylenone


Create Fire Lights Enabled, Grid-Based Self-Shadowing , Light Resolution: 25% , Render Time: 14m 45 seconds

Panel
borderStylenone


Create Fire Lights Disabled, Render Time: 1h 0m 03 seconds

...

Section
Column
width40%

For very simple scenes, setting the V-Ray Settings → Global Switches → Advanced → Adaptive lights drop-down to Full Lights Evaluation may speed up the rendering of volumetric effects.

For more information on Adaptive Lights, take a look at the Understanding Adaptive Lights article.

Column
width60%

 

Smoke Opacity and Probabilistic Volumetrics

...

Section
Column
width40%

Thick (highly opaque) Smoke renders faster than thin (highly transparent) Smoke because the lighting calculations for voxels completely hidden behind other, opaque voxels, can be skipped entirely.

If your Smoke is dense, you can speed up rendering further try enabling the Use Probabilistic Shading option in the Environment and Effects window to see if that gives you a boost in render speeds.

If your Smoke is highly transparent, Probabilistic Volumetrics won't make much of a difference, and in some cases may even slow down your renders.

If V-Ray's Global Illumination is enabled, the number of GI Samples will heavily affect the render times. Both high and low values will increase the render time - you should aim to find a good value somewhere in the middle.

Column
width60%
Image slider
Panel
borderStylenone


Probabilistic Shading: disabled , Render Time: 91s.

Panel
borderStylenone


Probabilistic Shading: enabled, Render Time: 54s.

 

V-Ray Adv vs V-Ray GPU Rendering of Volumetric effects

...

Section
Column
width40%

All options under the Rendering roll-out rollout are supported by V-Ray Adv (CPU).

The following options are not supported by V-Ray GPU:

  1. Smoke Color → Scattering → Approximate & Approximate+Shadows - V-Ray GPU is significantly faster when using the Ray-Traced (GI Only) option. V-Ray Global Illumination should be enabled for this option to have any effect.
  2. Smoke Color → Use Light Cache. This option refers to the internal Volume Grid Light Cache,  which is not related to the V-Ray Light Cache. It's a CPU-only feature that helps speed up Bucket rendering.
  3. Fire → Fire Lights. All Fire Lights options are ignored when rendering with V-Ray GPU. Enable Global Illumination from the V-Ray Settings if you need the Smoke and/or the scene to be illuminated by the fire.
Column
width60%
Image slider
Panel
borderStylenone


V-Ray Next Adv. CPU with Brute Force / Brute Force GI

Panel
borderStylenone


V-Ray Next GPU with Brute Force / Brute Force GI