Comfy3DPacktoTD
Take a 3D-Pack mesh into TouchDesigner as a point cloud
- mesh
Comfy3DPacktoTD is the node that moves a mesh out of ComfyUI-3D-Pack and into TouchDesigner. It takes the MESH output of 3D-Pack's generators, converts it to a colored point cloud, and streams it over WebSocket where the ComfyUI2TD.tox component parses it into CHOPs. If your 3D generation pipeline runs through 3D-Pack - TRELLIS, Hunyuan3D, TripoSR, StableFast3D and friends - this is the node that gets the result into a live TD project.
The single most important thing to internalize: this is a point cloud, not a mesh, on the TD side. The node throws away the faces and sends vertices plus colors. TD renders points, which is perfect for realtime point-cloud visuals and particle-style effects, but it's not a shaded, textured mesh. If you were picturing an OBJ-style model drop, reset that expectation.
How it works
3D-Pack's MESH objects carry vertices (.v), a UV layout (.vt), an albedo texture, and often vertex colors (.vc). The node reads the vertices and then tries, in order: bake per-vertex colors from the albedo texture using bilinear UV lookup; use existing vertex colors; or, if neither exists, generate colors from normalized positions so the point cloud still has some visual structure. Everything gets packed into a binary PLY (position + RGBA per vertex) and shipped over the WebSocket. The tox parses it into a point-cloud CHOP you can transform and render in TD.
The inputs
An output node - nothing wires onward.
- mesh - the
MESHsocket from any 3D-Pack generator. - broadcast - off by default (current client only).
Install
This one has two installs. First the pack:
cd ComfyUI/custom_nodes
git clone https://github.com/JiSenHua/ComfyUI-TD.git
(Or ComfyUI Manager, search ComfyUI-TD.) Then the real dependency: ComfyUI-3D-Pack itself, which is a heavyweight install with a lot of native wheels and models - the README candidly recommends a cloud image if local install fights back. The ComfyUI2TD.tox component must be v5.1.x+.
Gotchas
The pack README calls out one trap specifically: Hunyuan3D_V2 inside 3D-Pack and Hunyuan3DWrapper are not interchangeable, and you must pair each 3D generator with its matching transmission node. A Hunyuan3D run through 3D-Pack gets Comfy3DPacktoTD; a Hunyuan3D run through kijai's wrapper gets Hy3DtoTD - wire them crosswise and you'll feed a MESH into a node expecting a different object type. Also, since colors are baked from albedo via UVs, a mesh without a UV layout will fall back to generated positional colors and look flat/rainbow rather than textured. And remember the cloud caveat from the README: on the hosted image, only TRELLIS, Hunyuan3D_V2, TripoSR, and StableFast3D are verified.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| mesh | MESH | — | |
| broadcast | BOOLEAN | false | — |
Outputs (0)
No outputs