I recently got an “Einstar” scanner, which I would really recommend for the price (under 1000 €).
Since I need Breps for CAM toolpath generation, I’m trying to fing good reverse engineering techniques and tools.
I tried the Sub-D QuadRemesh route, but that generally gives me way too many Nurbs patches and still requires quite a bit of manual adjusting.
For now, I’m sticking with drawing guide curves, creating rough Nurbs patches manually and them using these as base surfaces for the “Patch surface” command.
Of course, I wanted to automate as much as I could, but GH seems to lack all the good stuff that would allow it :
-The GH “PullCurve” component doesn’t accept meshes as an input, contrary to the Rhino component
-The “Geodesic” component doesn’t accept meshes as input. By chance the “MeshPaths” plugin solves that.
-There is no native Point cloud support, and the plugins (Volvox, Cockroach) don’t allow point cloud baking
-The GH “Patch” component is a watered down version of the Rhino command, and it doesn’t accept starting surfaces, making it quite useless, since this generally produces wonky worthless surfaces.
I’m not him, but this is just a matter of copy-pasting the names on the component… patch.gh (9.6 KB)
Note that “fixEdges” require always 4 booleans as the documentation says:
Array of four elements. Flags to keep the edges of a starting (untrimmed) surface in
place while fitting the interior of the surface. Order of flags is left, bottom, right, top
That’s very interesting. I wonder if it can be used to place 4 points on a mesh and create a network surface that fits closely to the mesh. Hence, reverse engineering the mesh into nurbs
I also have 2 geodesics components in Nautilus plugin. One from a point and a direction and one from point to point.
And it could be access with a library.
Thanks for crafting this, I was in a but of a rush yesterday.
@osuire Flexibility.GH plugin has pretty much all standard components upgraded with all parameters available from RhinoCommon. It has a full Patch component. It also comes with a ribbon full of awful icons. Make your choice .
I suppose so, but with certain shapes, the geodesic curve can get funky / unpredictable.
Since I had already manually created my NURBS patches, I just created a definition that would project the isoparms on the mesh, and create Network surfaces from them.
Worked like a charm !
My sculptor likes his subtle sharp lines.
You know, the kind of car bodywork creases that vanish on a surface.
Moreover, I’ve heard that FUSION 360 doesn’t like meshes so much and will cause trouble with certain toolpath strategies, but to be honest, I never tried.
Many things are possible. I don’t own a CNC machine or robot but I’ve done some toolpath simulation and exported curves and lines for machining mostly wheel-wells on downhill skateboards.