Shawn

Thanks for insightful replies.  

 RE: >>For every modeling/rendering program, there is another version of the OBJ format.  No two programs import/export the same OBJ format.<< this explains my fustration.  So I gather the various 3D apps look for the general OBJ structure and verticy addresses and then builds from there. What they take from the data they do, and append more metadata properties as needed in the MTL?  In other words they interpret what they can, processess and add value, and append thier app specific data as needed to the files.  To learn more rather than look at my modelers output I need to examine my render's desired INPUT. OK!  A direction....

Background being in CAD / Engineering I decided to give subd character modeling a try. Ultimately my objective being to learn to make "retail quality" 3D characters and props, in the mean time I get up to speed I use what I can to render still images for themed web sites.  With that goal, I figure I should aim to make open architecture and broad use to make the most of each model.  That result would be multi-resolution model & texture packs,  with collada and milkshape rigged versions. I'm thinking this would be the aim of most general content developers.  (?)

Is there a .DAE de-compiler (or source) that allows you to examine DAE file structure ?