Meaning somewhere in the pipeline the OS or driver or both eat 2 extra frames, which is near to unacceptable for the application. When running the same software on Windows 7 (with no other software installed at all) however, we cannot get lower than 5 frames. On some systems with higher end cards we even get 2 frames. This is tested on a variety of systems, all running NVidia cards. The result is the approximate delay between the trigger and when the frame is effectively shown on the screen is, depending on video card and drivers, 3 frames or 50mSec for a 60Hz screen. This behaves very well on Windows XP: bsically the software waits for some trigger and when triggered, creates a new frame, puts it in the backbuffer, then tells DX to flip the buffers. The main task is putting something on the screen in response to external triggers in a reliable manner.

We have a piece of software that is programmed against DirextX 7 SDK (i.e the code uses LPDIRECTDRAWSURFACE7 and the likes) and runs in fullscreen.

Directx7 for windows 10