Quote - Okay.  Two questions.

1. Is it bad to have an option to fill verts with the localspace vertex coordinates?  These are sometimes useful, or even necessary (as when creating a morph which doesn't bake in the worldspace positions).

Just not there yet.  But I'm not sure the example you give makes sense :).  A morph is computed as a delta - from wherever the verts happen to be, to some new position, relative to there.

Quote - 2) Is there any reason not to allow vpolys for tris, or is that simply not added?  I've had cases where the vpolys list for... tpolys, as you call it, has been useful.

Just not there yet.

Quote - I'm really pleased to see the distance functions ported over.  I was considering using squared distances for something, recently, because I was afraid the square roots would slow things. 

You know... I don't know this.  What does the abs function do when applied to a vector?  Just return the abs value of all the vector values?  Or is it completely different?

 
Yes, the fabs() of each element.  Frankly, I'm not sure how usefull this is, but it was already implemented as such, so I left it.

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.