GN SDF Remesh

examples/gn-sdf-remesh/

A Geometry Nodes SDF remesh (MeshToSDFGrid → GridToMesh at the SDF zero-level), with a Set Material node carrying the material through the remesh.

Rendered headless by the example itself. Select it to enlarge.

witnesses An SDF grid is meshed with Grid to Mesh, not Volume to Mesh; GN geometry needs Set Material or it renders untextured.

tags geometry-nodes materials

runs on 4.5 LTS · 5.1 · 5.2 LTS

blender --background --python examples/gn-sdf-remesh/gn_sdf_remesh.py --

falsify it Breaks the contract on purpose and must exit 3

blender --background --python examples/gn-sdf-remesh/gn_sdf_remesh.py -- --no-sdf

A runnable example that remeshes an input mesh through an OpenVDB SDF grid using the build_remesh_via_sdf pattern from the geometry-nodes-python skill: GeometryNodeMeshToSDFGrid → GeometryNodeGridToMesh at the SDF zero-level, attached as a NODES modifier and evaluated via the depsgraph.

Which fix it witnesses: an SDF grid is meshed with Grid to Mesh, not Volume to Mesh (the Mesh to SDF Grid output is a grid socket; Volume to Mesh takes a volume-geometry socket, so wiring the grid there is an invalid link that yields no geometry). Grid to Mesh has the matching grid input.

Materials gotcha: geometry generated by Geometry Nodes carries no material, so the input mesh's material is dropped on remesh (the result renders with the default white). Re-apply it inside the tree with a Set Material node (GeometryNodeSetMaterial) on the remeshed output — this example does that and asserts the material survives onto the evaluated mesh.

Render#

The check measures a torus; the still proves the same build_remesh_via_sdf tree on a subject where remeshing is visible. A vase is kitbashed from overlapping primitives (foot, belly, neck, lip, two handles), each in its own clay tone under a thin cage of its own edges, so the interior faces and hard intersection seams read. Beside it the identical kit runs through the tree (finer 0.018 voxels, cobalt glaze carried in by Set Material) and comes out one fused, watertight shell with the handles filleted into the belly. The torus leaves the stage before the render; the render path gates framing through examples/gallery_framing.py (exit 10).

Run#

# Cheap correctness check only (no render) — the CI smoke check:
blender --background --python gn_sdf_remesh.py --

# Falsifier: no SDF modifier. Must exit non-zero (evaluated == base).
blender --background --python gn_sdf_remesh.py -- --no-sdf

# Falsifier: no Set Material node in the tree. Must exit non-zero (exit 6).
blender --background --python gn_sdf_remesh.py -- --no-set-material

# Also render the remeshed result (EEVEE on a GPU host; --engine cycles on GPU-less hosts):
blender --background --python gn_sdf_remesh.py -- --output remesh.png
blender --background --python gn_sdf_remesh.py -- --output remesh.png --engine cycles

Exit codes#

Per-script sequential checks. 9 is a valid check code; there is no rule against it.

CodeMeaning
0Success
1Uncaught exception (FATAL wrapper)
2argparse / usage
3SDF remesh produced no/unchanged geometry (--no-sdf lands here)
4--output produced no file
5Wrong-era EEVEE engine id was accepted
6Input material dropped by remesh (--no-set-material lands here)
10Framing gate violation on the --output path (gallery_framing)

The blender-smoke workflow runs the check on Blender 5.2 LTS and 4.5 LTS (5.1 on the weekly cron, the needs-5.1 PR label, or manual dispatch). Smoke does not pass --output. Its catalog falsifiers are --no-sdf (expects exit 3) and --no-set-material (expects exit 6).

Source

examples/gn-sdf-remesh/gn_sdf_remesh.py View the script on GitHub →
Two amphora vases on walnut bats: left, a kit of overlapping clay primitives under their own ring-topology cage; right, the same kit SDF-remeshed into one fused cobalt-glazed shell.