Forum: Poser - OFFICIAL


Subject: M4 Bodysuit OBJ file... portability issue to be aware of

konan opened this issue on Jan 05, 2009 · 2 posts


konan posted Mon, 05 January 2009 at 10:09 PM

Hey Everyone,

This issue was brought to my attention by one of my customers. Please forgive me if it was already mentioned. As it turns out, the OBJ for the body suit contains negative indices for the texture coordinates. Here is a wee clipping from the file...

...
v -0.0522237 0.317561 0.0475531

Point/Line/Face list

g chest
usemtl 2_TurtleNeck
vt 0.200240 0.905683
vt 0.205515 0.902480
vt 0.201032 0.900054
vt 0.195893 0.902887
f 12/-1 7/-2 45/-3 44/-4

...

Some software packages may have trouble reading the UVs in this file, so if you need to edit it with the UV coordinates, it might be a good idea to import it into Poser or DS, then re-export the OBJ file. Currently, our software (Blacksmith3D-Paint/Suite) cannot read the UVs in this file properly, but I will make some adjustments in the next update. It will however properly read it after being exported from Poser as mentioned before.

Here are the first few polygons after being exported from Poser...

usemtl 2_TurtleNeck
f 12/4/12 7/3/7 45/2/45 44/1/44
f 45/8/45 47/7/47 46/6/46 44/5/44
f 46/12/46 49/11/49 48/10/48 44/9/44

Konan

p.s. That's the funny thing with OBJ files. They are so generic (being ascii files and all) that each application that exports them can do something just weird enough to confuse other programs. I do recall reading something about negative indices in OBJ files relating to 3DS Max. Some dude who wrote an OBJ import/export plugin for MAX was ranting pretty hard about it on his web site.


markschum posted Mon, 05 January 2009 at 10:29 PM

those may be relative indices which are legal but not handled by some. You can also try the free uv mapper , and save the file from it after loading. It seems to write a more standard obj file format.