Quote - ...snip...For the time-being, you should not pass the (optional)  'texpolylist' to the TriPolygonize() routine, or count on those elements being correct in tripolys unless you know that the entire mesh in question is fully uv-mapped.  The indices found in the Ngons (if not set to 'None') should be correct though.

I take (part of) that back... just to clarify, if you are using the MeshType interface to get your TriPolys, then the uv0, uv1, uv2 members of the TriPoly will either be correct, or all set to 0.

If you're using TriPolygonize() and pass in the optional 'texpolylist', there's a potential for crashing (or at least causing an exception).

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.