Blender Scene

First thing to know about "Blender Scene": the name is honest about half of it. It's a real Blender scene, but it is not a stage you Run. It's a DCC-style workbench embedded in a ComfyTV node - a live 3D viewport where you build and arrange a scene, and which the other Blender stages render from. If you hit Run on it, the node raises a StageError that basically says "this is a workbench, go pull renders with the Camera or Animation stage." That's not a bug; that's the design.

In ComfyTV's canvas model, everything is a stage and every stage emits a snapshot downstream. The Blender Scene stage is the exception that proves the rule: it emits nothing, because its job is to be the source the Camera and Animation stages read. Think of it as the scene file, and the render stages as the cameras pointed at it. You wire those downstream, not this node.

How it works

The card embeds a live Blender viewport streamed over a WebSocket from a separate "blender-web" renderer process - real Blender, running headless-ish as a bridge, with a status dot up top (green = bridge online, showing the Blender version; red = "waiting for the Blender bridge"). Scene edits happen live in that viewport, and there's an "add model from asset library" button to drop 3D assets into the scene, plus a fullscreen toggle when you need to actually see what you're doing.

That's also the whole heavy-dependency story, and it's worth flagging before you plan a 3D pipeline: ComfyTV itself has zero extra Python dependencies, but these Blender stages need the separate blender-web distribution running as a bridge (launched via blender-for-comfytv.bat), reachable at http://127.0.0.1:7684. No bridge, no viewport, no renders.

Inputs and outputs

• Inputs: only the internal stage plumbing - force_run_token, project_id, parent_output_id. Nothing for you to set.
• Outputs: none. is_output_node is false. This stage produces no data flow; it produces a scene.

That's the entire point. If you're used to every ComfyUI node consuming and emitting, this one breaks the pattern on purpose - it's state, not a function.

Install

Standard ComfyTV install: ComfyUI Manager (search ComfyTV) or

cd ComfyUI/custom_nodes
git clone https://github.com/jtydhr88/ComfyTV

then restart. Then make sure the blender-web bridge is up before you expect a viewport - that's the one non-obvious moving part.

Where people get burned

Almost every "my Blender stage doesn't work" complaint starts and ends with the bridge. The node card shows a red dot and "waiting for the Blender bridge," and the render stages fail with "Blender bridge is not running. Launch the blender-web distribution with blender-for-comfytv.bat and try again." On Desktop or macOS, the usual ComfyTV install gotcha also applies - clone into the running instance's custom_nodes by absolute path, or you'll install into a dead copy and wonder why nothing registers. Get the bridge up, get the scene built, and this node quietly disappears into the workflow where it belongs.