A tip from the perspective of a complete newbie; you could try to avoid structures that are not required for the program to run (and if you feel these should be included, get to it at later tutorials when the reader has a better idea of what he is doing).

For example, I found:

pVertexObject->Lock(0, 3*sizeof(D3DVERTEX), &pVertexBuffer, 0)


easier to understand than:

if(FAILED(pVertexObject->Lock(0, 3*sizeof(D3DVERTEX), &pVertexBuffer, 0)))
return(0);


because the code doesn’t fail anyway, whatever that means. And the above can be used in void functions etc.

Cheers

Property Page-> Configuration properties -> General -> Character Set “change it to Multi-Byte”

You can use the triangle strip method of drawing in a 64x loop to draw them all:

for (int i=0; iDrawPrimitive( D3DPT_TRIANGLESTRIP, i*4, 4 );
}


Regards, Peter

For anyone that wants to know:
InvalidateRect(NULL, hWindowHandle, FALSE)

Anyway, now I’m looking for an accurate timing system to force redraws every set number of milliseconds. Anything in ctime.h goes by seconds, and clock() uses a preset (unaccurate) measure that basically makes it a really fast frame counter. I’ll probly be able to find one myself, but just wanted to let you know I solved my original problem

BTW thanks again for the tutorial

Also, through playing around a lot, I have some more questions.

First, I am currently having a problem with one of either two things. I’m guessing the problem is that the window never redraws itself (unless I resize it). Is there a way to change this? Also, will this work for getting the r/g/b/a values of a color?

union
{
DWORD color;
struct { BYTE r, g, b, a; }; //Does alpha come first or last?
};

I’m guessing my first question should solve my problem. If it doesn’t then I’m guessing either the union is wrong or theres something messing me up with my multithreading (I have one thread for drawing and one for the game loop… though at this point I doubt its the problem)

-Greg Dolley

I just have one question. You create pVertexObject and pVertexBuffer, and then lock pVertexObject, which gives you a pointer to where to write to the buffer. My question is: are pObject and pBuffer not the same? (I would guess not if it requires both of them). I’m guessing pObject points to some type of struct/class/other data that DirectX uses (basically a header for the actual vertex buffer data), and pBuffer points to where the actual data is?

Also, once pBuffer has a value (and as long as you don’t resize pObject), will that value always be the same?

Lol I know I’m probly a pain but just wondering. Thanks for the tutorials again!