Bad Mesh Or Is It

Rhino 7. Why exactly is this mesh bad…?

Looks more like a bad ‘meshage’…

Hello - can you export this mesh and send to, with a link back to this topic in your comments? Looks like we need to tune the mesh checking…


Could it be is learning from Twitter…?

Pascal, file send. Generally I have to say Rhino 7 Mesh Repair tools are not too bad.

Hello - I think the mesh is fine - Check finds some self-intersections but actually locating these with MeshSelfIntersect shows they are ‘fake’ - it looks like the self-intersection finder needs fine-tuning, to me.


Hi Pascal
actually I didn’t know about MeshSelfIntersect command existence. After I run Check and than MSI I got these 4 intersections. I understand these are fake intersections you mentioned…?

Maybe it is morally bad. :grinning:

1 Like

Yes, exactly…


OK good.
Are there any other not obviously visible mesh diagnostic or repair tools…?

If Rhino becomes judgmental I’m screwed


Check Meshes is still very buggy. This is my latest out of several different weird behaviors I’ve encounter over the past few weeks.

It says good objects but it lists 20 zero length edges and yet Repair function is not available…


Hello - can you please post that mesh or send to with a link back here in your comments?


Like this (1.5 MB)

Got that, thanks - RH-63364 MeshRepair: Does not agree with Check, or itself


RH-63364 is fixed in the latest Rhino 7 Service Release Candidate

Thank you. I’m sure I will find out how effective your fix is…:slight_smile:

Sorry guys but it looks like the issue is still here.
Rhino: 7.4.21078.1001

Install this version

Thank you. This build indeed fixed the issue. So far so good.

1 Like