Mesh Customdata Bevel Weight Edge Add

This node has no configurable parameters at all - the schema is just the mesh object in, the mesh object out - and that's not a stripped-down summary, it's genuinely the whole thing. It wraps Blender's bpy.ops.mesh.customdata_bevel_weight_edge_add operator exactly as-is, part of Avatar Graph's larger practice of auto-generating a ComfyUI node per Blender mesh operator rather than hand-writing wrappers.

What it actually does

Blender doesn't allocate a per-edge "bevel weight" data layer on a mesh by default - it's optional custom data, only created when something asks for it. This operator is that ask: it adds the bevel-weight layer to the mesh, initialized to zero on every edge. On its own, running this produces no visible change whatsoever - you won't see a different shape, no geometry moves. What it does is make it possible for something downstream (a per-edge weighted bevel, a Bevel modifier set to use edge weights instead of a flat amount) to actually read and use per-edge weight values, because the storage for those values now exists on the mesh.

The input and output

• BPY_OBJ (optional) - the mesh object to add the layer to.

Output is the same BPY_OBJ, unchanged in shape, passed through so you can chain whatever actually sets or uses those weights next.

How to install it

Via ComfyUI Manager: search "Avatar Graph" (avatar-graph-comfyui), install, restart. Manually:

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

The pack's hard blocker: bpy==3.6.0 is pinned in requirements.txt and only builds on Python 3.10.x. Windows users get a bundled Python 3.10 ComfyUI zip from the README; Mac/Linux users should build a dedicated conda environment (conda create --name comfyui python=3.10) rather than fighting an existing 3.11/3.12 setup. Expect a heavier install overall - segment-anything, mediapipe, and OpenCV all come along.

Common issues & troubleshooting

"It doesn't seem to do anything." That's expected - this is a prerequisite/setup step, not something with a visible effect by itself. If you're expecting to see a bevel appear, you're looking for a different node; this one only makes per-edge weighting possible for whatever comes after it.

Running it twice, or on a mesh that already has the layer. Blender's add operator is safe to call on a mesh that already has the layer - it won't duplicate or error, it just leaves the existing data alone. Not something you need to guard against in your graph.

Weights aren't taking effect downstream. If a weighted bevel or modifier still isn't respecting per-edge weights after this node runs, the actual weight values still need to be set somewhere (this node only creates the empty layer, initialized to zero) - check what's supposed to be writing non-zero weights into it.