Ok, I finally (mostly) figured out what Vue is doing (which I consider 'wrong')...

• When Importing, Vue generates a Vertex-per-UVvert... so a cube would normally have 8 vertices, but since there are 6 faces, with (potentially) 4 separate UV values for each face, you end up with 24 vertices.  If this wasn't bad enough, somehow Vue comes up with 28 vertices for a simple cube (some not used for polygons).
• After the above vertex-expansion, it then does in fact do a averaging of ALL the vertices to find the center of the mesh - when it should be calculating an average of the 8 vertices that make up a bounding box of the mesh.

...I added code to one of my plugins to confirm the above and came up with the exact values that Vue comes up with (at least in some cases).  I did not check all cases (when no UVs exist, for example) and apparently the 28-vert cube example above may only use 24 of those (or something) to compute the center with, but a uv-mapped 3000+ vertex model I ran through testing came up with the exact same values Vue did.

Short story - this "bug" has nothing to do with how any app or plugin exports .obj files - it's a bug/feature of how Vue is determining the center of an imported mesh.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.