Versions Compared

Old Version 7

changes.mady.by.user Kristina Gaytandzhieva

Saved on

compared with

New Version Current

changes.mady.by.user Kristina Gaytandzhieva

Saved on

Key

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

...

Overview

The Input rollout determines the path of the input files for rendering and preview and the playback effects. Note that some playback settings require a fractional input frame, in which case the frame is blended between the previous and the next.

UI Text Box
typenote

Field3D files that come from FumeFX must be exported with gzip compression! If they are exported with the default proprietary FumeFX compression, they will not be imported properly in the V-Ray Volume Grid. 



Input

...

Section
Column
width52%50%

Volume Type – Determines what file type the Volume Grid is reading. The File Type supports the following cache files: Phoenix FD *.aur, Field3D *.f3d, and OpenVDB *.vdb. The VDB Generator allows Pyro Output objects to be linked to the Volume Grid, replicating the simulation while allowing the parameters of the Pyro simulation to still be editable.

Input Cache File – Gives the directory and the name template for the input files. Click the "..." to open a dialog for choosing one of several cache file types.

Column
width5%


Column
width45%

PNG File c4d2024_61030_VolumeGrid_Input_CacheFile1.pngImage Added

File Type


...

Section
Column
width50%

VDB Generator – Links a Pyro Output object to the Volume Grid. Drag and drop onto the field, or use the eyedropper tool. V-Ray recognizes it is a Pyro object, and a window pops up asking if you would like to use the Pyro preset. Click on Yes.
After linking the object, use the c4d2024_dropdownArrow.png button to expand the Pyro's parameters, and you can further edit them there or directly inside the Pyro Output and the Pyro tag. Changes are reflected everywhere. The Pyro Output object needs to be located in the current scene. NOTE: For the best results, when using the VDB Generator Volume Type, we recommend the Volume Grid's Render Mode be set to Volumetric. 

Column
width5%


PNG File c4d2024_61030_VolumeGrid_Input_CacheFile1.pngImage Removed

File Type
Column
width38%
45%

c4d2024_61030_VolumeGrid_Input_VDBGenerator.png

VDB Generator Type



UI Expand
titleClick Here to expand additional $(VARIABLE) and Channel Mapping information

$(work_path) – $(data_dir)/$(scene)_Phoenix_frames/$(nodename)_####.aur
$(data_path) – $(data_dir)/$(scene)_Phoenix2_frames/$(nodename)_####.aur
$(scene_path) – $(dir)/$(scene)_Phoenix_frames/$(nodename)_####.aur
$(scene_dir) – $(dir)/$(scene)_Phoenix2_frames/$(nodename)_####.aur
$(implicit) – Same as $(data_path).
$(dir) – The scene directory.
$(data_dir) – The current workspace data directory.
$(scene) – The scene file name.
$(nodename) – The name of the node.
$(fullname) – The full name of the node.
$(workspace) – The current workspace directory.
$env(<variable_name>) – An environment variable. See more about environment variables.

If you are transferring your scene and assets between Windows and Linux, prefixing your path with the $(workspace) or $env(<variable_name>) macros can make it possible to use the same scene without any manual modifications to the cache path.

Pound signs (i.e., hash) can be used to specify the cache frame number with at least as many digits as the pound signs. If the number of frame digits is less than the number of pound signs, the number is padded with zeroes to the left. For example:


Align
aligncenter

Result
Frame Number#######
11010001
1010100010
1000100010001000

...