BreakoutVec4

BreakoutVec4 rounds out ComfyMath's vector-unpacking trio: it takes a VEC4 - four related numbers bundled onto one wire, x/y/z/w or R/G/B/A or a bounding box's four corners, whatever you packed together - and splits it into four independent FLOAT outputs. Like its Vec2/Vec3 siblings, this exists so a group of related values can travel as a single connection instead of four separate wires crossing your graph, and this is the node that unbundles them again once each value needs to feed a different destination.

How it works

Feed a (VEC4, default [0, 0, 0, 0]) in, get four FLOAT outputs back, in the vector's original order.

The inputs and outputs that matter

• a - the VEC4 to split.
• Outputs - four FLOAT values, in order. Wire each to wherever that specific component needs to go.

Installing it

Search ComfyMath in ComfyUI Manager, or:

cd ComfyUI/custom_nodes && git clone https://github.com/evanspearman/ComfyMath

then restart ComfyUI. No pip dependencies beyond ComfyUI's own, nothing to download.

Common issues

The same rule applies here as the rest of ComfyMath's vector nodes: VEC4 is a type this pack defines for itself, and it isn't something ComfyUI's core nodes or most other custom packs speak natively. That means the VEC4 arriving at this node's input almost always came from ComposeVec4 or another ComfyMath vector node earlier in the same graph. Don't go looking for a way to feed a bounding box or RGBA value from an unrelated pack straight into this unless you've confirmed that pack's output is actually typed VEC4 - most aren't, and you'd build the vector yourself with ComposeVec4 first.

With four unlabeled outputs instead of two, order mixups are the easiest mistake to make here specifically. If you're not certain which output maps to which meaning (x vs. y vs. z vs. w, or whichever four values you're actually representing), trace back to the ComposeVec4 node that built it and match the input order there - a float doesn't carry any hint of which "slot" it was.

This is one of the quietest corners of an already small pack - the vector nodes get essentially no discussion in the community, and ComfyMath as a whole hasn't seen active maintenance since roughly early 2024. There's very little complexity for anything to break here (a four-way unpack with no external dependencies), but correspondingly little community troubleshooting to reference if you do run into something unexpected.