100% CPU when D3D window is obstructed?

When your program gets an unfocus message, call WaitMessage().

The CPU will still roar when a window is in the process of being moved around over the app, because it will probably use ON_PAINT to redraw the window.

Jiia, that works for me. Thanks! 3 points for ya.

Quote:

Original post by HaywireGuy What's the cause of it and how can this be addressed? Thanks in advance!

I forget the exact reasoning - but I did see an explanation of this "issue" from one of the DirectX developers a while back. Gonna bug me now [oh]

IIRC, it's something to do with the way that the runtime has to do extra clipping/copying operations so as to "play nice" with the other windows. Things are a bit easier for it when it's in focus [smile]

hth
Jack

Jack, it happens when the D3D is TOTALLY obstructed by other window. Even if
there is 1% of the client area that is visible, the CPU usage remains at 2%.
What I think could be the possibility was that the rendering routine pass
without rendering anything (since the window is invisible to the user), so the
message pump goes looping with literally nothing in it, causing the CPU usage
to go all the way up.

Just like what Jiia said, I use GetMessage() when the window does not have the
focus, this problem goes away. Thanks anyway Jack for your help :)