UV Rip Move

Let's be straight with you: UV Rip Move is the node in this pack that makes the least sense as a node. In Blender it's the "rip and move" tool - you click on a UV edge, tear it open, and drag the resulting pieces apart, all in one mouse gesture. The whole operator is built around that interactive drag, and this auto-generated version exposes it with a single BPY_OBJ input and nothing else. There's no move vector, no location, no gesture to feed it. If you were hoping for a controllable "split here and shift by this much" node, this isn't it.

How it works

It wraps bpy.ops.uv.rip_move on your BPY_OBJ, same as the other UV_* nodes: edit mode, operator call, object returned. That's the entire node - one input, one output. What happens in practice is it invokes the operator with all-default parameters, which in an automated graph means the operator's internal "move" state is empty. You can chain it and it will pass your object through, but the meaningful work (the rip) is better done with UV Rip, which at least takes a location you can set.

Where it fits

Honestly: it mostly doesn't, for graph-based work. If you want to split UVs in a workflow, reach for UV Rip - it takes a real location input and produces the split you can actually control. If you want to move islands afterward, use a transform node or re-pack. Consider Rip Move a leftover from the pack's approach of auto-generating every Blender operator whether or not it makes sense as a node - some of them are genuinely useful (Pack Islands, Follow Active Quads, Mark Seam), and some of them are interactive tools that don't survive the translation. This is the latter. Knowing which is which saves you an afternoon.

Installing Avatar Graph

This node ships in the Avatar Graph pack from Avatech. From ComfyUI/custom_nodes:

git clone https://github.com/avatechai/avatar-graph-comfyui
cd avatar-graph-comfyui
python -m pip install -r requirements.txt

then restart ComfyUI with --enable-cors-header. Or ComfyUI Manager → search Avatar Graph → Install.

Standard pack warnings: it pins bpy==3.6.0, which needs Python 3.10.x or the pip install fails entirely. First launch downloads the ~2.5 GB SAM model, which looks like a freeze. And the pack is explicitly still changing - pin the version once your workflow is stable.