Mesh Customdata Skin Clear

The teardown side of Mesh_CustomdataSkinAdd. Wraps Blender's bpy.ops.mesh.customdata_skin_clear operator directly - one BPY_OBJ in, the same one out, no other fields.

What it actually does

Blender's Skin Modifier reads a per-vertex radius layer to decide how thick each point of a skeleton-style mesh should inflate to. This node removes that layer entirely. If a Skin Modifier is still attached to the object after this runs, it has nothing to read and effectively has no per-vertex thickness data to work with - any custom radii you'd painted or set are gone, not reset to a default.

You'd use this to genuinely undo skin-vertex setup, most likely because you're switching a piece of geometry away from the skin-modifier workflow toward something else, or because an earlier step in a generated pipeline added the layer speculatively and it's not being used.

The input and output that matter

• BPY_OBJ (optional) - the mesh to remove the skin vertex-radius layer from.

Output is the same BPY_OBJ, minus that data layer if present.

How to install it

Search Avatar Graph in ComfyUI Manager, or clone manually:

cd 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. Everything here depends on bpy==3.6.0, which requires Python 3.10.x - the README's prebuilt Python-3.10 zip covers Windows, a dedicated conda environment covers Mac/Linux. opencv-python, mediapipe, and segment-anything also install, unpinned.

Common issues & troubleshooting

A Skin Modifier still attached to the object stops working sensibly after this runs. That's expected - the modifier depends on the per-vertex radius data this node just deleted. If you still want skin-based inflation, either don't clear the layer, or re-add it with Mesh_CustomdataSkinAdd and set radii again afterward; clearing and expecting the modifier to keep working off old values won't hold.

Nothing visibly changes after running this. If there was no Skin Modifier reading the layer, or the layer was never added in the first place, this is a quiet no-op - nothing to see either way.

Unsure whether your graph even uses skin data. Most Avatar Graph workflows built off the README's templates (segment → mesh layer → unwrap → shape keys) never touch skin vertex data at all - this node, like its Add counterpart, is here because the pack wraps a broad slice of Blender's mesh operators, not because it's part of the documented rigging path.

bpy import errors at startup. That's the pack's Python-version pin, not this node - verify 3.10.x first.