Combine Meshes (Batch)

Combine Meshes (Batch) is the sibling of the plain Combine Meshes node, and it exists because four fixed input slots aren't enough once you're doing real work. Where the regular node takes mesh_a through mesh_d, this one takes meshes - a single input that accepts a list of TRIMESH objects - and merges them all into one. The author's own tooltip says it plainly: "List of meshes to combine."

This is the node you reach for when the count isn't known in advance or is just too big to wire by hand. Scanned fragments, a batch of parts generated by a loop, dozens of objects split out of a scene - feed them in as a list, get one mesh out. Like its sibling, it's a merge, not a boolean union: geometry gets concatenated, overlapping parts stay overlapping. If you need parts carved into a single solid, that's the Boolean node, not this one.

What you feed it and what comes out

One input, meshes (TRIMESH, and it's list-typed - the wire will accept a list of meshes rather than a single one). Two outputs:

• combined_mesh - the merged TRIMESH, ready for a viewer, an exporter, or the next processing step.
• info - a STRING with the merge stats, which doubles as a sanity check that nothing silently dropped.

In practice you'll get the list from GeometryPack's own batch/mesh-list machinery or from a loader that can emit multiple objects, then land this node's output on a saver for one clean file instead of twenty.

Installing it

Identical install to the rest of GeometryPack:

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 ComfyUI after. ComfyUI Manager also works - search "GeometryPack" or install via Git URL with https://github.com/PozzettiAndrea/ComfyUI-GeometryPack.git. The pack's one-click installer is experimental (comfy-env, drags in the pixi package manager), so if that path gives you trouble, the manual route above is what the README calls "most reliable."

The thing to watch

Merging a big list is memory-friendly only up to a point - a few million combined triangles is fine, but the merge is all in one Python call and the resulting single mesh can get chunky. If a huge batch makes the node crawl, think about decimating the list before the merge instead of after. And the usual young-pack caveat applies: GeometryPack is a fast-moving WIP, so if the node errors on load, update it or re-run install.py before you go hunting for a config bug - it's probably the pack, not you.