X-Particles OpenVDB Motion Blur known issue?

[jayroth]

I have a scene file that uses the separated motion blur vertex files generated from X-Particles Open VDB mesher for motion blur. Without these files (and thus, no motion blur on that object) Octane zips through the scene rather quickly on my 2 hybrid RTX208ti cards. However, when I enable motion blur for that object, using those vertex map tags in the appropriate slots, renderings become an order of magnitude slower, frame to frame, with each frame getting slower than the last. Without motion blur, the frame renders at about 10 seconds. With motion blur, almost 20 minutes... ouch. And, frankly, undoable, as even farm time for this would be prohibitively expensive, given my frame counts (at least until Pixel Plow comes online.)

I am using the Path Tracer set to a lowly 128 samples and rendering at a 1280 x 720 resolution. I do have an Octane Specular material on this mesh (it's supposed to be water) with noise in the bump map slot. Octane version 2018.1.2.

Is this a known issue or have I run into something new here?

[jayroth]

More information. It appears to be motion blur in general, upon further investigation.

[jayroth]

Same results in 4.04 looks like that's just the way it is...

[RyanSilva]

If you stop the render every 30 frames or so, you can limp through it. Worst workaround ever.

This specific issue is pushing me away from Octane.

[aoktar]

Don't you mind to share a scene let me test it?

[jayroth]

I will PM you with a link. Thanks, Ahmet!