OpenVDB --> instant crash

[Hesekiel2517]

Hallo,
if i load a openvdb file via the openvdbvoxelitem and hit render Modo crashes instantly. The vdb File is generated from Blender and loads both in the Standalone and the Modorenderer just fine. Is there a solution to this?

Great work on the Plugin by the way!

PS: I use the latest Versions of Modo, Blender, Octane and Octane Plugin

[face_off]

Hi - how exactly are you loading the vbd pls? Can you post a screenshot of how you did this? Are you able to also post the vdb pls?

Paul

[Hesekiel2517]

Hey Paul, sure:

Thank you for the fast reply!

[face_off]

if i load a openvdb file via the openvdbvoxelitem and hit render Modo crashes instantly. The vdb File is generated from Blender and loads both in the Standalone and the Modorenderer just fine. Is there a solution to this?

I have found the issue - and it will be fixed in the next release. In the meantime, pls do not attempt to render vdb files in the plugin.

Paul

[divljikunic]

Confirming the bug, is this fixed yet?

So, you think it will be possible to render vdbs normally (meaning they get rendered as volumes, not converted to geometry) in the plugin?
That'd be great, I need "real" fire in the fireplace not some compositing tricks..

[divljikunic]

Oh, btw, ran into this, hopefully it might help.. So, basically there's a type of compression that vdb version 3 uses which is not supported by the modo importer, however vdbs without it load fine..

http://community.thefoundry.co.uk/discu ... 9&t=109419

[face_off]

Confirming the bug, is this fixed yet?

Yes, fixed in the latest TEST release. Pls see https://docs.otoy.com/manuals/products/ ... -features/ for details. You can also add an Octane Override to the Volume Item Group in the Shader Tree and attach a NodeGraph node to it with a Volume Medium. However it's alpha-quality functionality at the moment, and will work better in the next release (at which time I'll explain the workflow better in the manual).

Paul