Interesting… although my code doesn’t do anything interesting with the meshes at all. It stores a mesh that rhino generates and assigns colors. The only modification I think is that it gives each polygon a distinct set of vertices, so that it won’t interpolate colors between vertices. I will try it, though.
Is there a resource that explains the new criteria?
Thanks for informing me of this change. So given my share that my code discretizes each polygon so that false color shading is disabled and each polygon can have its own color (and I suspect this is what is causing the issue), I have two questions:
Should I be doing this? Is there some sort of consequence I should consider (bearing in mind that these are just analysis meshes, designed to demonstrate acoustical parameters over an area).
If the answer to the above question is that it is fine, then what hoops do I need to jump through now, and will the code still work in Rhino 5 when I’m done.
Hi @Arthur, run mesh.IsValidWithLog() to find out what is wrong with the mesh. It would also help if you can show the object properties page of your mesh before you changed the mesh. My guess is that David is right and the problem is related to double precision mesh. If this is the case, note this.
How is this performed in your code ? Be unwelding or by creating a new mesh face vertex list ?
It’s a little complicated, because I run the mesh through my own mesh and Ray tracing code.
Both functions that do this are here:
First, it runs the BREPs though Create_Map_Mesh(), and then through Rhino_to_HareMesh().
After it has run the simulation, when you plot the results, it calls PlotMesh, which calls Hare_to_RhinoMesh(). PlotMesh then rewrites the mesh as discrete faces. (PlotMesh might be what you’re looking for.)