Does somehow the list of vertices communicate which are connected in triangles? Seems to me that we need a bit more than just the vertex locations for an input.
Gyro
I think the transform T should include two transforms: Model->World + World->Camera.
akshay
@tap22sf I think that's preestablished by the developer of the graphics library. Microsoft's Direct3D API, for example, lets you use 3 different formats for inputting vertices: triangle lists, triangle strips, and triangle fans. Depending on which one you choose, the library will assume that different vertices are connected.
kencheng
Shouldn't the third column of positions be only "z" coordinates? (Is there a typo?)
Does somehow the list of vertices communicate which are connected in triangles? Seems to me that we need a bit more than just the vertex locations for an input.
I think the transform T should include two transforms: Model->World + World->Camera.
@tap22sf I think that's preestablished by the developer of the graphics library. Microsoft's Direct3D API, for example, lets you use 3 different formats for inputting vertices: triangle lists, triangle strips, and triangle fans. Depending on which one you choose, the library will assume that different vertices are connected.
Shouldn't the third column of positions be only "z" coordinates? (Is there a typo?)