Pre-binary DMX meshes can't export

[GoogleCodeExporter]

What steps will reproduce the problem?
(-1. Import a mesh.
0. Export it as DMX; it will now be a binary DMX, with bones and mesh.)
1. Import binary DMX mesh (like one exported by Blender, not one from the 
Source SDK; they are KeyValues 2)
2. Export it.
3. Import or compile the newly exported one.

What is the expected output? What do you see instead?
Expected: Model with bones and mesh. Noticed: Model with bones... but no mesh.

What version of Blender and the SMD Tools are you using? On what operating
system?
Windows 7 64-Bit
Blender 2,69a (current), and/or 2.67b, and/or 2.65a, and/or anything else with 
SMD Tools support. (Blender-independent. Unknown for 2.68a, though, as it 
didn't import DMX UV maps correctly.)
SMD Tools 1.9.1 (current), and/or 1.9.0, and/or 1.8.6, and/or 1.7.2, and/or 
anything else with DMX support. (Version-independent.)

Please provide any additional information below.
Because of this, if one exports a DMX mesh, one can't import it, edit it, and 
then re-export it, since there will be no mesh.
Occasionally, Blender will crash/quit upon exporting a pre-binary DMX.
It IS possible to export pre-binary DMX meshes as SMD, and import them again, 
with functioning mesh and bones. Though, if having flexes, it will be annoying 
to name the flexes correctly again, since VTA import doesn't name flexes, even 
though they have "# [name]" after their "time [vta frame number]" in the VTA.

Original issue reported on code.google.com by TheZeroT...@hotmail.com on 5 Nov 2013 at 1:31

[GoogleCodeExporter]

Fixed in r354 and a re-released 1.9.1. This is a fairly obscure bug so I've not 
bumped the version number.

Original comment by cont...@steamreview.org on 5 Nov 2013 at 2:43

• Changed state: Fixed

[GoogleCodeExporter]

Now that I've had a go with the re-released 1.9.1, I can confirm that you did 
fix it. Pre-binary DMX files now export like a charm.

Original comment by TheZeroT...@hotmail.com on 6 Nov 2013 at 5:44