DP Draggable Floats 3
Three float knobs, 0–2 range for the ones that go past 1
- float_value1
- float_value2
- float_value3
Three draggable float knobs in one node - and the detail that actually matters here versus the 1- and 2-value siblings: the range is 0 to 2, not 0 to 1. That wider ceiling is the reason to pick this one specifically. It's built for values that legitimately go past 1.0.
Which values are those? LoRA strengths you want to overdrive. CFG-adjacent scales. ControlNet strengths pushed above 1 for a stubborn condition. Weights where 1.0 is "normal" and you sometimes want "more than normal." The 0–1 knobs can't reach up there; this one can, three at a time.
The inputs that matter
float_value1(0–2, step 0.01, default 1)float_value2(0–2, step 0.01, default 1)float_value3(0–2, step 0.01, default 1)
Three independent knobs, each stepping in hundredths from 0 to 2, each with its own matching output (float_value1, float_value2, float_value3, all FLOAT). They don't interact - the node is a container for three tunable floats, nothing more.
Why the 0–2 range earns its own node
A default of 1.0 with room to double it is the natural shape for strength-style parameters. Think three LoRA strengths you're balancing in a stack: you want each to sit around 1.0 but occasionally push one to 1.3 to make its concept win, or pull another to 0.6 so it stops fighting. A trio of 0–2 knobs on a single node is the clean way to do that - everything you're balancing is visible and adjustable in one spot. It's the same promote-your-tunables ergonomics as the rest of the draggable family, sized for three values and pitched at the ones with headroom.
How to install it
ComfyUI Manager: search ComfyUI-Desert-Pixel-Nodes, install, restart. Or:
cd ComfyUI/custom_nodes
git clone https://github.com/DesertPixelAi/ComfyUI-Desert-Pixel-Nodes
then restart. No dependencies, no models. Under the "DP" utils category.
Common issues & troubleshooting
I need to go above 2.0. The cap is 2.0. That's already generous for most strength parameters - pushing a LoRA past 2 usually just fries the output rather than strengthening the concept. If you genuinely need more, a plain float primitive has no ceiling, but reconsider whether the value is doing what you think first.
These outputs aren't summed or averaged. Correct - three separate knobs, three separate wires. No math happens inside the node.
Which draggable float do I actually want? Count your values and check your range. One value in 0–1: Floats 1. Two in 0–1: Floats 2. Anything that needs to exceed 1.0, or a set of three: this one. Don't reach for the 0–2 node just to hold a single denoise value that never leaves 0–1 - the narrower knobs give you the same fine control without the extra clutter.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| float_value1 | FLOAT | 1.000–2 | — |
| float_value2 | FLOAT | 1.000–2 | — |
| float_value3 | FLOAT | 1.000–2 | — |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| float_value1 | FLOAT | — |
| float_value2 | FLOAT | — |
| float_value3 | FLOAT | — |