Motion blur with Displacement still broken?

[mgtaylor]

Hi,
When I try to use transform/vertex motion blur on an object with a octane material that has displacement, the Live Viewer simply get stuck at "updating". I've been looking up on forums and it seems admins replied to people with the same issue before and noted that motion blur does not work with displacement, but that was 2014. Is this really still the case?

[aoktar]

It's not broken but sensitive to mesh topology/uv and amount of displacement. Also using geometry motion blur is heavy effect on renderer.
"Updating" message shows that Octane is in progress.
Check Console window. There may be some cuda errors. Other than this you may be forced too much the renderer. Try lower displacement amount.

[garryjoshi]

@aoktar have you got any solution? I am encountering the same error it's simply stuck at updating and no output. I even tried lowering displacement amount but still its the same.

[mgtaylor]

@aoktar have you got any solution? I am encountering the same error it's simply stuck at updating and no output. I even tried lowering displacement amount but still its the same.

Never worked for me. I had to use the displacement maps in Bump instead to finish my renders.

[yolo1133]

Has anyone got the solution yet? My phone is stuck at updating. Tried lowering the displacement as well.

[chrisbrearley]

Just another reason why major production house won't use Octane. We rely massively on real smart motion blur as Octane just refuses to render motion blur with displacement. This is an absolute must for anyone doing animations.

[ceen]

Yes, this is a major issue with Octane in production. Please fix those things related with Motion Blur. It makes Octane basically impossible as a character animation tool in production since it also kills the rendering with joints in combination with displacement.

[chrisbrearley]

I was hoping for this to have been sorted with v4 but it hasn't. I guess we'll be sticking with RSMB for the time being.

[ceen]

Can confirm. Still not working in V4

[frankmci]

I was hoping for this to have been sorted with v4 but it hasn't. I guess we'll be sticking with RSMB for the time being.

Depending on the amount of displacement you are using, one way to get better MB via RSMB/Octane is to use the non-displaced geometry to generate the motion vectors, then use that pass with RSMB on the displaced/rendered pass. Obviously this works a lot better if the displacement is primarily for details and not gross geometry.

But really, RSMB does such a good job, it's rarely worth the extra effort to generate a separate vector pass. I love RSMB; it's probably saved me literally months of render time over the years!