SAM 3D Body: Get Mesh Info
A quick text readout of what's actually in your mesh
- mesh_data
- info
A small utility node with a slightly misleading class name - it's called SAM3DBodyGetVertices under the hood but shows up in the node picker as "SAM 3D Body: Get Mesh Info." Don't go looking for a raw vertex array output; what it actually gives you is a text summary of the mesh, not the geometry itself. If you just want to confirm a SAM3DBodyProcess (or Advanced, or Multiple) call actually produced something usable before you spend time exporting it, this is the cheap sanity check.
How it works
Feed it a mesh_data object and it reads the mesh's metadata - the kind of thing you'd otherwise have to open a 3D viewer to check - and hands it back as a plain string. Wire that string into a text-display node (or a console/log node if your workflow has one) and you get a readable summary without leaving ComfyUI.
The input and output that matter
There's exactly one of each. mesh_data (SAM3D_OUTPUT) is required - it's the mesh coming out of SAM3DBodyProcess, SAM3DBodyProcessAdvanced, SAM3DBodyAddMeshToSkeleton, or SAM3DBodyLoadMesh. The output, info (STRING), is the human-readable summary. It doesn't modify or pass through the mesh itself - this node is read-only, a tap on the wire rather than a step in the pipeline.
How to install it
It ships as part of the full pack, so there's nothing to install separately. Get the pack via ComfyUI Manager - search SAM3DBody, install, restart - or manually:
cd ComfyUI/custom_nodes
git clone https://github.com/PozzettiAndrea/ComfyUI-SAM3DBody.git
cd ComfyUI-SAM3DBody
pip install -r requirements.txt --upgrade
python install.py
No extra model download or heavy dependency is specific to this node - it's a lightweight introspection utility, not something that touches the SAM 3D Body checkpoint itself.
Common issues & troubleshooting
It's not in the node picker under the name you'd search. Search for "Get Mesh Info" if SAM3DBodyGetVertices doesn't turn anything up - the display name and class name diverge here, which trips people up more than you'd think for such a small node.
You wanted the actual vertex coordinates, not a summary string. This node doesn't expose raw geometry data as a usable output type - if you need to manipulate vertex positions programmatically, this isn't the node for that; it's a debug/inspection tool, not a data-extraction one.
Nothing downstream to wire it into. That's expected - info is a terminal string meant for display, not for feeding back into another SAM3DBody node. Drop a text preview node after it and move on; there's no further chaining here.
You're not sure it's worth adding to your graph at all. For a one-off run, probably skip it - debug_image out of the Process nodes already tells you whether detection worked. This one earns its keep more in a graph you're actively debugging, where you want to confirm the mesh object itself is populated before an export step fails downstream for a reason that isn't obvious from an image preview alone.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| mesh_data | SAM3D_OUTPUT | Mesh data from SAM3DBodyProcess node |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| info | STRING | — |