Chamfer

Status: Implemented

Chamfer bevels the selected edges of a single solid. Three bevel shapes are available, chosen by which parameters you set.

Walkthrough

Inputs

• id – a string, default null.
• edges – a multiple reference_selection filtered to EDGE and FACE, default null. Select edges directly, or pick faces to gather their shared edges.
• distance – a number, default 1. With distance2 and angle both at 0 the bevel is symmetric, and distance is the rolling-ball radius: the kernel runs the Fillet construction at radius distance and keeps the chord of the arc instead of the arc, so the bevel joins the two points a ball of that radius touches. On a 90° edge between two planes those tangency points sit exactly distance along each face — the familiar setback — but on curved faces they do not: a distance of 1 across the crease between two unequal spheres sets back 1.186 along each one. Use distance2 or angle when you need an explicit per-face setback.
• distance2 – a number: optional second setback for an asymmetric (two-distance) bevel, measured along the second face. 0 (default) means symmetric; when it is greater than zero the edge gets a lopsided distance × distance2 bevel.
• angle – a number: optional distance-angle bevel. The angle in degrees between the chamfer face and the first face. 0 (default) means unused, and it is ignored when distance2 > 0.
• direction – an options value: AUTO (default) or INSET.

Behaviour

• The shape is picked in this order: distance2 > 0 gives the asymmetric bevel; otherwise angle > 0 gives the distance-angle bevel; otherwise the symmetric bevel runs.
• The result reuses the target solid's name: the target is removed and the bevelled body is added under the same name.
• Each generated bevel face is named after the edge it grew from, {id}:BLEND:{edgeName} — the same naming helper Fillet uses, including its F fallback prefix when the feature has no id. Pre-existing names propagate through the kernel.

Limitations

• direction accepts only AUTO and INSET. Any other value — OUTSET included — fails with direction '…' belonged to the removed legacy mesh pipeline. OUTSET never had a kernel-exact path, so an old saved file that used it errors loudly rather than building different geometry.
• A selection spanning more than one solid is a hard error (chamfer requires the selected edges to belong to a single solid). Note this differs from Fillet, where a cross-solid selection is a quiet no-op.
• A non-positive or non-finite distance is a quiet no-op.
• The asymmetric bevel is built for straight edges on planar faces; other configurations may be refused.
• Edge names that do not resolve are recorded as unresolved; if nothing resolves the feature does nothing.

Where to find it

Offered in the Modeling and All workbenches. Type code CH. The context bar offers it when faces or edges are selected.