Game Editing > Scripts & Support

[MD5] EXPORT script for Blender 2.6x (OPEN)

<< < (35/46) > >>

kat:
The coordinates shown in "bounds" represent the MD5's bounding box (volume of space occupied) per frame of a given animation sequence.

Assuming the mesh and Armature are properly centered on Blenders grid so the Objects 'Origin' point is placed at grid-centre (0,0,0) prior to export, both positive and negative values should be seen in the resulting output because they represent, in 'Object Space' (values based on the Objects Origin iirc), the 'min' and 'max' "X", "Y" and "Z" coordinates of each face of the six-sided volume as it changes shape and size due to articulation of the underlying mesh.

If you're not seeing any obvious errors, i.e. the mesh is all over the place, what you have there appears to be fine.

Rajveer:
Thanks for the quick reply. The models I've tried look fine - they are properly centered and have width in all axes. With all of them I get the same issue, the min x, y, z and max x values are all the same. When trying this with the "Bob" MD5 model provided in the MD5 downloads section on this site I get the min x, z and max x values being the same, so the bounds ends up being a 2d square along the y-z plane with no width, which definitely looks wrong (this was in Blender 2.63 and 2.66a)?

kat:
What are you using to test/view the mesh data? Using 'Bob' there shouldn't be any general issues using the files as-is, so there must be something else going on. To check try exporting from Blender 2.69 using the same script (which works fine) to see if that fixes the issue.. if it does then you know there's a problem exporting from the mentioned versions of Blender rather than the files you're actually exporting.

Rajveer:
I've downloaded Blender 2.69 and unfortunately get the same issue. I'm using my own engine to view the MD5 mesh/animation and it's per-frame AABB, however the AABB problem can be verified by just opening the file in Notepad++ and comparing the values. The actual exported model and animation work perfectly, it's just the bounding boxes that have an issue.

If you have the time, could you verify these results by trying to export the Bob MD5 model and checking what the exported bounds are? I only ask because I'm at a loss :(

kat:
OK looking in to this as the bob example files exported from Blender 2.69 are showing some odd distortion errors for me when opened into MD5View - something that doesn't happen with other recent files/projects so I suspect these issues are the result of the many internal changes Blender has undergone with 2.5/2.6 series. Will post an update shortly.

Navigation

[0] Message Index

[#] Next page

[*] Previous page