Trying to load up a an specific 3D binary model, and I'm having some trouble with face-reading.

Only documentation I got is that the faces are supposed to be read as strips, and that I should read the last reference point of the last face every time I read a new reference point and create a new face.

But I thought faces are supposed to be created with only 3 indices? How could I possibly create one from 2 reference points?

The face indices are just unsigned short ints in big endian.

TL;DR;, how do you read faces indices as strips and create the appropiate faces in a format like (index 1, index 2, index 3)?

I always thought the indices were completely arbitrary and its up to the programmer to decide what they are. But you have to be consistent once you choose your coordinate frame.

Ok so according to your answers, the following code should work I think...

But it looks like this:
{"name":"605556","src":"http:\/\/static.allegro.cc\/image\/cache\/d\/a\/da1ca4a727f6bc3ce803415892c2d5ff.png","w":405,"h":373,"tn":"http:\/\/static.allegro.cc\/image\/cache\/d\/a\/da1ca4a727f6bc3ce803415892c2d5ff"}

Perhaps...

• the vector indices aren't right,

• or the vectors are supposed to be ordered in the inverse order(as in, pushing to the front of the list),

• or the above code has a bug I haven't noticed yet?

EDIT: It's supposed to be some kind of tree.

If you're creating triangles out of triangle strips yourself, note that odd and even triangles have different vertex orderings (to keep a CW/CCW order).

Vertex list, Faces list(in the order of the binary file)

Here's how the vertices(or is it vertexes? ) alone look like.
{"name":"605559","src":"http:\/\/static.allegro.cc\/image\/cache\/e\/8\/e86ed7a9a167b7422a069fdebc9f4553.png","w":590,"h":536,"tn":"http:\/\/static.allegro.cc\/image\/cache\/e\/8\/e86ed7a9a167b7422a069fdebc9f4553"}

EDIT: The "65535" face index is probably a 0 that I just endian swapped.

I think you might be on to something. But perhaps I just need to add a new face at the end of each strip?
{"name":"605560","src":"http:\/\/static.allegro.cc\/image\/cache\/0\/4\/04a3228cc210bbb3ff6de5f4678e19c2.png","w":822,"h":669,"tn":"http:\/\/static.allegro.cc\/image\/cache\/0\/4\/04a3228cc210bbb3ff6de5f4678e19c2"}

Just looking at the model, it might be what gnolam said, the triangles alternate ccw and cw so every second one is getting culled.

Indeed it seems to be... when I enable the 2-sided faces on Ogre it looks like this:
{"name":"605562","src":"http:\/\/static.allegro.cc\/image\/cache\/f\/5\/f54888b990b3c09174fcb3e49e2f0177.png","w":786,"h":578,"tn":"http:\/\/static.allegro.cc\/image\/cache\/f\/5\/f54888b990b3c09174fcb3e49e2f0177"}

How do I fix the winding problem? Swap the indices order at every odd/even index? Forcing culling off is not really the right way to do it.

Yes.

[EDIT]
I realized I had it handy, so here comes an explanatory diagram for why this is done. Triangle strip representation of 2 connected quads:
{"name":"605563","src":"http:\/\/static.allegro.cc\/image\/cache\/9\/3\/932f02495b960569a060561c122247e8.png","w":542,"h":300,"tn":"http:\/\/static.allegro.cc\/image\/cache\/9\/3\/932f02495b960569a060561c122247e8"}
As you can see, if the winding order isn't reversed, every second triangle will appear to face the wrong way.

If you're reading the model yourself it shouldn't be hard to fix yourself.

read 2 vertices
int t = 0, v = 2
while not done
   read vertex
   if (t % 2 != 0)
      new triangle(v, v-1, v-2)
   else
      new triangle(v-2, v-1, v)
   t++
   v++

See attachment

I tried some of the examples with my OBJ loader, the space shuttle example didn't have a mtl file, the triceratops had more than 4 vertices for a face, and when the f5e_05 example had 3 texture vertices I gave up.

[EDIT]

If I clean them up by running them through Blender they work.

{"name":"605568","src":"http:\/\/static.allegro.cc\/image\/cache\/9\/7\/9789eafdcc5469610f0a17f72ee90ba1.png","w":1000,"h":800,"tn":"http:\/\/static.allegro.cc\/image\/cache\/9\/7\/9789eafdcc5469610f0a17f72ee90ba1"}

All of which are perfectly legal for an OBJ.

(Well, I'm only pretty sure about the first (it's been a while since I did anything with my OBJ loader). The latter two are definitely legal, though - faces can have any number of vertices, and 3D textures are supported.)