Hi Jorgen - I see that - for now, run testConvexHull on the points, and then MeshPatch with that included in the input. @tim, it seems to me you once explained me why points can be left out in MeshPatch - if I am not making that up, can you remind me? it probably made some sense at the time but I cannot remember what you told me…
Hmmm - not that I know of… it really does not come up very often I guess, Having it in RhinoCommon would be a good thing. All that said, there are comments from the developer, in the code, about how slow this function is, and indeed to bogs down pretty quickly if you give it even a couple of thousand points, so I guess it is really not very ready for prime time.
OK, there already is a convex hull component in GH, and as GH is based in RhinoCommon, I thought… But I guess there are other things also missing in RhinoCommon that are in GH like Delaunay, etc…
BTW feeding 10K points to the GH Convex Hull gets a result instantly. Maybe the developer in question should talk to David…
Indeed… I think testConvexHull is ancient history and really is a test thing for some other (not top level Rhino) purpose. I’ll dig into this a little more and see what we can come up with.
I had no idea V5sr12 coudln’t open a V5sr13 file, that seems like a bug to me as I didn’t know that sr13 added any new geometry to the file that sr12 couldn’t read.
But thanks for showing the GH component.
Hi Jorgen - Tim is revising how the outer boundary is computed - it will not need testConvexHull - you can fix it yourself, in a way, by running the dash version of MeshPatch (I know, I know) and setting MainSegmentCount to 1 instead of 10.
Ah, yeah, I played with the -meshpatch settings but didn’t get a good result, I thought I adjusted MainSegments too, probably didn’t try 1. Thanks for looking into it!