Hunyuan 3D 2.1 Use MultiViews From MetaData
Resume a texturing job from disk — the node that remembers the whole camera rig for you
- trimesh
- pipeline
- albedo
- mr
- camera_config
Hy3D21UseMultiViews is for reloading views you have in memory. Hy3D21UseMultiViewsFromMetaData is for reloading views that have been sitting on disk since Tuesday. Point it at a meta_data.json written by the WithMetaData pipeline, give it the mesh, and it reconstructs the camera config, finds the saved albedo/MR PNGs, and rebuilds the paint pipeline - without you remembering a single azimuth or weight. It's the "load your save game" button for texturing.
The inputs
- trimesh - the mesh you're texturing (same one the views were generated for).
- metadata_file - path to the
meta_data.jsonwritten byHy3DBakeMultiViewsWithMetaData(found inoutput/3D/<name>/). This is the whole trick: everything else is derived from it. - view_size (512) / texture_size (1024) - pipeline configuration, same as the generator's.
How it works
It reads the JSON, rebuilds the MetaData object, and pulls the camera config out of it (azimuths, elevations, weights, ortho scale) to construct a matching Hunyuan3DPaintPipeline. Then it loads the view images from the folder next to the metadata file. The smart part: if the metadata has albedos_upscaled / mrs_upscaled lists (written when a bake detected upscaled views), it loads those instead of the originals - you always get the best views that were saved. Outputs: pipeline, albedo, mr, and the recovered camera_config, ready for a re-bake.
When you'd use it
Mostly two situations. You upscaled views and re-baked (Hy3DBakeMultiViewsWithMetaData), then later want to tweak the bake - the inpaint parameters or texture size - without regenerating views. Or you're restarting a texturing job days later; the views and rig are on disk, so the generator never needs to run again. Either way, it's the cheap path to "change the last step without paying for the first ones."
Installing it
Standard install; it reads images and builds state, no GPU math of its own (though a downstream bake still needs the renderer):
cd ComfyUI/custom_nodes
git clone https://github.com/visualbruno/ComfyUI-Hunyuan3d-2-1
cd ComfyUI-Hunyuan3d-2-1
pip install -r requirements.txt
Common issues
The obvious one: wrong path. Point it at a meta_data.json that isn't there and it errors on file open. Second: if the metadata was written by an older generator run, it may lack the albedos_upscaled fields - the code guards for None, so it falls back to the originals, which is correct behavior, just not what you might expect if you thought you upscaled. And the mesh you feed should match the one in the metadata's mesh_file; mismatched geometry and views produce smeared bakes, silently.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| trimesh | TRIMESH | — | |
| metadata_file | STRING | — | |
| view_size | INT | 512 | — |
| texture_size | INT | 1024 | — |
Outputs (4)
| Name | Type | Description |
|---|---|---|
| pipeline | HY3DPIPELINE | — |
| albedo | IMAGE | — |
| mr | IMAGE | — |
| camera_config | HY3D21CAMERA | — |