Mesh Rip Move

In Blender's own viewport, hitting V doesn't just rip a selection open - it rips and then hands you the new geometry to drag around with the mouse, in one continuous motion. That combined action is bpy.ops.mesh.rip_move, a macro operator that bundles Blender's rip with a follow-up translate. This node is that exact macro, exposed as a ComfyUI node inside Avatar Graph, the pack that runs real Blender (via the bpy Python package) inside ComfyUI's process to build interactive 2D-to-3D avatars, auto-generating a node for every mesh operator Blender has.

How it works - and the catch worth knowing

It rips the selected geometry away from its neighbors exactly like Mesh Rip does. The difference is the second half of the macro: in Blender's UI, that's an interactive drag where you physically move the mouse to place the ripped geometry. There's no mouse in a ComfyUI graph. Called this way, headlessly, the translate step has nothing to drive it - so in practice this node performs the rip and effectively skips the interactive move, landing you in roughly the same place as the plain Mesh Rip node. If you need the ripped geometry to actually move somewhere specific afterward, do that with an explicit transform elsewhere in your graph rather than expecting this node's name to imply a move happens automatically.

Inputs and outputs

• BPY_OBJ - the mesh coming in, with the geometry to rip already selected. That's the only field exposed on this node - none of the proportional-editing or fill options that the bare Mesh Rip node carries are here, because this is the macro version and those live on the sub-operator, not surfaced independently.

Output is a single BPY_OBJ - the same object, ripped, ready for the next step in your chain.

Installing it

ComfyUI Manager: search "avatar-graph-comfyui", install, restart. Manually: cd ComfyUI/custom_nodes && git clone https://github.com/avatechai/avatar-graph-comfyui, then cd avatar-graph-comfyui && python -m pip install -r requirements.txt, then restart ComfyUI.

Get Python 3.10.x sorted before anything else - that's what the bpy package this pack runs on requires, and the README steers macOS/Linux installs toward a dedicated conda environment (conda create --name comfyui python=3.10) rather than trusting an existing setup. Windows users get a prebuilt ComfyUI + Python 3.10 zip linked in the README, unzipped over an existing install, followed by adding the pack through Manager. Restart with --enable-cors-header (macOS also needs --force-fp16) for the live 3D preview to work with Avatech's web viewer - skip it and the graph still runs, you just save the mesh out manually from the pack's Avatar Main Output node instead.

Common issues

If this pack's nodes aren't loading, check the Python version first - 3.10.x is non-negotiable for bpy to have a working build. On this node specifically, the recurring point of confusion is expecting "Move" in the name to mean something actually moves: since there's no interactive drag available in a headless graph, don't rely on this node to reposition anything - treat it as a rip, and handle any actual displacement with a separate transform step. If you specifically want more control over the rip itself (fill behavior, proportional falloff, mirroring), reach for the plain Mesh Rip node instead, since it exposes those options directly and this macro version doesn't. As with the rest of this pack's mesh tools, feeding it anything other than a real mesh BPY_OBJ from earlier in the same graph will surface as a Blender-side error rather than a clean failure - these nodes are built to chain, not run in isolation.