Can't Render openvdb

[yaseunghee]

When I used Octane V3.03 and Modo 11, rendering openvdb files in modo render is normal but Octane is abnormal.

Now i use Octane V3.06 and Modo 11 when i render openvdb files in octane, it writes this message.

A first Image is render with octane but failed and a second image is render with modo 11.

[face_off]

The error msg is saying to look in the Octane Log. What did the Octane Log say pls?

Paul

[yaseunghee]

Oh, I forgot attaching a log.

like this.

[face_off]

Thanks. Can you send me the VDB file pls?

Paul

[Greggers]

I had the same issue a little while ago but I gave up. It would be interesting to see how to resolve this one paul. I know mine turned out like that when I exported a vdb from blender. I thought it was the blender end causing the issue when setting up to export. exporting. There are videos on you tube explaining the creation of smoke in blender and exporting it as a vdb.

[yaseunghee]

i send a message with file to you.

[face_off]

i send a message with file to you.

Hi - I have not received this file yet.

Paul

[yaseunghee]

Maybe i mailed wrong way..

Sorry for waiting.

I mailed you again with private mail~

[face_off]

Thanks for sending through the VDB file. I couldn't get that VDB file to render in Modo10 at all, so I suspect there is something inside the VDB triggering a problem. In Modo11 the motion blur of the particles is causing an issue for Octane, which I will fix in the next release. I also tried loading that VDB sequence into Octane Standalone, and save as an OCS file, then loading that OCS file as an OCS proxy in the OctaneRender for Modo plugin - however it looks like image sequences are not being loaded by Octane correctly - which I will ask Otoy to look at.

Paul

[yaseunghee]

Hi paul

I think you couldn't render my openvdb files Because that were extracted houdini.

Houdini uses openvdb 3.0 but Modo 10 uses V2.0.

But the modo 11 now supports openvdb 3.0.

So i could render with modo renderer but as you knew failed with octane.