:rolleyes: That is just a madeup word, referring to all of the proprietary mathmaics Poser has been stocked with, just for processing native technology; like your .CR2s.

I mean some of the money you've paid for Poser with was the cost of just this programming specifically, and we know it works fine, so leave the streamlining to Poser's Developers.   If Poser formats were too large, Poser would have never got off the ground and sold like it has. :ohmy:

What you are suggesting seems like a huge overhaul of Poser programming, that(I think) would happen to technology that came after the riginal .OBJ.  Which would be awsome, if you are correct, because then I'd say you should not only get a refund for your purchase of Poser, but then a job on it's Development Team :tt1:

I think trying to take that much of a shortcut, around native Poser files, is too much work; I'll just live with the Deveoper's current File Format System, becasue beween them and my$elf  it's all just number crunching. :scared:

If either of us would care to actually purchase Poser, from EF, and then Test...replaceing the Poser files with .OBJs(or whatever;) I'd say Godspeed to you, but then need add a few Hail Mary's :mellow: