RC Mesh.MatchEdges() often makes invalid meshes - how to fix?

Hi there,

I’m finding that running MatchEdges() on a mesh frequently produces an invalid mesh - which makes parts of the script using the result downstream fail - and I’m wondering why… Running the native Rhino function does not often result in a bad object.

Corrollary to this is how to repair an ‘invalid’ mesh once it has happened.

Hi @Helvetosaur,

If you have a simple way of repeating (the creation of bad meshes), we’d like to see it.

– Dale

Hi Dale,

I will try to create a couple of simple examples in the next day or so, thanks.