Up until recently, I’ve been using a C++ tool written using assimp to export objects from blender files into a format that is useful for some other software. The problem is that it only works on 2.5x and earlier blender files.
I wrote an export script in blender 2.68 python to replace the tool, but there are some pieces of data the old tool used which the new one doesn’t account for, in particular some transformation information that is important for the models i’m exporting to display correctly in relation to each other, both in size and position. I’m sure that there is stored, SOMEWHERE in the bpy.data.* structure, some additional position and scale information which I can extract and use in a 4x4 transformation matrix in order to duplicate the previous methodology, but it doesn’t seem to be obvious.
All of the objects that I care about are polygon meshes, no textures, no uv, no bones, no poses.
If anyone had good resources that expounded on the subject, specifically in relation to blender 2.68+, I would greatly appreciate any assistance. Beyond just solving my immediate problem, I’m hoping to understand the conceptual rhyme & reason for the way the bpy.data.* is structured. I’ve been relying on a few people from various forum sites (mostly @CoDEmanX, many thanks), and I’d like to know where folks learned these things in addition to the facts themselves so I can stop bugging folks for these tidbits.
Thanks in advance.