if you want to have even nicer surfaces / result build all four sided Surfaces with SrfPt or Loft between 2 line (to have untrimmed surfaces for the flowAlongSrf)
my go still would be:
find the back-face-profile / section to build it as extrusion.
build the extrusion
_unrollUV
_flowAlongSrf to get a planar representation of the curved geometry / mesh / scan data.
rebuild build the flat representation with SrfPt which will allow maximum edibility.
_flowAlongSrf to get the planar decor back to 3d / curved, do it with history enabled.
finetune the the flat version while comparing the 3d-version with 3d-“pseudo-scan” data.
if you just want to make your surfaces watertight: _join _showEdges … check what is wrong - rebuild the surfaces that can not join. … (first part of my post above)
I didn’t have a scanned mesh to hand, so im practising on a high poly mesh I had instead. I have to learn to reverse engineer from scans for work. I’m using the mesh2surface plugin for rhino.
I’m newish to rhino, but i’ve 3D modeled in mesh software like Maya blender and 3dsmax. I’ll be doing a variety of things, like for example i’m being asked to do a piece of a dashboard for a car next week. the stuff will be 3D printed so I need the gemetry to be watertight/Manifold.
My recommendation is you take time to learn modeling in Rhino, particularly if you need NURBS surfaces rather than meshes. It’s very different than mesh software like Maya blender and 3dsmax.
“Reverse engineering” a shape in Rhino from scan data is much easier with better results if you know how to build the shape in Rhino.
How closely does the Rhino model need to follow the scan? Does it need to closely follow the scan everywhere? Or are there a few critical areas where the Rhino model needs to match the scan (or other criteris) and elsewhere it needs to be “close enough”? If the Rhino model will be used to refine the shape then modeling with as few control points as possible while still meeting the requirements should be the goal.
A scanned mesh will give you a result that is very different from a meshed nurbs surface.
Typically scans must be cleaned up in advance of using any reverse engineering application. I do not know if Mesh2Surface has these tools, but presenting the issue here indicates that it does not.
Rhino has very limited ability to deal with all the problems resulting from a scanned mesh. The only meshes I have seen straight from the scanning application that are nearly perfect are from CT scans.