ComfyUI Node

float _O

The boring pass-through node you'll wire up anyway

By omar92·Created 3 years ago·Updated 5 months ago· 181
float _O
    • FLOAT
    float0.00

    Some nodes do glamorous things. float _O holds a number and hands it to the next node. That's the entire job, and it's one of those quiet quality-of-life nodes you don't think about until you're building a workflow that needs a reusable value - a CFG, a denoise strength, an upscale factor - in more than one place. Instead of retyping 0.45 into four different nodes (and updating all four when you change your mind), you type it once into float _O and wire the output wherever it's needed.

    It's from the Quality of Life Suit pack's O/utils folder, sitting alongside int _O, Text _O, and seed _O. They're all the same idea: a plain input widget exposed as a typed output, so the graph is the single source of truth for a value instead of a scattering of identical widgets. If you've used rgthree or similar "everything wired up" packs, you know the pattern - this is the minimal version of it.

    How it works

    It's a straight pass-through. The source takes your float input and returns it unchanged as a FLOAT - no clamping, no conversion, no surprises. What you type is what comes out.

    • float (FLOAT) - the value. Default 0, and the widget's range runs 0 to a huge max, so there's no negative side to the slider. If you need negatives, just type one in.

    That's it. One input, one output.

    Where it fits

    The genuinely useful pattern is wiring it into nodes that accept a FLOAT input, so you get one visible control for a value that's used in several places. Pair it with the pack's math nodes when you want to derive the value instead of typing it: run float _O into Equation1param _O, and suddenly your denoise strength is x * 0.8 + 0.1 computed for you. Convert it to text with floatToText _O when you need the number inside a prompt string or a filename.

    If you just need a one-off number inside a single node, this is pointless overhead - the widget on that node is fine. The moment the same number matters in two places, though, the utility node wins.

    Installing it

    Ships in the Quality of Life Suit pack (omar92/ComfyUI-QualityOfLifeSuit_Omar92). Install via ComfyUI Manager (search "Quality of Life Suit") or clone:

    cd <ComfyUI>/custom_nodes
    git clone https://github.com/omar92/ComfyUI-QualityOfLifeSuit_Omar92.git
    

    Restart ComfyUI, not just a browser reload. No models, no dependencies. The pack creates a config.json on first launch with autoUpdate: true, so it can pull new commits on startup; flip it to false if you'd rather it not.

    Common issues

    • "I set the widget but my node reads something else." A pass-through can't corrupt a value - if the downstream node shows a different number, check whether you converted types on the way (an int round trip will drop decimals). That's usually a floatToInt _O doing its job, not this node failing.
    • Nothing to see here. Honestly, this node is so simple that if you're troubleshooting it, the bug is elsewhere in the graph.

    It's not a node you'll brag about. It's a node that keeps a workflow tidy - and for a value you tweak constantly, that's quietly worth a lot.

    CategoryO/utils

    Inputs (1)

    NameTypeDefaultDescription
    floatFLOAT0.000–18446744073709550000

    Outputs (1)

    NameTypeDescription
    FLOATFLOAT