Use this setting to scale Alembic objects at object level without having to re-import them. Details see Scale
This setting can be used to adjust the weighting (if present) of imported Subdivision Surfaces. Make sure that you use values greater than 100%. This is necessary because there are Alembic files whose weighting can be greater than 100% (see Structure Manager). These will then be imported accordingly.
Enable this option if the dummy object is already located in the open Project. You will then not have to re-enter the path to the Alembic file.
As already mentioned here, the Alembic tags link to a separate Alembic file. This path will be set automatically when an Alembic file is opened. At the right you will find a selection button with which the link can be changed. At the right of the file selection button a green check mark or a red ,x’ shows whether or not Cinema 4D was able to locate the file.
This is a unique ID that displays a link to the corresponding object in the Alembic file (don’t be confused by any unknown naming conventions - Alembic uses its own special naming conventions). At the right, a green check mark or red ,x’ shows whether or not Cinema 4D was able to locate the object.
Enable this option if you want to play the animation saved in the Alembic file. If disabled, Frame will define which frame of animation should be displayed. Intermediate values such as 4.76 are also possible if Interpolation is enabled.
Frame can, for example, be controlled using XPresso to create a wide range of effects.
A temporal offset can be defined for the animation for fine-tuning.
Define here what should happen at the end of the animation:
Lets you define an animation speed. Extreme slow motion is also possible (whereby you should always enable Interpolation).
This resets any modified animations settings back to a defined state, i.e., as the Alembic animation was intended to be and saved.
This curve can be used to affect the animation’s timing. This is exactly what the Timeline’s Time Tracks do. For example, if the animation cycle should first run quicker then slower - or even in reverse. These effects can be defined here.
When working in Cinema 4D it can be cumbersome working with high-res objects. It is easier to work with simple dummy objects that can be automatically replaced with high-res objects for rendering. Enable this option if a given object should be switched with another object (defined by the next two options) for rendering. Note that the same object type must be used.
Here you can define the path to the Alembic file that contains the object to be rendered. If the Alembic file lies in the same directory as the Cinema 4D Project file, all you have to do is enter the object name.
This is where you define the precise object ID of the dummy object for the rendered object in the Path to Alembic File field. To do so, open the corresponding Alembic file and copy the hierarchical path from the corresponding Alembic object. This object must be a polygonal object.
Only this object will be used - all Child objects will be ignored.
This option defines if the position, scale and rotation information from the animation in the Alembic file should be transferred to the corresponding object. This option will only be made available if the object has a PSR animation. If this option is disabled, the current animation state will be frozen. It can, for example, be animated briefly in Cinema 4D. However, if this option is then enabled, the Alembic file will define the object’s animation.
This option defines if the geometry animation in the Alembic file (in Alembic files, an object’s vertices can be changed in number and position at any time, which in turn affects corresponding tags such as UVW, Normal, Selection, etc.) should be transferred to the corresponding object in Cinema 4D. If this option is disabled, the current animation state will be frozen. As soon as the option is enabled again, the Alembic file will define the animation.
Use this option to determine if the visibility states saved in the Alembic file should be assigned to the object.
The following options show the respective functions as tags (which cannot be modified, copied or deleted). These will be marked with an a in the Object Manager to show that they are controlled by an Alembic file.
If these are disabled, the corresponding tag will no longer be displayed. If multiple UVW tags exist, these will work in conjunction with the normal Texture tag (arrange the Texture tag to the right).
Otherwise tags can be used as usual (e.g., a Polygon Selection tag can be linked in a Texture tag to restrict the material to a selection).
Use this option to define if the Normal tag should be evaluated/displayed.
Use this option to determine if the UV tag should be evaluated/displayed.
Use this option to define if the Polygon Selection tag should be evaluated/displayed.
Use this option to define whether or not Vertex Color tags should be evaluated/displayed.
Use this option to define whether or not vertex and edge weighting for Subdivision Surfaces should be evaluated.
Enable this option if the attributes saved in other tags (see also Other Attributes) should constantly be evaluated.