Log (VEC3)

Camera and 3D-flavored workflows speak in VEC3 - a single wire carrying three numbers (an x,y,z position or motion vector) - and nothing on that wire tells you what's inside it until some node consumes it. Log (VEC3) (LogVec3) prints the triple to the console and passes it through, so when your camera drift looks wrong you can check the actual vector feeding the motion node instead of re-running and squinting at the result.

How it works

Same Log family recipe as the rest of RF Nodes: LogToConsole(prefix, value) prints a cyan line to the terminal running ComfyUI, and the node returns the value unchanged. Passthrough, so the graph behaves exactly as if the node weren't there - it just reports.

The inputs that matter

• value - a VEC3, forceInput, so it must be wired from a node that outputs a 3D vector.
• prefix - the label before the value (default Value:). cam_move:, offset: - whatever identifies the line.

Output: VEC3 - the same vector, unchanged.

When you'd use it

Camera motion, positional offsets, and 3D transforms - the workflows where a VEC3 gets built, scaled, or clamped somewhere upstream and then drives a motion node. Logging right before the consumer shows you the effective vector: is the z-component really what you set, or did an upstream math node quietly zero it? That's the difference between a two-minute fix and a ten-minute hunt.

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

• "This looks identical to LogVec2." - Functionally, yes; the input type differs (3 components vs 2). Grab the one matching your wire's type - ComfyUI won't let you plug a VEC3 into a VEC2 socket.
• "No log output." - The console is where it goes, not the browser. Run ComfyUI from a terminal if you want to see it.