Preview3DAnimation_motorway_edition

If Preview3D is the "look at a model" node, this is its sibling that also presses play. Preview3DAnimation is the same browser-based 3D viewer from ComfyUI core, but for .glb/.gltf files that carry animation - a character rig doing a walk cycle, a spinning object, a camera path. It loads the model, plays the embedded animation, and lets you scrub around it, which is exactly what you want when the model's whole point is that it moves.

Like its static sibling, this is an output node: it renders a viewer and has no real data outputs. So the _motorway_edition wrapper is about as thin as they get. It takes the MOTORWAY 🚌💨 bus, shows whatever model the widgets point at, and returns the bus untouched so the rest of your chain keeps flowing. There's nothing to fetch by key because the original node only has widget inputs.

The widgets

• model_file - path to the animated .glb or .gltf. Relative paths resolve against ComfyUI's input folder.
• material - original, normal, wireframe, or depth. For animation work, wireframe is great for checking that a rig actually moves the way you expect.
• up_direction - axis correction (original, -x, +x, -y, +y, -z, +z) for models that load sideways.

That's the whole input surface. The MOTORWAY 🚌💨 input is optional, so the node can tag along at the end of a bus workflow or act as a standalone start.

Install

No Python dependencies, no bundled models - pure code:

cd ComfyUI/custom_nodes
git clone https://github.com/agilly1989/ComfyUI_agilly1989_motorway

or ComfyUI Manager → search ComfyUI_agilly1989_motorway → install → restart.

What to know before you trust it

A few honest notes, in rough order of how much they'll bite you.

The pack is a beta project - the README's first line is effectively "IF THINGS BREAK ITS BECAUSE I BROKE IT" - and it's changed shape a lot. The _motorway_edition clones were produced by an auto-cloner that build 1.1.7 removed, so a fresh install may not have this node in the menu at all. The stock Preview3DAnimation in core ComfyUI is always there and does the same thing.

The viewer itself is browser-rendered WebGL, which means it's a quick-and-dirty inspection tool, not a final-quality preview. If you're judging actual animation quality you'll still export and open the file in a proper viewer. There's also a real chance the browser tab isn't the place your animation looks right - but for "did the rig move and does the loop close," it's perfect.

And one bus-shaped gotcha: if something downstream throws KeyError: 'hash_...' doesn't exist in motorway, that's a key-name mismatch between your ramp nodes and your readers - this viewer node can't cause it, because it reads nothing from the bus. Keys are case-sensitive and silently overwrite on collision, so keep names consistent and you're fine.