intToFloat _O

ComfyUI is picky about types. A node expects a FLOAT and you're feeding it an INT, and the wire simply won't connect - ComfyUI won't auto-coerce, and the graph just refuses. intToFloat _O is the two-second converter: INT in, FLOAT out.

It's in the Quality of Life Suit's O/numbers group, and it exists because this pack's own nodes make the problem obvious. Things like GetImage_(Width&Height) _O hand you dimensions as INTs, but a scale factor or a size input on another node might want a float - or you want to feed an integer seed into a float-based math node like Equation1param _O. Slap an intToFloat in between and the graph stops complaining.

How it works

intToFloat _O takes one INT (default 0, range up to 2^64−1) and returns float(int) - a literal type conversion with no rounding, no clamping, no math. 5 becomes 5.0. There's no precision loss because integers up to 2^53 are exactly representable as floats anyway. The single input is int, the single output is FLOAT.

It's the inverse of the same pack's floatToInt _O (which truncates toward zero - worth remembering if you round-trip values and wonder where the decimals went).

Installing

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

or ComfyUI Manager → search ComfyUI-QualityOfLifeSuit_Omar92, then restart ComfyUI. No dependencies.

The honest take

This is the thinnest possible utility node - a type cast wearing a trench coat. You will not use it in every workflow, and that's fine. But the moment you hit a "cannot connect: INT vs FLOAT" error and you're staring at a graph that's otherwise perfect, you'll be glad this exists. If you're doing a lot of numeric wiring, it's the kind of node that quietly saves a dozen "how do I make this connect" moments over the life of an install.