Cool.  I structured the code in a way that should make it easy to tell, for example:

"if I used to do X, to accomplish Y, I can now do Z to accomplish the same thing"

...as mentioned earlier, 'Z' is somewhat of a moving target at the moment, as shown in one particular example in the file:

    # each of the following do the same thing, just progressively more efficient/faster
    # point = Vector(v.x + (ray.x * intersect), v.y + (ray.y * intersect), v.z + (ray.z * intersect))
    # point = v + ray.scale(intersect)
    point = v.project(ray,intersect)

...as new functionality is added, there may be new (and/or faster) ways to do the same thing.  On a related note,  because the new keeps track of the face normal and plane equation, those tables don't need to be built (or passed to the test routine) when using this extension.  (BTW, I noticed that I didn't do a "pplanes = []" after the Numeric test run, but that shouldn't hurt anything).

[EDIT: those (separate) tables don't have to be built or passed to the routine, but you do have to call the Generate_TriPoly_Normals() routine to get them generated in the TriPolys structure]

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.