If you ever port this to C++ to get better performance, you should consider using CGeometryAccessor instead of the geometry API. CGeometryAccessor is more scalable and much faster to access the geometry data than the geometry API which is a pain when dealing with very large meshes.

-mab

Just wondered if you had any performance stats? Not only to see how fast it runs on a dense mesh, but also to see how it compares to writing a similar script with commands?

Cheers

Andy