Implements #41. This is a breaking change due to how NoLooseEdge (plugin must declare loose edges) and ConstantFaceCount (host is allowed to omit face counts) work.
I've tested this quite a bit with MfxVTK, which has a branch supporting these features: https://github.com/tkarabela/MfxVTK/tree/feature-mesh-optimization-attributes To this end, the "Identity" and "Identity (forward attributes)" effects from libmfx_vtk_plugin_extra.ofx are quite useful, since they don't do any processing. "Idenity" round trips through VTK internal representation, while "Identity (forward attributes)" forwards points/vertices/faces directly at OFX level. Vertex colors/UVs are not handled in MfxVTK.
eliemichel
commented
3 years ago
Implements #41. This is a breaking change due to how NoLooseEdge (plugin must declare loose edges) and ConstantFaceCount (host is allowed to omit face counts) work.
I've tested this quite a bit with MfxVTK, which has a branch supporting these features: https://github.com/tkarabela/MfxVTK/tree/feature-mesh-optimization-attributes To this end, the "Identity" and "Identity (forward attributes)" effects from
libmfx_vtk_plugin_extra.ofxare quite useful, since they don't do any processing. "Idenity" round trips through VTK internal representation, while "Identity (forward attributes)" forwards points/vertices/faces directly at OFX level. Vertex colors/UVs are not handled in MfxVTK.I didn't try in with nightly due to #44.