Page tree


Artists rendering exported Alembic meshes from Houdini may have trouble rendering motion blur. This is usually because the topology of the mesh changes frequently and this makes it difficult for RenderMan to calculate motion blur. The solution is to export the mesh as an Alembic using a Houdini ROP node.



Now for Katana to make use of this information you need to add a Velocity Apply node. Be sure the path in the CEL statement is the Alembic polymesh in the hierarchy that you exported from Houdini.



With motion blur enabled in the PrmanGlobalStatements and a shutter interval that isn't 0 in the RenderSettings, you should automatically get motion blur. If you do not, be sure the VelocityApply path in the CEL statement is correct, motion blur is enabled, and that there is velocity data on the mesh. You can check the velocity data by selecting the mesh and looking at the Attributes > Geometry > Point > v  In this area you should see a table of values for the vertices. Katana automatically looks in geometry.point.V, geometry.point.v, and geometry.arbitrary.v for the correct data if you have not specified it.


No motion blur


With motion blur