SAM 3D Body: Load Skeleton

The other half of SAM3DBodySaveSkeleton. Once you've written a pose out to disk, SAM3DBodyLoadSkeleton reads it back in as a usable SKELETON object - no re-running detection, no image needed at all. It's the smallest, simplest node in the pack, and it earns its place once you're building anything resembling a pose library rather than a one-off single-photo pipeline.

How it works

Give it a filepath and it reads and parses the saved skeleton data, handing you back the same SKELETON type that comes out of SAM3DBodyProcess. From there, the typical next step is SAM3DBodyAddMeshToSkeleton - feed the loaded skeleton plus a SAM3D_MODEL in, and get a mesh back for that pose without a source photo in sight.

The input and output that matter

Just one of each. filepath (STRING, default empty) - you type or paste in the path to a previously saved skeleton file, typically one written by SAM3DBodySaveSkeleton. There's no dropdown here the way the mesh-loading nodes have one, so you'll need the exact path rather than picking from a browsed list.

The output, skeleton (SKELETON), plugs directly into SAM3DBodyAddMeshToSkeleton - that's the only other node in the pack that consumes a skeleton as an input on its own (SAM3DBodyVisualize and the export nodes all want mesh_data, not a bare skeleton).

How to install it

Bundled with the pack. Via ComfyUI Manager: search SAM3DBody, install, restart. Manual install:

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

Nothing extra to fetch for this node - it reads a file you already produced, no model or gated checkpoint involved.

Common issues & troubleshooting

Path doesn't resolve, node errors on run. Since filepath is a plain text field rather than a dropdown, typos are the most likely cause - double-check the exact path SAM3DBodySaveSkeleton reported back in its filepath output rather than retyping it from memory.

Loaded skeleton by itself doesn't render or export anything. That's expected - a skeleton alone isn't visualizable the way a mesh is. If you want to see or export something from it, route it through SAM3DBodyAddMeshToSkeleton first to get a mesh_data object, then use SAM3DBodyVisualize or either export node from there.

Not sure this node is worth the extra step versus just re-running the photo. If you still have the source image handy and don't mind paying for inference again, re-running SAM3DBodyProcess is simpler for a single use. This node earns its place specifically when you've deliberately built a saved-pose workflow - reusing poses across multiple body shapes, or keeping a small pose library instead of a folder of source photos.