Here is an update of my work on the openVDB node in Blender. Via this node you currently can use
- VDB files created with the internal smoke simulation of Blender
- external files and file sequences created with other programs, e.g. Houdini
The node still is in very early state and the UI elements are rather technical and will change in future versions.
The automatic file sequence detection for VDB files from Blender cache doesn't work yet but you can use the "use internal cache files" option to get the files directly from blender.
Normally in LuxCore the VDB files are internally normalized to a [0...1] range to fit in the domain bounding box. This is ok for still frames in most of the cases. If you use an file sequence and the domain size changes form frame to frame the volume data will jitter or move unexpectedly. Then you have to check the 'Use Bounding Box Offset' option to use the offset stored in each file.
The nx, ny, nz values set the resolution of the volume grid on each axis. After selecting the file the node stores the resolution of the selected file. If the resolution changes in the sequence due to larger occupied space of the volume data these initial values could be too small.
Here are some demo videos which show the workflow of the openVDB node usage.
https://www.youtube.com/playlist?list=P ... wLtBVku72G
Blender smoke simulation:
Houdini cloud bunny test file:
Houdini buddha test file:
i7 5820K, 32 GB RAM, NVIDIA Geforce GTX 1080 + GTX 780, Windows 10 64bit, Blender 2.79b
Support LuxCoreRender project with salts