Really? Tell me more.

I'm asking because in skimming the Cornucopia thread it appears that the script in question creates a "sequence of meshes" which is what the Barton export script does though it is limited to the .obj format rather than the list of Vue compatible formats in the thread.

Does your import script eliminate the requirement for having an export script by handling both ends of the pipeline in effect?

I'm definitely interested in an alternative method that is more resource friendly for prepping the simulation so it is readable by Poser .

The main (only) advantage that I've found for converting to .obj is that the results are usable in any program that handles .obj sequences.

Now my other question is: How does your import script handle extracting the information from within the Blender file.?

As you noted in the discussion in the Cornucopia thread .obj format while simple to parse is much larger in size than a binary format. in the interest of resource efficiency being able to use binary formats is much more appealing.

Perhaps you can also give insight into improving Meshfoot, a script for handling Poser .obj sequences so they can be imported into Blender for animation purposes. Sounds like you could clean that up or eliminate the need for it entirely.

I tend to be direct when asking questions so please don't take anything outside of that context.