Octane Deformation Motion Blur in Cinema 4D: Object Tags, Alembic and Fixes
Most broken Octane motion blur comes from the Octane Object tag setup, not from the camera. The main points from OTOY's documentation:
- Tag the whole hierarchy: Every animated object and its parents need an Octane Object tag; an untagged object is left out of the motion calculation.
- Pick the right motion data: Transform for rigid motion, Transform/Vertex for deformation, Vertex Speed for caches with changing point counts.
- Displacement limit: Deformed objects with texture displacement do not blur properly; OTOY recommends vertex displacement.
- Check in the final render: OTOY forum threads show Live Viewer and Picture Viewer can differ on motion steps; test a few frames in the real output.
- Heavy caches: Vertex motion data adds memory per frame; iRender RTX 5090 servers with 32 GB per GPU let you test Alembic blur on the final GPU before rendering the sequence.
Deformation motion blur is one of the most reported Octane problems: Alembic caches that render sharp, rigs that blur in the Live Viewer but not in the final frames, or strange streaks on displaced objects. Almost every case comes down to the Octane Object tag. This guide follows OTOY’s documentation and staff answers on the OTOY forum.
Checked against the Cinema 4D and OctaneRender documentation, November 2026.
1. How does Octane calculate object motion blur?
Octane has camera motion blur and object motion blur. Object blur needs an Octane Object tag on every object or parent in the hierarchy (OTOY: Motion Blur).
With Transform, a moving ball streaks but its shape stays rigid. With Transform/Vertex, a waving flag or a character also blurs its changing shape. An object without a tag in its hierarchy is left out of the calculation, and the result looks wrong; OTOY describes this as how the system works, not a bug.
Motion data options in the Octane Object tag
From OTOY's Motion Blur page for Octane in Cinema 4D.
| Option | What is blurred | Use for |
|---|---|---|
| Disabled | No object motion data is exported | Static objects; note camera motion still blurs them |
| Transform | Position, scale and rotation | Rigid objects, MoGraph clones, vehicles |
| Transform / Vertex | Transforms plus vertex movement | Character rigs, deformers, cloth, Alembic point caches |
| Vertex Speed | Motion taken from a per-vertex velocity attribute | Caches whose point count changes, such as fluids or meshed particles |
Sources: OTOY: Motion Blur (C4D), OTOY: Motion Blur tab.
2. How to set up deformation motion blur for Alembic (step by step)
To get deformation motion blur on an Alembic cache in Octane, add an Octane Object tag to the Alembic object and every parent, set Motion data to Transform/Vertex (or Vertex Speed when the point count changes and the cache has velocities), enable motion blur in the Octane Camera tag, and test frames in the Picture Viewer.
Settings checklist (copy or follow line by line):
Step 1: Import the Alembic correctly
Import the .abc and keep it as an Alembic object, or make it editable so an Alembic Morph tag preserves the cached deformation (Maxon: Alembic Morph tag).
Step 2: Tag the hierarchy
Add an Octane Object tag to the Alembic object and its parents. A tag on a null alone is not enough for the mesh.
Step 3: Set motion data
Use Transform/Vertex if the point count is constant, Vertex Speed if the cache has velocities and a changing point count.
Step 4: Set the shutter
Enable motion blur in the Octane Camera tag and set shutter time or angle for the look you need.
Step 5: Test in the real output
Render two or three frames to the Picture Viewer or to files. OTOY forum threads show results can differ from the Live Viewer when motion steps change.
3. Why does Octane motion blur break, and how do you fix it?
Octane motion blur usually breaks for four reasons: a parent in the hierarchy has no Octane Object tag, a deforming object uses texture displacement (use vertex displacement instead), fast curved motion needs more motion steps, or a moving camera blurs objects whose blur is disabled. OTOY’s documentation and forum staff describe each case.
- Texture displacement on a deformed object: OTOY staff said this combination does not render motion blur properly; use vertex displacement (OTOY forum).
- Missing tag on a parent: tag every level of the hierarchy, as OTOY’s docs require.
- Fast curved or rotating motion: more motion steps describe the curve better, at the cost of memory; OTOY’s other host docs note vertex blur uses two steps.
- Disabled tag still blurs: a moving camera blurs every object, even ones set to Disabled.
Sources: OTOY: Motion Blur, steps and vertex blur.
Octane motion blur problems and fixes
The same four causes explain most broken motion blur reports. Use the table as a checklist before rendering the sequence.
Common Octane motion blur problems
Based on OTOY's Motion Blur documentation and OTOY forum answers cited above.
| Symptom | Likely cause | Fix |
|---|---|---|
| Alembic renders sharp | A parent has no Octane Object tag, or Motion data is Transform | Tag every level of the hierarchy and set Transform/Vertex |
| Blur breaks on a deformed, displaced object | Texture displacement on a deforming object | Use vertex displacement instead |
| Fast rotation blurs in a straight line | Too few motion steps for curved motion | Raise motion steps; it costs memory |
| Blur in Live Viewer but not in the final frame | Live Viewer and Picture Viewer can differ when motion steps change | Test frames in the Picture Viewer or to file |
| Objects with blur disabled are still blurred | The camera is moving | Expected: camera motion blurs everything |
Checklist: before you render the blurred sequence
Tick each item as you check it in the scene.
4. Where should you render heavy deformation shots: SaaS or IaaS farm?
A SaaS render farm suits a scene whose blur has already been checked frame by frame. An IaaS render farm such as iRender gives you the full Cinema 4D session with the Alembic files, so you can verify blur in the final output on the same GPUs before rendering the whole sequence.
These videos show Cinema 4D and Octane jobs on iRender multi-GPU servers.
On iRender you rent a whole server with 2x, 4x or 8x RTX 5090 or RTX 4090 GPUs, with Cinema 4D and OctaneRender pre-installed. You sign in with your own OTOY account; for multi-GPU servers OTOY’s Studio+ plan has no GPU limit. Related: motion blur in Redshift. Plans and real render times are on the Octane render farm page.
5. Octane motion blur FAQ
1. Why is my Alembic object not motion blurred in Octane?
Check that the Alembic object has an Octane Object tag with motion data set to Transform/Vertex, that its parents are tagged too, and that motion blur is enabled in the Octane Camera tag. Test a frame in the Picture Viewer, not only the Live Viewer.
2. What is the difference between Transform and Transform/Vertex in Octane?
Transform only blurs position, rotation and scale. Transform/Vertex also blurs vertex movement, which is needed for deformers, character rigs, cloth and point-cache animation.
3. When should I use Vertex Speed?
Use it when the cache provides a per-vertex velocity attribute, typically for fluids or meshed particles whose point count changes every frame, where vertex positions cannot be matched between frames.
4. Why does motion blur break on an object with a deformer and displacement?
OTOY staff explained that a deformed object with texture displacement does not render motion blur properly. Switching to vertex displacement fixes it.
5. How do I control motion blur length in Octane?
In the Octane Camera tag, set the Shutter Type and shutter time; for example a 360° shutter (100%) gives longer streaks, 180° is the classic film look. Time Shift moves where the blur is calculated.
6. Does disabling motion blur on an object remove its blur completely?
No. Disabling it treats the object as non-moving, but a moving camera still produces blur on it because of the relative motion.
7. Why does Octane motion blur look different in the Live Viewer and the Picture Viewer?
According to OTOY forum answers, results can differ between the two when motion steps change. Render two or three frames in the Picture Viewer or to file before rendering the whole sequence.




