The plug-in is available for
- CINEMA 4D R20.057 or above
- CINEMA 4D R21.022 or above
- CINEMA 4D R22.016 or above
- CINEMA 4D R23.008 or above
There are two methods to check which version of the plugin is currently in use. If you open the IPR Window the version number is displayed in the title. You can also open the About dialog from the Plugins > C4DtoA > Help menu and read the version number from the dialog.
Below is a list of the current limitations and unsupported features in C4DtoA:
- Most of the native C4D shaders are not supported.
- While the IPR is running, material previews are not rendered because only one render session can be active in Arnold. Previews will be updated when the IPR is stopped. The last rendered preview is displayed with a small orange frame showing that the preview is delayed. The IPR is stopped when a render to Picture Viewer is started because of the same reason.
- The IPR requires the viewport (editor) window to be open and visible otherwise the IPR does not update on changes.
- C4D's built-in IRR (Interactive Render Region) feature is not supported. Use the Arnold IPR window instead which is designed to give real-time feedback on your changes.
- Viewport display limitations of Arnold lights:
Arnold specific settings (like color texture, radius, etc.) are not supported.
Skydome light is not supported.
- Viewport display limitations of Arnold Sky:
- Physical sky is not supported.
- Lighting is not supported.
- If a shader network material is linked to the sky color then only a root image shader is supported. UV settings of the image shader are not supported.
- Most of the shaders and their parameters are not supported in the viewport.
- The isometric view in the default Camera is not currently supported.
- The specular flag is not supported by light linking (exclude/include objects).
- The Fur object is not supported because it's not accessible via the C4D SDK.
- Environment objects (e.g. Sky, Physical Sky, etc.) are not supported.
- Motion blur with varying point count is not supported.
- Projection with nested objects is not supported (e.g. using a flat projection on a Null object or a Cloner).
- Some of the Texture tag features are not currently supported. These include Mix Textures, Seamless, Use UVW for Bump.
- Arnold drivers do not work properly in a single frame Team Render because they are executed on the client machines, writing out only a part of the image.
- Changing camera in a Stage object does not trigger an IPR update immediately. You have to move the mouse over the viewport or change selection to trigger a proper update.
- Reset all parameters of a shader resets the title to "Arnold Shader" and the title color to grey.
- Built-in spheres of a particle render have no UV coordinates. Use a Sphere child object instead.
- The Arnold IPR Window does not support TeamRender. This is not possible natively in C4D as Team Render is not designed for interactive rendering.
- When a custom color space is selected in the IPR (e.g. OCIO) Render to the Picture Viewer, Team Render to the Picture Viewer and therefore the native Save won't match. The image in the Picture Viewer is always displayed in C4D's built-in sRGB color space.
Procedurals have the following issues with IPR, related to the Arnold core:
- No update when changing the path (e.g. moving a timeline by a .ass sequence).
- No update when creating a new procedural.
- Removing a shader from the procedural node renders with an invalid shader.
Procedurals do not render correctly with object mask. The object mask overrides the shaders inside the procedural.
This is a self-shadowing error that can result from low tessellation or when objects do not have thickness. It usually occurs in concave areas or when the light is behind the polygon mesh. In these situations, it can introduce light leaking. There are some workarounds:
This is a self-shadowing error that can result from low tessellation or when objects do not have thickness. It usually occurs in concave areas or when the light is behind the polygon mesh. In these situations, it can introduce light leaking.
There are some workarounds: