Flux DeGuidance

FluxDeGuidance is a two-input conditioning node with a single job: it stamps a guidance value onto your conditioning, which Flux's guidance embedding then reads during sampling. It's the pack's answer to the stock FluxGuidance node - same idea, fewer moving parts - and it appears in nearly every example workflow in the repo, because the pack's samplers expect the model to know its guidance strength.

Why Flux needs this at all

Flux Dev is a guidance-distilled model. The distillation bakes prompt adherence in, so there's no CFG-style negative prompt - but the model architecture still has a "guidance" embedding, a value the model was trained with, and sampling without setting it leaves the model running at whatever the default happens to be. The stock guidance for Flux Dev is typically 3.5. Schnell doesn't use guidance (it's more aggressively distilled), which is why you'll see this node on Dev workflows and not Schnell ones. In the pack's RF-Inversion example, there are two FluxDeGuidance nodes - one for each branch of the edit.

How to use it

Inputs:

• conditioning (CONDITIONING) - your CLIPTextEncode output.
• guidance (FLOAT, default 3.5) - the value to embed. Range is -100 to 100, but you'll live between about 2 and 5.

Output:

• CONDITIONING - the same conditioning, now carrying a guidance value. Wire this into your guider.

The range's low end is a trap worth mentioning: you can go below zero and it won't crash, but there's no good reason to. For Flux Dev, 3.5 is the community default and the pack's default; treat it as a fine-tune knob, not a "how much do you want your prompt followed" dial.

Installation

Standard for the pack: ComfyUI Manager → search "ComfyUI-Fluxtapoz" → install → restart, or git clone https://github.com/logtd/ComfyUI-Fluxtapoz into custom_nodes. einshape is the only dependency; no model downloads.

Common issues

• "My Flux output ignores the prompt completely." On a guidance-distilled Dev model, an unset guidance value can produce flat, under-adhered output. Setting it via this node (or stock FluxGuidance) is the fix.
• Don't also wire a stock FluxGuidance node into the same path - two nodes stamping the value is fine (last one wins) but it's needless confusion; pick one.
• Schnell users don't need it. If you're on Schnell and the value seems to do nothing, that's correct behavior, not a bug.

It's the most boring node in the pack's editing chains and also the one you can't skip on Dev - think of it as the pack's way of making sure the guidance embedding is always populated.