TripoSRtoTD

TripoSRtoTD streams TripoSR meshes into TouchDesigner as colored point clouds. It takes the MESH output of ComfyUI-Flowty-TripoSR - TripoSR being the fast image-to-3D model that turns a single photo into a mesh in seconds - converts it to vertices plus colors, and ships it over WebSocket where the ComfyUI2TD.tox component parses it into a point-cloud CHOP.

What makes this node interesting is TripoSR's speed. The whole TripoSR pitch is "one image in, mesh out" in a few seconds, which is fast enough to feel realtime. Combined with this bridge, that's a genuinely interactive workflow: capture or generate a reference image, run TripoSR, and watch a 3D point cloud of it appear in TD almost immediately - good for live product spins, scanned-object style visuals, or just fast 3D iteration inside a TD project. As with every 3D node in this pack, what you get on the TD side is points, not a shaded mesh.

How it works

The node takes the MESH from ComfyUI-Flowty-TripoSR (it also tolerates a mesh list, using the first entry), extracts the vertex positions, and applies a coordinate rotation so the model arrives oriented sensibly in TD's space rather than sideways. Colors come from the mesh's vertex colors, or from face colors averaged onto vertices when only faces are colored, with a generated fallback if neither exists. The result is packed into a binary PLY (position + RGBA) and pushed over the WebSocket for the tox to parse.

The inputs

An output node - nothing wires onward.

• mesh - the MESH socket from ComfyUI-Flowty-TripoSR.
• broadcast - off by default (current client only).

Install

Pack first:

cd ComfyUI/custom_nodes
git clone https://github.com/JiSenHua/ComfyUI-TD.git

(or ComfyUI Manager, search ComfyUI-TD). Then the real dependency: ComfyUI-Flowty-TripoSR, which brings TripoSR's model. Add the ComfyUI2TD.tox component (v5.1.x+). This is one of the lighter 3D paths in the pack - TripoSR is a small, fast model compared to the Hunyuan/3D-Pack installs, so it's a reasonable first 3D node to try.

Gotchas

The classic gotcha is shared with all the mesh-to-TD nodes: what you get is a point cloud with per-vertex color, not a textured surface - a mesh with no vertex or face color data falls back to generated colors and looks flat. The coordinate reorientation is automatic, so don't be surprised that TripoSR's raw orientation differs from what shows up in TD; that's the node doing its job. And keep the MESH wiring honest: this node pairs with Flowty's TripoSR pack specifically, so if your mesh came from 3D-Pack's TripoSR, that's a different object type and the node won't take it.