BreakoutVec3

BreakoutVec3 is BreakoutVec2's three-value sibling: it takes a single VEC3 socket - three related numbers traveling together on one wire, x/y/z or R/G/B or whatever triple you bundled - and splits it into three independent FLOAT outputs. ComfyMath's VEC2/VEC3/VEC4 types exist so a group of related values can move through the graph as one connection instead of three separate ones cluttering the canvas; this is where you unbundle that group once each value actually needs to go somewhere different downstream.

How it works

Feed a (VEC3, default [0, 0, 0]) in, get three FLOAT outputs back - the vector's components, in order.

The inputs and outputs that matter

• a - the VEC3 to split.
• Outputs - three FLOAT values, in the vector's original order. Wire each to whatever needs that individual component.

Installing it

ComfyUI Manager: search ComfyMath, install, restart. Manually:

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

then restart. Pure Python, no extra dependencies, no models to download.

Common issues

Same caveat as the rest of ComfyMath's vector family: VEC3 is a type this pack defines itself, not something ComfyUI or most other custom node packs natively produce or consume. In practice that means the VEC3 you're feeding this almost always came from ComposeVec3 or another ComfyMath vector node earlier in the same graph - it's not a general-purpose way to break apart a "3D point" or color value coming from some unrelated pack, unless that pack specifically adopted ComfyMath's VEC3 type (uncommon).

The outputs aren't individually labeled beyond their order, so if you're not sure which component is which, trace back to wherever the VEC3 was built (usually a ComposeVec3's x/y/z inputs) rather than guessing - getting the order backwards is an easy, silent mistake since a float is a float regardless of which "slot" it came from.

This is a low-traffic corner of an already quiet, small pack - the vector nodes see essentially no discussion anywhere in the community, and ComfyMath overall hasn't had active maintenance since roughly early 2024. There's very little here that could actually break (it's a simple unpacking operation with no external dependencies), but also little to lean on if something does go wrong beyond checking your own wiring carefully.

A quick sanity check that's worth doing once: if two of your three outputs look identical after a run, it's almost always because the VEC3 upstream was actually built from the same value repeated (a ComposeVec3 call with the same widget wired into two of its three inputs by mistake), not because this node is duplicating anything - it only ever reads and forwards what it's handed.