Remesh Blender Blocks (backend)

Every once in a while you want a mesh to look like it was carved out of building blocks. That's exactly what Blender's Blocks remesh modifier does, and this backend runs it inside GeometryPack. It's the playful sibling of the voxel and sharp backends: same octree machinery, but the surface comes out blocky - every face a flat slab on the grid, like a low-poly Minecraft sculpture of your object.

It's the blender_blocks backend you pick from the Remesh Blender dispatcher dropdown (or the main Remesh node's blender_blocks option). Dev-only in the schema, as all the backend nodes are - you'll select it, not add it.

How it works

The Blocks modifier runs the same octree rebuild as the Smooth and Sharp modifiers, but stops before the smoothing step and instead flattens the surface onto the grid. The result is a watertight mesh whose faces are grid-aligned slabs. It's still a real, manifold, printable surface - the chunky look is aesthetic, not broken. The two controls are shared with the other octree backends: how fine the grid is (octree_depth) and how much the output shrinks relative to the input's bounding box (scale).

Inputs and outputs

• trimesh (TRIMESH) - the mesh to remesh.
• octree_depth (default 6) - grid resolution. Higher = finer blocks, more of them, and a look that gets closer to the original shape. Lower = chunkier blocks, more aggressively "blocky."
• scale (default 0.9) - output size as a ratio of the input bounding box.

Outputs: remeshed_mesh (TRIMESH) and info (STRING) with the before/after counts.

Installing

Blender-backed nodes carry the pack's heaviest install. ComfyUI Manager → GeometryPack, or:

cd ComfyUI/custom_nodes
git clone https://github.com/PozzettiAndrea/ComfyUI-GeometryPack.git
cd ComfyUI-GeometryPack
pip install -r requirements.txt --upgrade
python install.py

Restart after. The install.py step is the comfy-env/pixi installer that fetches a full Blender build into an isolated environment - the big download, and the step that most commonly fails. First run of any Blender backend initializes that env and takes a while.

When to reach for it

This is a stylistic node first and a technical one second. Use it for voxel-art game assets, for a low-poly Minecraft-style prop, for stylized renders. There are also workflow-adjacent uses: because the output is watertight and grid-aligned, it's a decent quick way to get a clean closed surface from a messy scan when you also want the chunky aesthetic - two birds, one modifier. If you want a clean uniform surface without the block look, use blender_voxel or blender_smooth instead; the blocks look is the entire differentiator.

Troubleshooting

• Too chunky - raise octree_depth; each step up roughly doubles resolution.
• Not chunky enough - lower octree_depth until the slabs read clearly.
• Blender env errors on install/first run - re-run python install.py; Blender env failures are the pack's most-reported install issue. Check the repo Discussions if it won't resolve.
• Stale-workflow validation errors are the pack-wide gotcha - if the dispatcher node throws, delete and re-add it, then re-pick blender_blocks.

One honest note: this is a niche backend even within a niche pack. It's great at exactly one thing and you'll know if that thing is yours.