The following is the latest information on Animation and Motion Blur, which has not yet been added to the on-line manual.
Fast Moving Objects
In general, if there are object moving quickly in the scene, you will need to increase the Kernel->Animation->Sample Per Frame so the Octane gets more transforms per frame. For fast rotating/spinning objects, the object will get smaller the higher the motion blur percent unless there are sufficient Samples Per Frame.
In cases where a Mesh Item is rotating rapidly, if the Mesh Item "center" of the geometry is not at in the middle of the geometry, the motion blur may not be calculated correctly. In this case, either increase the Kernel->Animation->Samples Per Frame to get the correct motion blur, or set the "center" and "pivot" point of the geometry to the geometry bounding box center.
Motion Blur on the First Frame
The plugin will not load object transforms into the Octane timeline prior to the first frame of the Current Modo Range. So if you need motion blur on the first frame, you need to either add one (or more) frames to the start of the animation, or set Kernel->Animation->Shutter Alignment = After.
Motion Blur on Replicators
To render motion blur on replicators, make sure Camera and Object motion blur are enabled on the Kernel->Animation tab. Then enable Object Motion Blur on the Replicator. IMPORTANT: motion blur on Replicators only works if there are the same number of Point Source transforms each frame. So if the Replicator has a Point Source of a Particle Generator or similar, then there will most probably be a different number of transforms for each frame in the animation, and if Object Motion Blur is enabled on the Replicator, the Replicator will NOT appear in the Octane Viewport. In this situation, UNTICK Object Motion Blur on the Replicator, and TICK Kernel->Animation->Refresh Replicators When Scrubbing The Timeline.
emReader meshes can be rendered with the plugin, however make sure you are on at least plugin version 2020.1.3.163, which contains the Kernel->Animation->Refresh Non-Live Meshes When Scrubbing The Timeline property, which you should turn ON to ensure the emReader mesh is reloaded each animation frame. Because the emReader mesh vertices are not consistent between frames, motion blur will not render in Octane - and even using octane.saveAnimation will not result in any motion blur being rendered on emReader meshes. Turning ON the Kernel->Settings->Use Modo Render Cache does not assist in rendering emReader animations, as the Render Cache appears to only load the first frames emReader mesh, and not subsequent frames.
Last edited by face_off
on Wed Sep 16, 2020 1:22 am, edited 4 times in total.