Blender Input Load 3D

If your workflow generates or edits 3D - texture generation, mesh-to-image rendering, Hunyuan3D-style mesh workflows - it needs a way to pick which 3D file to operate on. BlenderInputLoad3D is the pack's answer: it lists every 3D file in the server's input/3d folder and hands the chosen one to the workflow as a file path. On the Blender panel it becomes a dropdown of your .gltf, .glb, .obj, .fbx, and .stl assets, with upload support.

This one isn't a subclass of a native loader - ComfyUI has a native Load 3D node, but its file list isn't shaped the way this pack needs, so the source builds the list itself. It reads the input/3d directory, filters to the five extensions above, normalizes backslashes to forward slashes (so a path looks right on Linux even if it was dropped in from Windows), and returns the path as an any-type output. The 3d subfolder is created for you if it doesn't exist.

Inputs and outputs

• model_file - the 3D file to use, chosen from everything in the server's input/3d folder. A dropdown in Blender, with a file-upload option so you can push a mesh over from the panel.
• order - panel position, lower first.

Output is a single * (any type) - the path string of the selected file. It feeds whatever consumes a 3D file in your workflow: a mesh/texture generator, a 3D-to-image renderer, or a node that saves 3D output downstream.

Installing it

Standard for the pack. ComfyUI side, ComfyUI Manager → search "ComfyUI-Blender", or:

cd ComfyUI/custom_nodes
git clone https://github.com/alexisrolland/ComfyUI-Blender

Restart ComfyUI. No extra Python dependencies, but you need a current ComfyUI - schema v3 nodes, and the README says latest is required. The Blender add-on is the other half, a ZIP from the latest release installed via Edit > Preferences > Add-ons > Install from Disk.

Where people get burned

The folder is input/3d specifically - a mesh sitting loose in input/ or somewhere else on disk won't appear, and the dropdown quietly stays empty. Drop files in the right subfolder (or upload through the panel). Second, the list is generated when the node loads; add a file and it won't show up until ComfyUI refreshes the node. Third, the file needs to be on the server, which is the recurring remote-ComfyUI gotcha across this whole pack. And remember: this node hands over a path - it doesn't load the mesh into a renderer, so check what your downstream node actually expects. Panel appears after an API-format export and import, title-as-label and all. It's a niche node - you'll only reach for it in genuine 3D workflows - but when you do, it's the correct tool.