Re: ac_object_get_triangle_surfaces vs ac_object_get_surface
Well, I'm afraid I found the difference between our logics. When you get triangulated surfaces from the object the surface listing is in opposite order from the list you get if you just get 'surfaces'.
This seems to indicate that I have an input order dependency in my code, but I can't actually rely on the surfaces coming in in an order that works.
What surprises me is that this hasn't been reported from the field, yet.
Is there any magic behind internally tracked surface listings which has protected me from these problems, or has it just been luck that no-one has reported them?
-- Jeff
|