OpenMfx is a plug-in API for procedural 3D mesh effects.
cross-software – Write a mesh processing effect once, run it in every digital content creation tool that supports OpenMfx.
low overhead – The API intends to limit as much as possible the copy of data in the communication between a plugin and the host software.
non-destructive interchange – Export a 3D scene without burning in non-destructive effects. If these effects are backed by OpenMfx plugins, they can be seamlessly imported into another piece of software and result in the very same geometry.
user-friendly – Writing your own mesh processing effect is made as straightforward as possible thanks to a C++ SDK that wraps around the portable raw C API, providing a nicer interface without scarifying performance.
- Quick Start
- Programming Guide
- SDK Reference
- API Reference
- Implementations and Related Work
- Requests for Comments
- RFC001 - Design Principles
- RFC002 - Edge Representation
- RFC003 - Constant Face Size
- RFC004 - Renaming Vertex into Corner
- RFC005 - Deform-only effects
- RFC006 - Null stride for constant face size
- RFC007 - Requesting attributes
- RFC008 - Enumerating attributes
- RFC009 - Dynamic linking hell
- RFC010 - Mesh representation of common hosts
- RFC011 - Non-mesh inputs/outputs
- RFC012 - Arbitrary attributes on Point/Corner/Face
- RFC013 - Renaming OpenMeshEffect into OpenMfx
- RFC014 - Buffer Protocol