Everything on this page runs in your browser. The geometry kernel, the diff, and the merge are the same algorithms as the command line tool, ported to JavaScript. Nothing is uploaded and nothing is precomputed.
Drag to orbit, scroll to zoom, shift and drag to pan.
Working copy
at revision 1Parameters
Features
Turn one off to see what it was holding up.
What kerf sees
no changeRewrite an equation and the part rebuilds.
The equations
A dimension in CAD is rarely a number. It is a rule such as bolt_d/2, and that rule is the design intent somebody wrote down. Edit any of these and the part rebuilds. Point one at a name that does not exist and kerf says so, the way a rebuild error would.
Drive it and see where it breaks
Every guide to parametric CAD says to move each variable across its range and check the model still rebuilds, because equations that work at the nominal value often fail at the extremes. Here that runs in a few milliseconds. Hover a bar to see the part at that value.
The merged part is drawn from the tree kerf produced, not from either branch.
Two people, one part
Both branches start from the same bracket. Pick what each person did, then merge. Kerf works feature by feature, so edits to different features combine. After that it evaluates the result and checks whether the two sets of changes occupy the same space.
Merge result
not runPick two branches and press merge.
The same solid, exported twice. Nothing about the shape changed.
Open the file, save it again
Every CAD system writes a different byte stream each time it exports. Facet order moves, the header carries a new timestamp, and floats wobble in the last digit. This page exports the part twice and then measures the result rather than describing it.
The first button writes the file the way the same exporter would on a second run. The second adds the float noise a different toolchain leaves behind. The third changes the part.
Two answers
waitingPress export to write the file a second time.