Range Float (VixUI)

VixUiRangeFloat is a float value wrapped in a slider, plus the metadata that turns that slider into a real control when the workflow is published to Visionatrix. In plain ComfyUI it's a pass-through - you set a float, you get that float. The payoff is on the Visionatrix side: a Visionatrix user drags a range control instead of you hardcoding a number, which is exactly the "give this flow a strength setting" use case the pack exists for.

The README's own example is prompt strength, and that's the right mental model. Put one of these on denoise, strength or a guidance input and your flow's users get a proper slider with min, max and step, rather than a text field they can break.

Inputs that matter

• value (FLOAT, default 4.0) - the current value and the only thing that actually flows out.
• display_name (default "Display Range") - the label in the Visionatrix UI. Rename it or you'll ship a control that literally says "Display Range".
• min (default 1.0) and max (default 9.0) - the slider bounds. This is where you actually design the control: a denoise slider should probably span 0.0–1.0, not 1–9.
• step (default 0.1) - slider granularity.
• optional, advanced, order (default 99), custom_id - the standard VixUI control metadata from the rest of the family.

hidden is the optional input if you want the control out of the UI.

Outputs

One FLOAT output carrying the current value. Wire it into anything that takes a float - KSampler's denoise or cfg, a LoRA loader's strength, an upscale factor.

How it works

do_it returns the value untouched. All the logic lives in the metadata: min, max and step describe the slider; optional, advanced, order and display_name describe how it's presented; Visionatrix reads all of it when it renders the flow. The node is a declaration plus a passthrough.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/Visionatrix/ComfyUI-Visionatrix

Restart ComfyUI, or install ComfyUI-Visionatrix from ComfyUI Manager. No model downloads; dependencies are the usual torch/pillow/numpy, already present.

Gotchas

The default min/max of 1.0–9.0 with a default value of 4.0 is a trap if you copy the node without thinking - you'll ship a denoise slider that can't go below 1.0 and the "off" value you wanted is unreachable. Always set min/max to the real range of the thing you're controlling before you publish. And remember the UI fields do nothing in plain ComfyUI: tune them while testing locally and nothing visibly changes, which is expected. In the Visionatrix world, this is the node you'll reach for more than any other - it's the single best way to expose a meaningful setting to non-technical users.