Chamfered 26.6 Build 1 | Chamfered.app

Aug 18, 2026

Chamfered (26.6 Build 1)

Repeat Pattern is here. Any solid in the Builder can now be turned into a Linear row, a Radial ring, or a Grid array straight from its own parameters — no more placing and nudging copies one at a time by hand.
- Linear walks copies out in a straight line along whichever axis you choose, spaced however far apart you like.
- Radial arranges copies evenly around a full circle — think a ring of bolt holes, or a wheel of spokes.
- Grid spreads copies across independent Columns and Rows in the plane perpendicular to your chosen axis, for laying out a whole field of shapes at once.
- Skew adds a progressive lean to any of the three, and it’s worth just playing with: on a Linear row it turns into a staircase, on a Radial ring it turns into a spring/helix, and on a Grid it turns into a terraced ramp. Small values already produce dramatic results.
- A pattern still respects the solid’s own Add/Cut/Intersect setting as one unit — a Radial ring of cutters cuts all at once, exactly like a single shape would.
- Count (for Linear/Radial) and Columns/Rows (for Grid) automatically grey out whichever pair doesn’t apply to the Type you’ve picked, so there’s never a mismatch between what you’re editing and what’s actually governing the pattern.
- Selecting a patterned solid now shows a small star marking the one copy the whole pattern was generated from, so a crowd of identical shapes doesn’t read as one anonymous blob in the viewport.

Trackpad panning in the Builder viewport now moves the way your fingers expect. It previously moved the camera in the direction you swiped, which made the model visually slide the opposite way — backwards from how every other trackpad gesture on macOS behaves (Maps, Preview, Finder, and friends all move content with your fingers). Two-finger panning now matches that: swipe right, the model follows your fingers right.

Editing certain parameters in the Inspector could silently appear to do nothing, inconsistently. A rare data mix-up could leave two copies of the same setting sitting on one element, and Chamfered would sometimes read the wrong one — the edit was real, it just wasn’t the one taking effect. This is now structurally impossible going forward, and any project carrying an existing mix-up quietly cleans itself up the next time it’s opened.