Three App

In the WAS Three.js suite, Three App is the node everything reports to. Geometry goes into a mesh, meshes go into a group, the group and a light go into Three Scene, and then a scene and a camera need somewhere to be turned into an actual picture. That somewhere is here. Wire scene and camera in, pick your renderer settings, and the single app output feeds whichever sink you're using: Three Viewer to look at it live, Three Render to capture frames as an IMAGE batch, or Three Compile to write out a standalone web page.

Don't think of it as a big scary aggregator. It's really the camera-plus-renderer settings sheet - the same decisions you'd make in any 3D tool before hitting render. The ones beginners actually set:

• tone_mapping - how brightness above 1.0 is squashed into a viewable range. aces is the filmic default and is right for almost everything. none shows raw values and clips them (occasionally what you want for a flat technical render). agx is gentler if aces feels heavy.
• exposure - overall brightness going into that tone map. 1.0 is neutral, 2.0 is a stop up. This is your global brightness knob; reach for it before you start re-lighting.
• loop_seconds - set the hidden clock of the whole animation. It's the length the viewer loops over, the axis Three Render's strip is drawn against, and the span every per timeline motion in Three Animate Transform is spread across. 4.0 is a steady turntable loop; 20.0 is a long move your render takes a few seconds out of.
• shadows and shadow_quality - shadows on by default, and 2048 is a sane map size. A light and a mesh have to opt in too, so if your render has no shadows despite this being on, check them.
• orbit_controls with auto_rotate - orbit lets you drag the viewer to spin around; auto_rotate turns the camera on its own (it pauses while you drag). Great for a self-demoing scene.

There's also the optional effects socket, which is where a post chain from Three Bloom, Three Depth Of Field or Three Antialias plugs in. Leave it unwired and the frame is drawn exactly as-is.

How it works under the hood

Nothing here is rendered on your server. Three App bundles the scene, camera and settings into a typed descriptor - a plain description of the app - and hands it to the browser, where the three.js bundled inside the pack draws it on a WebGL surface. That's the architectural trick of the whole Three suite, and it's why a 43-node 3D subsystem can ship in a pack that installs zero Python packages.

Installing it

This is WAS Node Suite v3. Install via ComfyUI Manager (search WAS Node Suite v3) or:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui.git

Restart, and you need ComfyUI 0.14.0+ / Python 3.10+. Nothing downloads - three.js is bundled. If the menu is absent, set features.threejs: true in <ComfyUI user dir>/was-node-suite/config.yaml.

If it looks wrong

The classic mistake is wiring a mesh into the scene socket - a mesh is a THREE_OBJECT, the socket wants a THREE_SCENE, and ComfyUI will refuse the wire. And remember the capture caveat that bites everyone: Three Render draws in an open ComfyUI browser tab, so a headless queue stops rather than hangs. And if your still looks jaggy, it's antialias or pixel_ratio_limit on this node, not your GPU.