Range Int (VixUI)

VixUiRangeInt is the integer sibling of VixUiRangeFloat: a whole-number slider that becomes a proper integer control when the workflow is published as a Visionatrix flow. In plain ComfyUI it's a pass-through that emits whatever integer you set. In a Visionatrix flow, the same node renders as a number slider a non-technical user can drag - think "steps" or "number of images."

If you're building flows for the Visionatrix simplified UI, this is your steps control. The README literally calls out "number of steps selection" as the use case, and honestly it's the one the defaults are tuned for.

Inputs that matter

• value (INT, default 10) - the current value; the only thing that flows downstream.
• display_name (default "Display Range") - the label shown in the Visionatrix UI. Change it to "Steps", or your published flow will label the control "Display Range".
• min (default 1) and max (default 20) - slider bounds. These defaults actually suit a steps slider reasonably well, which is refreshing for this pack.
• step (default 1) - granularity. Bump it to 5 if you want a coarser sweep.
• optional, advanced, order (default 99), custom_id - the standard VixUI metadata family.

hidden is the sole optional input.

Outputs

One INT output with the current value. Wire it into KSampler's steps, a batch count, or any other whole-number input.

How it works

Identical pattern to the rest of the VixUI family: do_it returns the value unchanged, and the min/max/step/display metadata is what Visionatrix consumes to draw the slider. Nothing is computed; everything is declared.

Install

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

Restart ComfyUI, or grab ComfyUI-Visionatrix from ComfyUI Manager. No models to download; deps are the stock torch/pillow/numpy.

Gotchas

The common mistake is treating this like a generic number box and ignoring the range. If you ship a flow where the only way to reach 30 steps is for nobody to touch the slider, you've broken the control - set max to what you're actually willing to let people use. Second, it's an INT, not a FLOAT: if your downstream node wants a float, most ComfyUI nodes convert, but a strictly-typed input may need the float variant instead. And as with every VixUI node, the display metadata only does something inside Visionatrix - don't expect local UI changes while you test.