TY360 Preview

Every 360 photo dies in the default ComfyUI preview. An equirectangular (ERP) panorama is a 2:1 image meant to wrap around a sphere, so laid out flat it's just a squashed strip - the horizon bends, the poles stretch into soup, and you cannot tell what you're actually looking at. TY360 Preview is the fix: it wraps your ERP image around a virtual sphere and lets you drag to look around inside it, inside the ComfyUI canvas.

That's the whole node, and that's fine. It exists so you can actually see a 360 image before you do anything with it - check a photo came out clean, eyeball which direction is the front of the room, or inspect the result of a pasteback edit.

How it works

The backend side is almost trivial: the node takes your image and saves it as a preview through the same path ComfyUI's own PreviewImage uses, flagged as pano_input_images. The clever part is frontend. A WebGL widget renders that saved frame wrapped around a sphere, and you navigate it like a tiny panorama viewer: drag to pan yaw and pitch, scroll to zoom the field of view. There's a grid overlay so you can keep your bearings - handy when the whole scene looks like a white apartment.

Don't expect it to transform anything. This is a display node, pure eyeball.

The one input

• erp_image (IMAGE) - the equirectangular image to look at. Wire it from whatever node produces your ERP: a load, the output of TY360 Pasteback, anything.

It has no outputs, so it ends a branch. Put it where you'd put a PreviewImage node - in fact, in the pack's demo workflow it's wired after Pasteback so you can drag around the final edited sphere.

Installation

Same as the rest of this pack - it's all one repo, supart/ComfyUI-TY360-Photo-Edit. Easiest path is ComfyUI Manager: search "TY360" and install the pack. Or clone it manually:

cd ComfyUI/custom_nodes
git clone https://github.com/supart/ComfyUI-TY360-Photo-Edit

Then restart ComfyUI. There's no requirements.txt and no model download - it only uses numpy, torch and PIL, all of which ComfyUI already ships, so there's nothing extra to fetch.

Common issues

• Nothing renders until you run the graph. The widget shows the last executed output of whatever feeds it, so an empty gray box usually just means you haven't hit Queue yet.
• It won't save anything. It's a viewfinder, not an exporter. Put a SaveImage on the same branch if you want the file.
• WebGL hiccups. The interactive viewport needs a browser that can do WebGL; on a headless VM or a remote box without GPU-accelerated browser rendering, the preview can stay blank even though the node ran fine. The data isn't lost - the image is still flowing downstream - it's just your screen that can't keep up.

That's it. One input, zero outputs, and suddenly your 360 work stops being guesswork.