lukas-toenne / voronoi_tools Goto Github PK

Data layers are somewhat incompatible between the two modes. Having two separate operators would clarify these settings and make code better organized.

• Create a new object when in object mode
• Add mesh on top of existing data when in edit mode

Write mesh data to alembic files instead of creating a mesh object directly. This allows longer mesh sequences without requiring a new data block for each mesh. Alembic file can then be re-imported through the standard modifier for playback.

Should be possible by using the existing alembic export operator:

1. Create a depsgraph update or frame change handler that runs after scene changes, but before the abc operator.
   https://docs.blender.org/api/2.82/bpy.ops.wm.html#bpy.ops.wm.alembic_export
2. In the handler: Create mesh data in the exported object with the triangulator, based on point data for the current frame.
3. Run standard alembic operator over a frame range.

Currently the triangulator duplicates points for creating tileable patterns, which creates 9x the amount of points. Tileability can be ensured more efficiently by wrapping the point set when reaching the boundary:

1. Sweep-hull would create a sorted list including repeated points, mapping each to the original point index and storing the distance. Convex hull is only extended to positive-repetition points and then stops. Vertices are created on-the-fly when extending the convex hull to avoid adding unused vertices.
2. Edge-flipping edges also takes wrapped geometry into account. Boundary edges can now be flipped, possibly adding a new vertex in positive repetition. Affected edges also apply to the original data by wrapping.
3. Voronoi cells take wrapped triangles into account for creating loops on boundary verts.