All polygons are broken down into triangles before rasterization on the graphics card. So when you switch to wireframe rendering (which I am guessing is how you saw the triangles) you will see the edges of the finally rendered triangles. I believe there is a method to stop these from being rendered by flagging edges on your model for display.
All polygons are broken down into triangles before rasterization on the graphics card. So when you switch to wireframe rendering (which I am guessing is how you saw the triangles) you will see the edges of the finally rendered triangles. I believe there is a method to stop these from being rendered by flagging edges on your model for display.
No it isn't in wireframe mode...it's in fill mode...
The vertices of your all your quads are defined in a zig-zag order, like a Z, and not clockwise or counter-clockwise around the quad. The order of your vertices are very important. It should be enough to swap the order of the last two vertices of all quads to at least have the vertices define a proper quad. There may be other problems, such as inconsistent winding order and backface culling, that will break your cube.
The vertices of your all your quads are defined in a zig-zag order, like a Z, and not clockwise or counter-clockwise around the quad. The order of your vertices are very important. It should be enough to swap the order of the last two vertices of all quads to at least have the vertices define a proper quad. There may be other problems, such as inconsistent winding order and backface culling, that will break your cube.
Thanks man...didn't know the vertices had to be in order...
