DP Draggable Floats 1

A single float value you can drag, ranged 0 to 1. That's it, and that's the point - it's a clean little knob you park somewhere obvious in your graph and use to feed a strength, a denoise, or a weight that you tweak a lot. Instead of hunting for the tiny number field buried inside a KSampler or a LoRA loader, you promote that one value to its own node where it's easy to grab and adjust.

The 0-to-1 range is deliberate and it maps to the most common tunables in image work: denoise strength on an img2img pass, ControlNet strength when you're keeping it under 1, IP-Adapter weight, LoRA strength when you're staying conservative. Anything that naturally lives between "off" and "full."

The one input

• float_value (0–1, step 0.01, default 1) - drag it, or type it. Steps in hundredths, so you get fine control between 0.00 and 1.00.

Output is a single float_value (FLOAT) that wires into any float input downstream.

Why bother promoting a number to its own node

Two real reasons. First, ergonomics: in a big graph, the value you actually iterate on shouldn't be the one you have to zoom in to find. Put it on a draggable node near the edge of your canvas and it's always one grab away. Second, reuse: one knob can drive several inputs at once. Wire this into two nodes' strength fields and now a single drag moves both in lockstep - no more setting the same number in three places and forgetting one. That "one source of truth for a value" habit is exactly what quality-of-life node packs exist to encourage.

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 a value above 1. This node caps at 1.0 by design. For strengths that go higher - CFG, LoRA strengths you want to push past 1, or anything with headroom - use DP Draggable Floats 3 (which ranges 0–2) or a plain float primitive. Don't fight this one; it's the 0–1 tool on purpose.

It's not connecting to an integer input. It outputs a FLOAT. If the target wants an INT (a step count, a seed, a frame number), use one of the DP draggable int nodes instead. ComfyUI won't silently convert.

Do I need three separate float nodes? The pack ships 1-, 2-, and 3-value versions so you can keep related knobs in a single node instead of scattering three of these around. If you've got one lonely value, this is the right size; if you're tuning a pair or a trio, grab the 2 or 3 variant and save canvas space.