does it make a difference what file 4mat you use when creating objects, props, clothes, etc 4 poser??? i was using rhino, and am able 2 import/export perfectly using .3ds.

Well ultimatly it doesn't matter. In my oersonal opinion it does and I will tell you why. Lets start with a final result. You want an object that works well in poser that can also take a good texture map. Now how do you get that? Well poser uses OBJ files, that's easy enough. To create UV Coordinates for texture maps I use steve's UVMapper. It exports OBJ and only imports OBJ. This takes me to needing an OBJ format before I even hit poser. Rhino exports to OBJ fine. So I use Rhino to make My model, export to OBJ. This allows me to UV map it in UVMapper and save the new UVMapped Object. This object imports directly into Poser. So you see, you could add a step ad import whatever format into poser and then export it again as OBJ, but why do the extra step if you don't have to.

ok, check it..... i really like the way rhino and poser work together using the .3ds import/export. the pieces fit exactly in poser as they do in rhino, all good and well........... your concern is using uvmapper, which only handles .obj files.......... but i also use lithunwrap, which has a host of import/export 4mats, .3ds being 1 of them. so am i good 2 go?

I would say so. It all depends on your workflow really. I use UVMapper so I go with OBJ. If your workflow works well with 3DS then stick with that.

Just a Q - can someone clue me in as to this 'Lithunwrap' ? Just like to keep informed and this is one that rings a bell but dont seem to remember :) Cheers

Attached Link: http://www.unwrap3d.com/

lithunwrap is similar 2 uvmapper, but i find i can get better results w/ lith. you can map pieces of the same object differently, you get a whole lot more import/export options....... best way is 2 see 4 yerself..... i see now tho that the whole thing is changed.......... guess you missed a great 1, lol