Wrong motion blur with deformers

[kostache]

Hello Paul,

There is an example of the simple scene I made - bend deformer's motion blur in MODO an Octane (I've tested it in Octane 2019 and 2020). Seems like Octane is taking wrong action center for MB in the middle of object.
MODO:

Octane:

Scene is embeded

[face_off]

Hi. The Octane plugin is obtaining motion vectors for motion blur via the Modo Render Cache. There is an outstanding bug report with Foundry regarding this where it appears the incorrect motion vectors are being provided by the Render Cache. I have provided your scene to Foundry as further evidence of this problem. The only way around this is to export the animation to an ORBX file and render in Octane Standalone - however I got an out of memory error doing this (which I have previously reported to OTOY, but not have a response on). I am sorry I cannot give you a better resolution.

Paul

[Carnera]

Hi guys

just trying to understand the motion blur workflow.

If I want to have motion blur rendered (inc. vector motion blur pass) in octane

- turn on motion blur in modo camera
- octane settings ...turn on use modo render cache
- octane animation ... turn on camera motion blur and object motion blur
- is it important to have "Reload Mesh Each Frame" turned on?

In any case (whether objects that are transforming/rotating/scaling OR deforming) octane has to import the entire scene for rendering. Is that a normal behavior ?

In my case the scene I am working on is rather heavy (3000 objects...with dynamic caches). When I start the octane render viewport, octane immediately starts importing the scene (which can take 10 min in my case).
once the scene is imported and I start "render animation", octane starts importing the scene again. Which is strange ...
So I decided...
Next time I wanted to start a render, I hit the octane render viewport ...it started importing the scene...so I decided to cancel the importing, knowing that it will import the scene again once I hit "render animation".
Is there are reason why octane needs to import the scene again before starting the render?

I saw similar issues with deforming objects , the modo motion blur looks different to the octane motion blur.
I am using modo 14 and it looks like Foundry has not updated the render cache vector motion bug.

Is octane preferring Mdd or Alembic for geo caches? We are using ACS 2 (character rig) is that something that octane would have a problem with? Meaning is it better to cache the geo (mdd or alembic) or can we use the ACS deformed character?

Thanks a lot

Andras Kavalecz
-------------------------------------------------
http://www.checkpointVFX.com

[face_off]

Hi Andras - the plugin is evolving with each release, so can you please tell me what version you are running please and I will try to answer your question.

Paul

[Carnera]

Hi Paul

using Modo 14.0v1 and Octane plugin 2019.1.4.154
On windows 10

Thank you

Andras Kavalecz
-------------------------------------------------
http://www.checkpointVFX.com

[face_off]

May I suggest trying with the latest version of the plugin, as it contains some changes and fixes for motion blur. Also, have a look a this thread - viewtopic.php?f=34&t=73940.

Paul

[Carnera]

Hi Paul

I thought 2019.1.4.154 is the latest Modo plugin version?
That's the one I am using.
Is there a newer version I am not aware of ?

I looked at the other link but could not find any valuable info. I have deforming objects and not objects that are being transformed.

Do you have any ETA when the foundry is going to fix the vectors for the motion blur?

Thank you

Andras
http://www.checkpointvfx.com

[face_off]

Hi Andras - please see viewtopic.php?f=34&t=71990 for the latest Octane 2019.1 release.

Paul