MeshMeshAccurate outputs additional tiny segment

[piac (Giulio Piacentino)]

Hi Emil,

@emilpoulsen

I get an extra tiny line segment when intersecting two meshes against each other using the MeshMeshAccurate method

thanks for the input. I created report RH-57805.

This is nonetheless partially expected. The tolerance value is too high, and that creates enormous pressure on the intersector to try join tiny gaps, thereby actually sometimes by mistake “repeating” them. This is an issue that is counteracted with several strategies, but not all of them are active in the old MeshMeshAccurate call. I’ll try to enable them also there this week. That being said, the new documentation has more information about tolerance. Please see it in the docs. This means that double tolerance = 0.001; is too big.

I’ll look into what exactly happens in this case as soon as I am around that area of code.

@emilpoulsen

what is causing the split? I would expect a polyline with 2 segments

This is explained more in detail in this topic, part 3. The new _MeshSplit is based on top of the new _MeshIntersect intersector.

The new code for MeshSplit

Part of a series on mesh intersection code improvements. Other Mesh Intersection Milestones… Hi all, the new Rhino 7 WIP contains a rewrite of the _MeshSplit command: fun stuff I’ve been working on for several months after the _MeshIntersect and _MeshSelfIntersect commands, which have also been slowly improving in parallel. Here a few comparison of know problematic cases for the old mesh splitter. The new one seems to be faring better for these cases. 1. Pay respect to tiny gaps [image] …