Log (VEC2)

Vector types are ComfyUI's newer addition to the primitive family - a single VEC2 wire carrying a pair of numbers (an x,y offset, a 2D position, a translation) - and the catch is they're invisible on the wire. A VEC2 doesn't show you its contents until you do something with it. Log (VEC2) (LogVec2) prints the pair to the console as it passes through, so you can see what you're actually feeding into that camera-motion or positioning node.

How it works

Standard RF Nodes Log recipe: LogToConsole(prefix, value) writes a cyan line to the terminal running ComfyUI, then the node returns the value unchanged. It's a passthrough, so you drop it onto a VEC2 wire, observe, and let the graph continue exactly as before.

The inputs that matter

• value - a VEC2, forceInput, so it must be wired from a node that outputs a 2D vector.
• prefix - the label before the value (default Value:).

Output: VEC2 - the same vector, unchanged.

When you'd use it

Any workflow that moves, offsets, or positions things - camera motion, pan/tilt, translation offsets - carries VEC2 values between nodes, and those values are exactly the kind that get computed, scaled, or clamped upstream and then silently surprise you. Log the vector at the point of use and the console tells you the effective offset, not the one you think you configured. There's no number formatting to argue with here: vectors print as their component values, which is what you want for debugging.

Installing RF Nodes

No dependencies, no models. Via ComfyUI Manager search "RF Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/foxtrot-roger/comfyui-rf-nodes

Restart ComfyUI; it's under RF in the menu.

Common issues

• "I don't see any VEC2 sockets to wire." - Then your workflow doesn't use vectors, and you don't need this node yet. It's for camera/motion/3D-flavored graphs.
• "The log isn't appearing." - Console, not browser. Launch ComfyUI from a terminal to see the output.