-
Notifications
You must be signed in to change notification settings - Fork 196
Alembic Export Support
Alembic export is not officially supported in the FLIP Fluids addon. The reason for this is that the Blender Alembic exporter can be unstable with the large meshes produced by the fluid simulator. The resulting Alembic cache works well for importing back into Blender, but we cannot guarantee that this will work for importing into other software that use different standards for how the Alembic cache is structured. However, many users have had success in exporting a FLIP Fluids simulation to Alembic for use in other software.
A common problem with exporting FLIP Fluids whitewater meshes is that some third-party softwares cannot import this data properly. The Blender Alembic exported does not support exporting particles or instances so whitewater simulation meshes are structured as vertex-only meshes where each vertex represents to position of a whitewater particle. Some softwares do not recognize vertex-only meshes as valid geometry.
When exporting to Alembic, the Blender Alembic exporter checks if there are any modifiers on the object to determine if the object is animated.
To export a fluid simulation as an Alembic cache, you will need to use a workaround of adding a modifier to the fluid_surface object (and whitewater objects if applicable) so that they are recognized as an animated mesh. For example, a smooth modifier with 0 repeats can be used. The animated meshes can then be exported within Blender (Blender > File > Export > Alembic (.abc)).
Alembic export of a FLIP Fluids simulation is not possible due to a severe bug in Blender 2.80. The bug has been fixed in Blender 2.81 or higher.
Important Note: To prevent crashes during Alembic export in Blender 2.81, the Blender interface must be locked (Blender > Render > Lock Interface).