Definition not running on certain meshes? Please help!

Okay this is a series of mesh that I am trying to run this definition on.

The mesh were generated in Maya, the color was mapped on, and each surface was extracted, then combined (so they are ever so slightly seperate faces that are grouped by the original geometries).

I exported them into an .fbx 2010 and then imported into rhino.

When I run this definition, I can't get the 2 large meshes up front to respond.

Any advice???

Thanks in advanced.

Replies to This Discussion

Permalink Reply by David Stasiuk on May 15, 2012 at 8:24am

Hi Leila-

Some of the meshes you had imported weren't clean...a number of duplicated edges and vertices...normally you could just weld the mesh vertices before you run it into any weaverbird component to fix this, but doing this kills any color information embedded in the mesh, which is a key part of your definition. To work around this I welded all your meshes and then decomposed both the original and the newly welded meshes. Then I did a closest point lookup between the newly welded mesh vertices and the old mesh vertices, and based on the closest point index pulled the appropriate color value from the original mesh (even though there were duplicate vertices, the color values were the same for any duplicates, so the closest point just picks one of the two) and rebuilt the mesh with color embedded using the newly welded mesh topology.

Hope the explanation helps!