Mesh Rip Edge

If you've done any mesh editing in Blender, "Rip" is a familiar tool - the V-key command that tears geometry apart along an edge instead of just deleting or moving it. Mesh Rip Edge is that operator, exposed as a ComfyUI node inside Avatar Graph, Avatech's pack for rigging static character art into real-time avatars.

Specifically, this wraps bpy.ops.mesh.rip_edge - the edge-based variant of Blender's rip tool, which splits the mesh along a run of selected edges so the geometry on either side becomes disconnected rather than sharing vertices. (Blender also has a plain vertex-based Rip; this is the edge version, which is the one you want when you're separating a strip or a boundary rather than a single point.) Avatar Graph wraps bpy directly inside ComfyUI, so this node's parameters mirror the real Blender operator one-to-one.

Where this actually gets used in an avatar-rigging context: when you're building mesh layers from segmented character art - an eye, a mouth, a piece of clothing - you sometimes need to deliberately break a seam so a part can move or deform independently from its neighbor, rather than staying welded together. Ripping an edge is how you create that separation without deleting geometry.

Like Transform Resize (another node in this pack), Mesh Rip Edge carries a large parameter list because the operator implicitly includes a move step after the rip - in Blender's interactive viewport, ripping and then dragging the torn edge away is one fluid motion. In a scripted ComfyUI graph, most of that interactive baggage doesn't matter:

• mirror - mirrors the rip operation across a symmetry axis, if your mesh has one set up. Leave off unless you know you need it.
• use_proportional_edit, proportional_edit_falloff, proportional_size, use_proportional_connected, use_proportional_projected - these control softening the effect across nearby geometry, same as any Blender transform tool. Not usually relevant to a clean rip; leave at defaults.
• release_confirm, use_accurate - leftover interactive-mode settings from the viewport tool. No effect in a headless graph run.

Output is the same BPY_OBJ, now with the rip applied.

Installing it: there's no way to install this node on its own - it comes bundled with the entire Avatar Graph pack. Easiest is ComfyUI Manager, searching "Avatar Graph" or avatar-graph-comfyui. Manual: cd ComfyUI/custom_nodes, git clone https://github.com/avatechai/avatar-graph-comfyui, cd in, pip install -r requirements.txt, restart.

The install issue that actually breaks people's setups: Avatar Graph needs Python 3.10.x, exactly, because its bpy dependency - Blender's API packaged as a standalone library - only ships wheels for that version. On a newer Python (which is what most fresh ComfyUI installs run today), the install fails outright rather than degrading gracefully. The README's recommendation is a dedicated environment: conda create --name comfyui python=3.10, then activate and install ComfyUI's requirements before this pack's. If you want the live preview in Avatech's own web editor, launch with --enable-cors-header (Mac adds --force-fp16); skip it and everything still computes correctly, you just export .glb/.gltf and check your work in Blender instead of seeing it update live.

Since rip operations depend entirely on what's selected when the node fires, the most common "why didn't anything happen" moment is an empty selection upstream - same story as most of this pack's edit-mode nodes.