Z3 Development

Here's a simple test case... ``` let geom2D = circle({radius: 10, segments: 8}) let geom3D = extrudeLinear({ height: 30, twistAngle: Math.PI / 8, twistSteps: 5 }, geom2D) ``` Even this...

OK. Continuing on... In most cases, these small differences don't matter. The produced shape will be useable in other operations, even the boolean operations. So, when does 100% accuracy matter?...

Here's my first attempt at a snap function. ``` const { vec3 } = require('@jscad/modeling').maths const { poly3, geom3 } = require('@jscad/modeling').geometries const EPS = 0.0000001 const snapVec3 = (v3)...

@gilboonet please try adjusting the EPS. Also, there’s a new function called measureEPS() which will provide a value based on the dimensions of the shape.

@gilboonet and @MathieuLoutre thanks for the feedback. this is helping to find out the issues. OK. Snapping is definitely going to help help bring vertices together. But it there's nothing...

@gilboonet do you know if meshlab has the ability to correct t-junctions in STL files?

@gilboonet thanks. i'll port fixTjunctions() and try with this example. Also, I will try to add snapping to this function as well.

@bitbybit-dev thanks for looking at this. retessellate.j is part of the booleans, and is called after each of the boolean operations. It’s a totally different algorithm to merge small polygons...

@MathieuLoutre @gilboonet @bitbybit-dev There are some changes as part of a new pull request #743 which address this issue (and more). If you have a local copy of V2 then...

Before:  After: `generalize({snap: true, triangulate: true, repair: true}, geom3D)`