Here are some demo videos which show the workflow of the openVDB node usage. If the resolution changes in the sequence due to larger occupied space of the volume data these initial values could be too small. But you can still use Fumefx with Octane if you use the. Octane just doesnt support native Fume files. After selecting the file the node stores the resolution of the selected file. I think its important to clarify that if youre using FumeFX 4, you can simulate OpenVDB files. The nx, ny, nz values set the resolution of the volume grid on each axis. Then you have to check the 'Use Bounding Box Offset' option to use the offset stored in each file. If you use an file sequence and the domain size changes form frame to frame the volume data will jitter or move unexpectedly. This is ok for still frames in most of the cases. Normally in LuxCore the VDB files are internally normalized to a range to fit in the domain bounding box. 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. The node still is in very early state and the UI elements are rather technical and will change in future versions. external files and file sequences created with other programs, e.g. VDB files created with the internal smoke simulation of Blender Here is an update of my work on the openVDB node in Blender.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |