Anyone knows what''s the difference between: Using ChangeDisplaySettings to change to fullscreen mode vs Creating a borderless window that has the same dimensions as the display area? Is the application supposed to run better under fullscreen mode?

Normally, when you call ChangeDisplaySettings() you then create a borderless window that covers the whole screen anyway. ChangeDisplaySettings() will change the resolution of the screen, so you''d only not call it if the screen was already in the resolution you wanted.

War Worlds - A 3D Real-Time Strategy game in development.

ChangeDisplaySettings does exactly what the control panel->display->settings->Resolution/color depth thing does. It has nothing to do with fullscreen, you still have to make a window. Unless, of course, you grab the DC of the desktop(there''s a function for this...) then you can draw on it-but I wouldn''t recommend it.

And, of course, the desktop is a window, too.

There are some advantages to running an app full-screen. As gph-gw hinted, there really is no distinction between windowed and full-screen since the latter is just a borderless window whose client area happens to fill the screen. However, since the app takes up the entire screen, this means that the OS doesn''t expect the user to have other windows showing at the same time. This assumption allows for page flipping or triple buffering, both of which are usually faster than the back buffer copying method.

Thanks everyone, everything''s clear now.