Mesh export: the faces of an edge share its points exactly (#1753)
Thanks @SychPL.
This commit is contained in:
1 parent
a8a3cea1d0
commit
74ce904142
3 files changed
+130
-1
No files matched your search
Vendored
+9
@@ -154,6 +154,15 @@ Changes:
|
||||
p11`, across that plane, at the middle). A bilinear patch equals the blend of its corners the
|
||||
division compared against, so a twisted ruled face (a loft between polylines) went out as two
|
||||
triangles per face (#1666); a flat cell such as a cone's trapezoid between rulings is not split.
|
||||
- `tessellation/triangulation.rs`: a shell's face meshes share their edges' points exactly. A
|
||||
face's mesh puts each point at its parameters on the face's own surface, so a point of an edge
|
||||
that lies off a surface within tolerance (an intersection-curve sample whose projection did not
|
||||
converge, an imported edge) came out in a different place on each of the edge's faces, and the
|
||||
exported mesh had a crack there. In display and export meshes (`Deflection::rulings`), a
|
||||
vertex at a point of a face's boundary loops that is farther than `TOLERANCE` from the nearest
|
||||
point of the face's edges now goes to that point, when it is within the chord tolerance
|
||||
(`onto_edges`). Points within `TOLERANCE` stay on the surface, so exact geometry meshes as
|
||||
before. The meshes Boolean operations intersect keep truck's points.
|
||||
|
||||
## matext4cgmath 0.1.0 (Apache-2.0, © RICOS Co. Ltd., https://github.com/ricosjp/matext4cgmath)
|
||||
|
||||
|
||||
Reference in new issue
Block a user