Pipe Out Sampler Settings (Flux)

Flux doesn't sample like SD1.5. It's flow-matching, which means a near-straight noise trajectory, few steps, no Karras, and a separate flux_guidance knob instead of classic CFG. When a workflow needs to carry all of that around as one bundle, RvTools packs it into a pipe - and this is the node that unpacks it on the other end.

"Pipe Out Sampler Settings (Flux)" takes a single pipe input and splits it into the fields a Flux sampler cares about: sampler, scheduler, steps, cfg, flux_guidance, denoise, sigmas_denoise, and noise_strength. The pipe passes through unchanged, so you can keep routing the bundle onward while also consuming the individual values. The source is, again, a pure tuple unpack - the values were captured upstream by a matching sampler-settings Pipe In node, and this node's only job is handing them out at the point of use.

Which outputs actually matter for a beginner?

• sampler, scheduler - for Flux, that's Euler-family sampler on a conservative scheduler (beta or simple), not the DPM++ 2M Karras you'd reach for on SDXL. The sampler panel's architecture rule in a nutshell: flow models want a straight-line path, and aggressive schedules distort it.
• steps - Flux runs fine at surprisingly low counts; distilled variants go as low as 4-8.
• flux_guidance - Flux's answer to CFG. Keep it modest; crank it and you get overbaked contrast, not "more prompt adherence."
• denoise - the img2img strength knob, 0 to 1.
• sigmas_denoise, noise_strength - the noise-injected sampling (NIS) fine-tuners: where on the sigma schedule the denoise starts, and how much fresh noise gets mixed in. You'll mostly touch these for inpainting-style and iterative workflows, not plain text-to-image.

The point of the pipe is that all eight values travel as one wire, so the sampler settings can't drift out of sync between the place you configure them and the KSampler that consumes them. That's the whole RvTools pipe philosophy, and for a parameter set this large it earns its keep.

Installing it

Ships in ComfyUI-RvTools_v2. ComfyUI Manager: search "ComfyUI-RvTools_v2". Or:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI-RvTools_v2

Restart ComfyUI; requirements (torch, numpy, Pillow, opencv-python, pilgram, pynvml, piexif) install through Manager. No models to download.

Where people get burned

• Wrong pipe, crash. This unpacker expects the eight-field Flux pipe. Wire in a Small pipe (four fields) and execution dies with a tuple-shape ValueError. The pipe type is the same on every wire, so ComfyUI can't catch this for you.
• Deprecation. The RvTools v2 pack is unmaintained and the README points to the successor ComfyUI_Eclipse. The nodes still run fine; new builds should check Eclipse for the same pair.
• Don't confuse it with the variants. There's a Flux+Seed version (adds a seed output) and a Small Flux version (drops the NIS knobs). Grab the one that matches the pipe you're actually feeding - see the family articles for the differences.