Quote - It could also be very useful to include data about neighbor verts or polys, the polygons to which a vertex belongs, the vertices of a poly, and possibly things like the polygon center or the material of a poly (or even vert).  And edges of polys, edge membership for vertices.  In trying to create a class for verts and polys, I was going to try to accomodate these things.  They've proven useful in the Geom module, at any rate.

But I'm getting carried away, huh?  <Shifty-eyed emoticon recurs>

All in good time :).

For your amusement:

Hip - [ 1152  :  1279 ]<br></br>
---Test1 Numeric: 0.829999923706<br></br>
---Test1  Vector: 0.234999895096<br></br>
---vector.timetest1(): 0.0160000324249<br></br>
Abdomen - [ 2270  :  2362 ]<br></br>
---Test1 Numeric: 1.53500008583<br></br>
---Test1  Vector: 0.438999891281<br></br>
---vector.timetest1(): 0.0150001049042<br></br>
Chest - [ 3732  :  3914 ]<br></br>
---Test1 Numeric: 2.53799986839<br></br>
---Test1  Vector: 0.72100019455<br></br>
---vector.timetest1(): 0.0469999313354<br></br>
Neck - [ 676  :  754 ]<br></br>
---Test1 Numeric: 0.484999895096<br></br>
---Test1  Vector: 0.141000032425<br></br>
---vector.timetest1(): 0.0<br></br>
Head - [ 14022  :  15078 ]<br></br>
---Test1 Numeric: 9.77399992943<br></br>
---Test1  Vector: 2.82000017166<br></br>
---vector.timetest1(): 0.155999898911<br></br><br></br>

...note the 3rd timng on each actor... "vector.timetest1()" ...that's the same test code ported over into the .pyd file.  That confirms what I was talking about before... the real speed comes from moving entire routines into the C code :).

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.