By default, MtoA will not motion blur an alembic cache of a mesh that has a changing topology. However, MtoA can use the velocity attribute as a source to derive motion blur data from a mesh that has a changing topology using a motion vector.
Use this velocity attribute as the source to derive the motion blur data. You must use the name that the velocity was exported as a per point vector. MtoA will use the vertex velocity attribute to calculate the motion blur. The point vector attribute coming from Houdini, for example, may be called 'v'. The default name is 'velocityPV'.
Choose between 'Per Frame' or 'Per Second'.
A float scale field (with a default value of 1) to do time scaling effects.
This short tutorial will go through the process of exporting an Alembic file with motion data stored in a vertex color channel from Houdini and rendering it in Maya with MtoA. We will use the velocityPV attribute to convert per vertex attributes with which MtoA can use to apply motion blur to the Alembic geometry. This geometry has topology that changes from frame to frame.
You will need to ensure that you have the SOuP plugin for Maya loaded for this tutorial to work.
We will use an alembic file from Houdini. It has point velocity in the v channel (point vector attribute 'v' coming from the geometry you are exporting in Houdini to store the velocity, which should be a vector of 3 floats) which calculates motion blur on a mesh where the point numbers are in motion.
Alembic file opened in Maya
Ensure that the Color Set is set to RGB and not RGBA, otherwise you will get an incorrect result.
Go to the soup shelf. Click on the first nodes icon and select arrayToPointColor.
Alembic node connected to arrayToPointColor and fluid surface geometry
When velocity blur is enabled, the translator will only exports two keys.
Color information can also be exported to the Alembic file from Houdini and then extracted and rendered with MtoA in Maya.