I have a directx9 application that needs to be run on a machine with Aero disabled. The application runs in windowed mode. When a window is first created, it looks just on one screen. When I move the window so that it spans two screens attached to the same graphics adapter (and graphics adapter), the area on one screen seems to reflect the region on the other screen. When I span two screens attached to different graphics adapters, I have no problem.
This can be easily reproduced using any standard window application, such as Tutorial 2: Vertices in the SDK of August 9th.
I see the same problem with the OpenGL window application.
This is not a problem when Windows is running with Aero turned on, but I need to run the application with Aero turned off. (Aero causes other problems in my actual application, flipping my own backbuffer in unpredictable times due to the processing that I do on the GPU, adding smoothness to my display in a manner that cannot be visualized by the thread.)
I am running Windows Vista Enterprise x64 with nVidia Quatro 4800 graphics cards.
- and I just noticed that this is only a problem when I use rotating screens rotated 90 degrees in the nVidia control panel. I think ... what is it then? Can anyone suggest a solution when I use rotated screens?
Any ideas?
source
share