Object Transfer Mode

Let's be straight about this one: Object Transfer Mode is the pack's auto-generated wrapper for bpy.ops.object.transfer_mode(), a Blender operator whose job is to copy the viewport display mode (wireframe, solid, textured, that sort of thing) from the active object to every selected object. It's a workflow nicety for when you're working in the 3D viewport and want a whole scene to switch to the same display style at once.

In a ComfyUI graph, that use case mostly evaporates. There's no viewport in front of the user, and - more importantly - the node's own base class deselects every object except your BPY_OBJ before running, while transfer_mode copies from the active object to the selected ones. On a bare graph with one object on the wire, there are no recipients. So this is one of the pack's registry leftovers: real, functional inside Blender, and nearly useless as a graph node.

What it takes, for the record: BPY_OBJ is the active object whose display mode gets copied, and use_flash_on_transfer (default true) flashes the viewport to signal the change - a Blender UI flourish that does nothing when there's no viewport to flash. The output is your BPY_OBJ passed straight through.

Honestly, the most useful thing to know about this node is when not to use it. These object-operator wrappers are auto-generated in bulk from Blender's operator registry, and the pack ships hundreds of them whether or not they make sense in a graph. This one, along with the interactive gizmo wrappers (Object Transform Axis Target, Object Transform To Mouse), is a "skip it" candidate. If you genuinely want to switch display modes on meshes, it does no harm in the chain - it just won't do what you might hope.

Install is the same as every node in the Avatar Graph 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). First launch downloads the ~2.4 GB SAM model, so budget for a slow start.

If you wired it in and "nothing happened," that's the design, not a fault - the op needs other selected objects in the Blender scene and the node deliberately clears selection before it runs. Leave it unconnected, or use it only in a scene where you've already arranged a multi-object selection. And as with everything here: the scene resets at the start of each run, so any selection you made last time is gone.