Pipe Out Generation Data II

Pipe Out Generation Data II [RvTools] takes a pipe in and unpacks it into fourteen named outputs - sampler, scheduler, steps, cfg, seed, resolution, prompts, model and VAE names, LoRAs, denoise, clip skip - while also passing the original pipe through untouched. It's the "read the bus" node that pairs with the pack's Pipe In nodes, and it's how you turn an opaque pipe back into individual wires you can actually use.

Why you'd reach for it

Pipes are a great way to move data, and a terrible way to see it. Once your generation settings are bundled on one wire, you've lost the ability to grab just the seed, or just the positive prompt, to feed a metadata writer, a display node, or a comparison. This node opens the bundle: pipe in, and every field pops out as its own typed output ready to wire anywhere.

It's also the answer to "what did this run actually use?" - wire it into the tail of your graph, attach the outputs to a text saver or ShowText, and your generation log writes itself. Given how much of the community runs on "workflow included" reproducibility, that's a genuinely useful habit.

How it works

The pipe it expects is the pack's Generation Data format - a 15-element tuple the author's Pipe In Generation Data nodes produce. execute simply unpacks that tuple into the named outputs and returns them alongside the original pipe. No transformation: what went in comes out, just visible now.

Input: pipe - the pack's generation-data pipe.

Outputs: pipe (passthrough) plus sampler_name, scheduler, steps, cfg, seed_value, width, height, positive, negative, modelname, vae_name, loras, denoise, clip_skip.

Install

Standard RvTools install:

• ComfyUI Manager → search "RvTools" → install ComfyUI-RvTools_v2 → restart.
• Or: cd ComfyUI/custom_nodes && git clone https://github.com/r-vage/ComfyUI-RvTools_v2, then restart.

No models or downloads.

Gotchas

The one real constraint: it's specific to the pack's pipe format. This is the "II" (v2) version of the generation-data pipe - a 15-field tuple with a PipeVersion = 'V2' marker. If you feed it a pipe from a different source (rgthree's context, or another pack's settings pipe), the unpacking will mismatch and you'll get garbage or an error. The author iterated on this format - that's why there's a v1 and a v2 of the pipe family - so old saved workflows may be carrying the v1 shape that this node can't read. If outputs look wrong, check which generation-data node created the pipe.

And the standing pack note: RvTools v2 is deprecated (successor ComfyUI_Eclipse), and v1-era node names in old graphs won't auto-map. The pipe format itself may differ between versions too, so be ready to rebuild that section when migrating.