Edgy cuts chips and cracks directly into the geometry: a shared core for Cinema 4D and Blender

Artist Cornelius Dämmrich has released Edgy, a plugin for Cinema 4D and Blender that cuts chips, dents and cracks directly into an object's geometry. The tool changes the mesh itself, so the wear reads in the silhouette at any distance from the camera and in any render engine.

The source model is left untouched. In Cinema 4D the result becomes a child object of the Edgy generator; in Blender it is written into a new object next to the original, so you can return to the clean geometry at any moment.

Six damage modules

Damage is broken down into six modules, each with its own distribution logic:

• Chips — chipping along open edges.
• Corners — larger damage at points where several open edges meet.
• Craters — shallow dents on flat surfaces, distributed by area.
• Fracture — crack networks of up to three levels.
• Buildup — the reverse operation: material is not removed but accumulates in inner corners and recesses.
• Breaker — removes whole chunks from the object.

Six ready-made setting sets are included, and you can create and reuse your own presets.

A shared core and separate materials for the damage

Edgy's geometry core does not depend on the host application: it takes a mesh and a block of parameters and returns a mesh, and there is no Cinema 4D- or Blender-related code inside it. In Blender the add-on loads the core as a compiled Python module, edgy_core_py; in Cinema 4D the same files ship as part of the commercial plugin. On the core's side are edge detection, cutter placement, boolean operations, a secondary pass, the crack module, the fracture geometry and the damage cache.

The result is cached. Each damage type is written into its own selection in Cinema 4D and into a separate face attribute with a separate material slot in Blender, so chips, cracks and buildup can be assigned different materials. Exactly where the wear appears is set by a mask: Fields in Cinema 4D and a vertex group in Blender.

The input geometry has to be closed: the tool cuts damage into the edges and surfaces of a closed mesh, and the approach is based on boolean operations.

Open source on the Blender side

The core loaded by the Blender add-on is published on GitHub under GPL-3.0-or-later: the sources are out in the open because the license requires it — every buyer who receives the compiled module also receives its source code. The author remains the sole rights holder and distributes the same files under a separate proprietary license as part of the plugin for Cinema 4D. The repository does not accept pull requests: it is regenerated from the plugin repository on every release, and dual licensing only works as long as the rights to all of the code belong to a single person. Forking, however, is allowed.

Each release corresponds to one commit and a git tag with the version number, so the source of any shipped build can be found by its tag. The compiled module is tied to a specific CPython ABI, so different binaries are built from identical source code for Blender 4.5 (CPython 3.11) and Blender 5.x (CPython 3.13). The core depends on Manifold, Clipper2 and oneTBB; build scripts for Windows and macOS are in the same repository. The Edgy page — the plugin can be downloaded there as well.

Why geometric damage has become interesting again

Edgy arrives amid noticeable interest in destruction at the geometry level rather than in shading alone. Blender has recently seen tools built on Geometry Nodes that work along similar lines — for example, the Damage Control set by Jesse Miettinen with destruction, object scattering and grime in the spirit of The Last of Us. In Cinema 4D this niche has apparently remained noticeably less filled.

Behind this there is probably a shift in the quality bar. As long as the shot is static and distant, shader wear is enough, but with camera movement and close-ups a perfectly sharp edge gives the model away. At the same time the operation itself is getting cheaper: boolean computations on closed meshes have become faster, and caching the result makes it possible to work with damage interactively.

If the trend continues, wear and damage will increasingly move out of the texturing stage back into modeling, and environment artists will get one more procedural layer that can be regenerated for a new camera angle. Most likely, small teams and solo artists will benefit — those who have neither the time for manual detailing nor a tech artist of their own to build a similar generator from scratch.