📤 Settings Pipe Unpack

The 📤 Settings Pipe Unpack is the companion to the pack's ⚙️ Flux/Sdxl Settings Pipe: it takes a FLUX_PIPE in and hands you every field as its own output. If the Settings Pipe is the one-stop place to configure sampling, this is the node that spends that configuration - without making you dig into a dict or wire a pipe into a node that doesn't speak pipes.

Why the first output is a pipe

The design detail worth understanding: the first output is also pipe - the same bundle you fed in, passed straight through. That's deliberate. The pipe output is meant to keep the chain extendable: you can unpack the settings here, and simultaneously forward the bundle to another compatible node downstream. One cable in, two uses out, no extra wiring. It's the same "forward the context" pattern that runs through the whole pack's pipe nodes.

What comes out

All ten outputs mirror what the Settings Pipe produced:

• pipe (FLUX_PIPE) - pass-through for chaining.
• LATENT, width, height - the blank latent and its dimensions.
• sampler (SAMPLER object), sigmas (SIGMAS), noise (NOISE), seed (INT) - the sampling components.
• cfg (FLOAT) and conditioning (CONDITIONING) - the guidance/CFG side.

If you're old-school and prefer explicit wires over bundles, this is how you go back: pack once at the start, unpack where you actually need the pieces. KSampler-class nodes take the sampler, sigmas, noise, and latent; the conditioning feeds CLIP/KSampler; width/height can flow into metadata or size-dependent nodes.

The honest caveat

The unpack does no validation and no defaulting magic - it pulls whatever keys exist in the pipe and returns None or zeros for anything missing. Feed it a pipe built by something other than FluxSettingsPipe and the outputs may be empty; there's no error to tell you. In practice that only bites if you construct FLUX_PIPEs by hand or from a third-party source. For pipes produced by this pack's own settings node, it just works.

It also doesn't add anything the Settings Pipe doesn't already have - there's no resolution list here, no presets, nothing to configure. The only input is pipe. That's the point: configuration lives in exactly one place, and this node exists purely to spend it.

Install

Part of Light-x02 Nodes - ComfyUI Manager → search "ComfyUI-Lightx02-Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/Light-x02/ComfyUI-Lightx02-Nodes

Restart ComfyUI, find it under 💡Lightx02/utilities. No extra dependencies. It's bundled with the settings pipe it pairs with, so installing the pack gets you both ends of the workflow.