VDB Export operator

The VDB Export operator can be used to export VDB data to disk.

Grids

  • SDF/Scalar/Vector: controls which VDB grids will be saved to the .vdb file.

When importing VDB data into another program, sometimes the naming scheme of each grid type is important. For example, certain software packages expect the SDF grid to be named “LevelSet” and the scalar grid to be named “Density”. To export grids with those names, make sure you’ve initialized the grids with those names elsewhere in your flow.

Output

  • Filename: the output path for the .vdb file.

Simulation

  • Auto-export during simulation: when enabled, .vdb files will be written automatically as the simulation progresses, after each time step.

Enabling this setting will cause any existing .vdb files in the output path to be overwritten, any time the simulation progresses.

Export

  • Generate VDB files: when pressed, the entire timeline will be simulated, exporting .vdb files after each timestep.

Because VDB data is not cached on a per-frame basis, a previously-cached sim must be recomputed during manual export.

VDB loaders

  • Notify loaders after export: when enabled, the specified VDB loaders will be refreshed after the .vdb file(s) are exported.

The VDB Export operator will attempt to notify scene VDB loaders that their data needs to be updated, but only some loaders are officially supported for this task. The officially supported loaders are: PhoenixFDFire containers and RedshiftVolumeGrid containers.