geometry-dual-contouring

Dual contouring preserves sharp terrain edges by placing one vertex per cell using Hermite data and QEF optimization, avoiding the smoothing typical of marching cubes. It requires edge intersections and normals to maintain accurate cliff features.

To generate crack-free terrain meshes, accumulate Hermite data per octree cell, solve QEFs with mass-point bias for stability, and assemble the faces. An optional clamping mechanism keeps vertices inside their cells for adaptive subdivision.

Yes, dual contouring requires Hermite data, which includes edge intersections and normals, to accurately place vertices and preserve sharp coastline features. You must load a scalar field and normals to accumulate this data per cell.

QEF vertex placement becomes unstable without a mass-point bias for stability. Applying this bias during the QEF solve anchors the vertex placement and prevents erratic floating geometry in your terrain mesh.

Yes, dual contouring supports Rust-friendly implementation considerations for terrain mesh generation. You can load scalar fields, process Hermite data, and solve QEFs to output crack-free quad meshes within a Rust environment.