☁️BizyAir Hy3DExportMesh

What it is

This is the finishing node for a Hunyuan3D pipeline - the one that takes the 3D mesh a Hunyuan3D workflow generated and actually writes it to a file you can open elsewhere. Hunyuan3D is Tencent's 3D generation line (2.0 released in January 2025, with 2.1 following), and it's one of the few genuinely open corners of 3D asset generation - the KB flags it as "the portfolio's least contested ground," with no real open equivalent from other major labs. This node is part of BizyAir's Hunyuan3D wrapper, running that generation pipeline on their cloud rather than yours, with this specific node handling the export step at the end.

You'd use it as the last node in a text-to-3D or image-to-3D chain, after whatever upstream BizyAir nodes actually produced the trimesh.

How it works

It takes a mesh object and writes it to disk in whichever standard 3D format you choose, using your specified filename prefix. There's no generation happening here - this is purely the export/serialization step, converting an in-memory mesh representation into a file format that Blender, a game engine, a slicer, or any other 3D tool can actually open.

Inputs and outputs that matter

trimesh is required and is the actual 3D mesh data - the output of an upstream Hunyuan3D generation node in the same pipeline, not something you'd construct by hand. filename_prefix defaults to 3D/Hy3D and controls where and how the output file is named. file_format picks the export format: glb, obj, ply, stl, 3mf, or dae - glb is the safest general-purpose default if you're not sure what your downstream tool expects, since it's the most broadly supported modern format for textured meshes; stl is the one to reach for specifically if you're heading toward 3D printing, since it's the format most slicers expect.

The optional save_file (default true) controls whether the file actually gets written - turn it off if you only want the path returned without committing anything to disk, though in practice most people will leave this on. The output is glb_path, a string with the file's location - despite the name always being glb_path, this is populated for whatever format you actually chose in file_format, not literally always a .glb file, so don't be thrown by the output name if you exported to .obj or .stl.

Installing it

Install through ComfyUI Manager (search "BizyAir") or git clone https://github.com/siliconflow/BizyAir.git into custom_nodes, then restart ComfyUI. A BizyAir API key is required before any node in the pack, including this one, will run - register through the login prompt on first use.

Common issues

Since this node is purely the export step, if your output file is missing or empty, the problem is almost always upstream - check whether the Hunyuan3D generation nodes actually produced a valid trimesh before troubleshooting this node itself. If you're expecting a .glb extension on your output file and got something else, double check file_format - the output socket name doesn't change with your format choice, which is easy to misread as a bug. And because mesh generation runs on BizyAir's cloud like everything else in this pack, a slow or stalled export is more likely to be an upstream generation step still finishing than a problem with this node specifically.