Nodes/ComfyUI-ArchAi3d-Qwen/πŸ”’ Float Input
ComfyUI Node

πŸ”’ Float Input

A float input node with a name β€” which matters more than it looks

By amir84ferdosΒ·Created 11 months agoΒ·Updated 5 months agoΒ· 70
πŸ”’ Float Input
    • FLOAT
    β—„namefloat_inputβ–Ί
    β—„value0.00β–Ί
    β—„min-10000000000.00β–Ί
    β—„max10000000000.00β–Ί
    β—„step0.0100β–Ί

    ComfyUI already has a float input widget on a hundred nodes, so why does a pack ship its own? The answer is in one input: name. This is a bare input node - value, min, max, step, and out comes a FLOAT - but the name field exists for ComfyUI web interfaces that generate dynamic HTML forms from workflow inputs. Name it denoise_strength and a web UI can render a proper labeled slider for it, driven by the min/max/step you set. In the desktop app it's a regular widget; the node becomes genuinely useful when your workflow is being served through a web frontend where users should only touch certain values.

    Inputs

    • name - the identifier the web interface uses for the field. Make it human-readable; it becomes the label.
    • value - the float that comes out. Range is enormous (Β±1e10) so this works as a raw constant too.
    • min / max - validation bounds for the web form (and the widget's slider range).
    • step - the slider increment, default 0.01.

    Output is a FLOAT. Wire it into any node that takes a float - denoise, cfg, upscale_by, strength, whatever.

    The honest take

    For the desktop ComfyUI user, this is a slightly redundant convenience node: you can get a float constant from half a dozen packs, and even the base UI handles sliders fine. Where it pulls weight is (a) template workflows that are meant to be filled in by non-technical users through a web UI, and (b) keeping a workflow self-documenting - a named input node reads better than an anonymous constant when you're sharing a graph. The pack ships a whole family of these (Int, Float, Boolean, String), so if you're building templates on this pack you get a consistent input style across all of them.

    If you just want a number in a graph and you're not sharing via a web form, skip it and use a stock constant. If you're building a template workflow someone else will run, this is the tidy choice.

    Install

    Same pack as the rest of the ArchAi3D family:

    cd ComfyUI/custom_nodes
    git clone https://github.com/amir84ferdos/ComfyUI-ArchAi3d-Qwen.git
    

    No extra dependencies - it's pure stdlib. Restart ComfyUI, find it under ArchAi3d/Inputs. Free personal use, paid commercial, like everything in the pack.

    CategoryArchAi3d/Inputs

    Inputs (5)

    NameTypeDefaultDescription
    nameSTRINGfloat_inputIdentifier name for this input (used by web interface)
    valueFLOAT0.00-10000000000–10000000000The float value to output
    minFLOAT-10000000000.00-10000000000–10000000000Minimum allowed value (for web interface validation)
    maxFLOAT10000000000.00-10000000000–10000000000Maximum allowed value (for web interface validation)
    stepFLOAT0.01000.0001–1000Step increment (for web interface slider/input)

    Outputs (1)

    NameTypeDescription
    FLOATFLOATβ€”