Caches the current Time Slider frame only.
Specifies that your current Render settings determine the Cache time range.
Specifies that the current playback range in your Time Slider determines the Cache time range.
Specifies that the range of frames between (and including) the specified Start and End times determines the Cache time range.
Specifies how often samples are taken during file creation. By default, one sample of your object's transformations is taken every frame and saved to the Alembic file.
For example, a value of 2 caches the transformations of the current object at every other frame of the Cache Time Range.
Specifies at which frame to start the scene evaluation. Use this option to set the starting frame for time dependent translations that require a run up to the start frame.
Use the Cache Time Ranges options to specify multiple time ranges and sampling rates in the same Alembic file. For example in a cache file, you can specify a time range that samples every forth frame of an animation, and then specify another time range that samples every frame. You can use Cache Time Ranges to create a file that saves slow motion sequences at a lower sampling rate, while maintaining high sampling rates for full-action sequences.
Enter the first and last frame of the cache time range. You can also use the Start/End controls to set the time range.
Click Add Range+ to create multiple time ranges.
Indicates that a Pre-Roll range is set.
Displays the Frame Relative sample setting for the range.
Lets you add dynamic and custom attribute data to the exported Alembic file. To add attributes do one of the following:
Added attributes appear in the table under Attribute.
Specify a prefix to filter out the names of attributes you want written to the Alembic file. Type a value in the Attribute Prefix field and click Add. All of the attributes with the specified prefix in their attribute name are added to the Alembic file.
Outputs frame number information to the Script Editor or output window.
Turn on to exclude the source object's normal data from the Alembic cache file.
Turn on to exclude any non-renderable nodes or hierarchy, such as hidden objects, from the Alembic file.
Turn on to remove the namespaces associated with the exported objects before they are saved to Alembic file. For example, an object with the namespace taco:foo:bar appears as bar in the Alembic file.
Turn on to write UV data from polygon meshes and subdivision objects to the Alembic file. Only the current UV map is included.
Lets you write color per-vertex data from the source polygon meshes to the Alembic file. You can use this data to export motion vector data from the mesh for motion blur effects at render time.
Turn on Write Color Sets, and then add Motion Vector Color Set to the exported attribute list. To do this, in the Attributes section, type motionVectorColorSet beside Attribute, and then click Add.
Turn on to save per-face shading group assignments to the Alembic cache. Maya only saves the shading group names to the file. No material information is written to the cache.
When you load the Alembic file, Maya re-assigns shading to the faces if the shading groups exist in the scene. Maya does not create new materials or shading groups.
When on, geometry data at whole frames is sampled and written to the file. When off (default), geometry data is sampled at sub-frames and written to the file.
Turn on to store the top node in the node hierarchy as world space. By default, these nodes are stored as local space.
Turn on to store the visibility state of objects in the Alembic file. Otherwise, all objects are considered visible.
Turn on to filter , X, Y, and Z rotation data with an Euler filter. Euler filtering helps resolve irregularities in rotations especially if X, Y, and Z rotations exceed 360 degrees.
Turn on to export the geometry's edge and vertex crease information to the Alembic file.
Creates an Alembic cache file that conforms to the HDF5 data model. This option provides backwards compatibility with previous versions of Alembic.
Creates an Ogawa Alembic file. Files created with the Ogawa format are smaller in size and provide better performance than legacy Alembic files.
The recommended way to use callbacks with the Alembic export is to first define a global procedure. For example, in the Script Editor, define the following:
global proc perFrameCallback(int $frame) { print $frame; }
The full MEL callback is:
perFrameCallback(#FRAME#)
When each frame is evaluated, the string specified is evaluated as a MEL command. For example, print("#FRAME#").
When the translation has finished, the string specified is evaluated as a MEL command. For example, print("Done!").
When each frame is evaluated, the string specified is evaluated as a Python command. For example, print("#FRAME#").
When the translation has finished, the string specified is evaluated as a Python command. For example, print("Done!").