Now we have written one of the first meshes and opened the file in Rhino and it is saying it is an invalid mesh. If you click it in the viewport you can see the wireframe. When it is unselected you don’t see it at all in the viewport.
How can we find out what exactly makes it invalid? The mesh that is written in VL is a valid mesh as it can be rendered just fine, but maybe there is something missing.
Our dev will check it out. Meanwhile is there a way to get the log in Grasshopper? That would be very helpful since invalid meshes can happen quite quickly.
Interesting it is now saying that it is a valid mesh. Not sure what I did, but I though I had not done anything other than delete some layers.
Any idea why it is still not showing correctly in Wireframe mode? I can only see it when its selected. It seems like it’s actually there, but just rendered in the same color as the background or in some transparent material.
ON_Mesh.m_N[57282] is not a unit vector (length = 0).
CRhinoObject.Geometry() is invalid.
The mesh has unit vectors of length 0. I guess that’s a result of degenerated face.
As per this, Rhino is checking topo for every vertice which I think is slow, possibly due to zero-area faces sharing edges and generating a very heavy topo map.
I’ll look at whether the 0 area triangles can be filtered on the GPU or has to be done with the Rhino3dm library on the CPU.
Yes, seems to be the same issue. Maybe when downloading the buffers from the GPU they are too large or the count values aren’t correct. I’ll revisit that.
