I’m really stuck with a complex invalid mesh (see below for Rhino Mesh Check details), which I need to be able to work with for 3D printing. I tried everything I know to do in Rhino to fix the mesh and edges.
Here is what is wrong with this mesh: Mesh has 12 non manifold edges. Mesh has 1 duplicate face. Skipping face direction check because of positive non manifold edge count.
Important things to consider with this mesh: Mesh has 4915 normals that are not unit vectors, 4915 of which have zero length. Although this does not necessarily mean that the mesh is bad, these normals can cause problems if the ultimate goal is for rendering purposes. Mesh has 5875 faces where the face normal differs substantially from the vertex normals. Although this does not necessarily mean that the mesh is bad, these normals can cause problems if the ultimate goal is for rendering or boolean purposes. Mesh has 36 pairs of faces that intersect each other. Although this does not necessarily mean that the mesh is bad, it can cause problems if you’re doing mesh boolean operations with it."
Who knows what would be the best way to use to Grasshopper to get a workable mesh from this?
It’s easy to remove duplicate faces, it is not easy to get rid of non-manifold edges. With the faces it doesn’t matter which one you remove, you always end up with an identical valid mesh. Non-manifold edges on the other hand are edges where three of more faces come together. Removing different faces will result in a different outcome.
Since there aren’t that many problems with the mesh, perhaps easier to bake it into Rhino and fix it manually?
I have manually fixed all of the non-manifold edges, so ‘check’ now returns the following:
"This is a good mesh.
Important things to consider with this mesh: Mesh has 4915 normals that are not unit vectors, 4915 of which have zero length. Although this does not necessarily mean that the mesh is bad, these normals can cause problems if the ultimate goal is for rendering purposes. Mesh has 5879 faces where the face normal differs substantially from the vertex normals. Although this does not necessarily mean that the mesh is bad, these normals can cause problems if the ultimate goal is for rendering or boolean purposes. Mesh has 45 pairs of faces that intersect each other. Although this does not necessarily mean that the mesh is bad, it can cause problems if you’re doing mesh boolean operations with it."
However, when I reference the mesh into Grasshopper, the mesh component read ‘invalid mesh’
You can use the Null Item component in Grasshopper to inspect data for validity. The D output should have more information about why an object is considered invalid.
If you are going to use weverbird Catmull Clack Subdivision in the last step, then, even if you use hexagons, the final result will probably be similar.
