Arrgh...  I must have forgotten to hit the "Post" button yesterday, 'coz my first reply is missing.
 
I'm very excited about this format.  It is binary, and I can't seem to find any documentation on it, so I'll need to reverse engineer it.  If you could make up a file with the fewest possible number of vertices (but at least 2), and very few frames (2-3 is fine), and then document where the vertices are in each frame, I should be able to back it out of the binary file.
 
For instance:
If the object was a line (2 vertices), and in frame 1 it went from (1,2,3) to (4,5,6), and then it was moved in frame 2 so that it went from (3,2,1) to (6,5,4), that would be pretty much the perfect example file.  If that can't be done, a triangle would also work (just put the third point somewhere convenient, and tell me where it is).  And if that can't be done, a tetrahedron is the next best option.
 
Actually, it might be useful to actually have a third frame (just in case), and to know what the framerate is, so that I can try to back out the timing system.
 
Then, after I work out that file to where I think I know what I'm talking about, I can run my code against your larger file to see if things continue to make sense.
 
As always, many many thanks for your help!
Mac