Hey there
1. I want to verify, is there a way to render VDB directly from Houdini VDB? Or it can be still only loaded from the OBJ params VDB file?
I've tried first to render as Volume in OBJ params, but it takes more than a minute to load a frame (16mil voxels). VDB file is fast.
2. Also, it was a weird bug once with volumes not in a right place in render relative to camera, I think I had it when was rendering as volume and not VDB file, or is it fixed?
3. Also, I've tried to render it in Solaris. Tried to resemble the setup that is in Solaris release post (with explosion), loading with Volume LOP, but I couldn't assign a material. It was loading instantaneous, but rendering black, and in console was written unable to find a material /materials/octane_vopnet1, which was assigned and had a Volume medium connected to medium output gray input.
Thanks
VDB rendering
Moderator: juanjgon
The main Houdini plugin can render both "volume" and "vdb" Houdini primitives directly, extracting them at the scene extraction time. Extracting "vdb" primitives can be a bit slow, so it is better to convert them to "volumes" or even better, work with OpenVDB files that are loaded by Octane at the render time, so the extraction time is almost 0 and the CPU memory used in the extraction is also minimal. Working with OpenVDB files is always recommended, if possible.
Thanks,
-Juanjo
Thanks,
-Juanjo
juanjgon wrote:The main Houdini plugin can render both "volume" and "vdb" Houdini primitives directly, extracting them at the scene extraction time. Extracting "vdb" primitives can be a bit slow, so it is better to convert them to "volumes" or even better, work with OpenVDB files that are loaded by Octane at the render time, so the extraction time is almost 0 and the CPU memory used in the extraction is also minimal. Working with OpenVDB files is always recommended, if possible.
Thanks,
-Juanjo
yes, thanks, that's what I've been facing. Converting to Volumes is slow.
Can you please elaborate on question 3 in original post about Solaris?
Thanks