This node writes Bifrost point clouds and volumes to an OpenVDB file.
The Bifrost point clouds to write.
The Bifrost volumes to write.
If true, enables writing of files. Otherwise, node works as a passthrough.
The file name. Use # to include the input frame number. The number of occurences of # determines the amount of padding. For example, file####.vdb resolves to file0001.vdb, file0002.vdb, and so on.
The directory.
The frame number. You can connect the frame output of a time node to a to_long node, and then connect the result here.
If true, overwrites existing files.
If true, creates output directory hierarchy if it doesn't exist.
A space-delimited list of properties to write. Use * (asterisk) to specify all properties.
Controls the resolution rounding used when converting from Bifrost volumes to OpenVDB grids. Since Bifrost has more levels in its adaptive data structure than OpenVDB grids, voxel properties cannot be stored without conversion. In case of a mismatch you can choose to round the resolution up and avoid loss of resolution at the cost of higher resolution and thus larger file sizes. You can also choose to round the resolution down which saves space at the cost of some loss in resolution. As a compromise, you can opt to always round to the nearest possible resolution in OpenVDB. As a concrete example, consider a Bifrost volume with voxels with a voxel width of two. If you choose to "round up", these voxels will be stored as a 2x2x2 block of voxels in the OpenVDB grid. If you instead choose to "round down", the next level in the OpenVDB grid will be chosen, in this case that would be voxels with a voxel width of eight, and you would effectively have your resolution divided by four. Finally, in "nearest mode" a voxel width of two would (still) be "rounded up" and stored as a 2x2x2 block, while a voxel width of four would instead be "rounded down".
Passthrough of the input point clouds.
Passthrough of the input volumes.
True, if file was written successfully.
The full path of the written file.