I could really use an explanation if you guys have one. Here is how it is. I have my main file set up LaMothe style (GameMain, GameInit, and GameClose, not the gpdump thing). I am making this wrapper around Dx6 and I got it set up and then I drew some pixels on the Primary surface in the GameInit fucntion. When PeekMessage is called for the first time, the surface is totally wiped. BUT, if I draw any pixels after the first time PeekMessage is called, like in the GameMain funcion, PeekMessage doesn''t wipe my surface. To prove it I set up this code that would execute twice and put it just before PeekMessage. The first time I drew the pixels, PeekMessage wiped it, the second time PeekMessage was called, it wasn''t wiped. Someone please tell me what is going on. It isn''t like this is going to halt development of my wrapper or anything, but I would like to know why this is happening. Oh, and yes I am sure it is PeekMessage that is doing the wiping. If you guys can figure out what is happening, great. If you really need to see my code, I can. -Blackstream -Exerpt from the "How to get killed in gamedev.net forums" book Tip 242: Say this, with all the punctuation and I guarantee you''ll get strange looks or flames hi i have been programming for 3 months now and now i want to make a game sorta like quake 3 could you please tell me where to start thank you

No, I didn''t override WM_SIZE... That WM_ERASEBKGND is probably my problem. I don''t have any surface clearing code in any messages so I guess it is the WM_ERASEBKGND that is doing this. In the future I plan on drawing on Backbuffers and redrawing every frame, so if the WM_ERASEBKGND message did come up, I would still be okay.

Are there any other messages I need to watch out for besides the resizing, focus, and initiation/destruction messages?

-Blackstream

Just me, and my compiiiiiiiler

Oh okay. Thanks all, you''ve all been very helpful.

-Blackstream