Quote:
Originally Posted by Jeff-Groves
Read up on how the obj file handles faces. It's really simple once you fully understand it.
3 verts make a face. The f tells you what v gets what vt
f v1/t1 v2/t2 ....
|
You are right, if v's order was messed up during the recombining of an object (needed for baking its AO map), I could always grab the v coordinates of the main obj file (the one with diffuse UV map stored) and paste them in the AO obj file. The problem comes with face definitions. Keeping on your example, let's say that these are the face definitions of the main obj file:
f v1/t1 v2/t2 v3/t3
and these are the face definitions of the AO obj file (with messed up vertex order)
f v1(ao)/t1(ao) v2(ao)/t2(ao) v3(ao)/t3(ao)
The faces of the fixed AO obj file should look like this:
f v1/t1(ao) v2/t2(ao) v3/t3(ao)
I could do that file merger in excel indeed, but unless I find a way to create an 'intelligent' generic spreadsheet that works with obj files of any length, setting up a 'specific' spreadsheet every time, is going to be a time-expensive exercise...