Object Transform Axis Target

I'll save you the hour I spent: Object Transform Axis Target is an auto-generated wrapper around bpy.ops.object.transform_axis_target(), which is an interactive Blender operator - the gizmo that moves an object along a chosen axis when you drag it in the 3D viewport. It's not a processing step. It doesn't compute anything. It waits for a live mouse and a live viewport context.

In a ComfyUI graph you have neither. When you queue the workflow, this operator runs with no gizmo, no pointer, and nothing to respond to, so it does nothing and passes your BPY_OBJ through unchanged. It isn't broken - it's the wrong tool for the medium.

The Avatar Graph pack generates its hundreds of Object_* nodes straight from Blender's operator registry, and interactive gizmo operators like this one and Object Transform To Mouse are the ones that expose the registry's overreach: Blender ships them because the UI needs them, the generator sees "an operator," and now there's a node for something that only makes sense with a human dragging in a viewport.

There's exactly one input, BPY_OBJ, and one output, the same object passed through. Nothing to tune, nothing to wire around it. The only legitimate use I can imagine is as a no-op passthrough while you're laying out a graph, and even then a Reroute node does that with less confusion.

Install is identical to every other node in the pack: ComfyUI Manager → "Avatar Graph", or git clone https://github.com/avatechai/avatar-graph-comfyui into ComfyUI/custom_nodes, pip install -r requirements.txt on Python 3.10 (bpy==3.6.0). Expect the usual first-launch downloads - the ~2.4 GB SAM model and mediapipe landmarkers.

Troubleshooting here is really "should you troubleshoot at all": if this node is in a workflow and you're expecting movement, remove it - it will never move anything in a queued run. The same logic applies to its siblings that wrap interactive gizmo ops. When you see an Object_* node whose inputs are only BPY_OBJ and maybe some session_uuid/drop_x/drop_y plumbing, treat it as suspicious. A real processing node in this pack has actual parameters. This one is Blender's UI bleeding into your graph, and it's safe to ignore.