Viewerframe Mode Exclusive
Because the OS compositor isn't running, standard overlays cannot draw on top of an exclusive viewerframe. Game developers must implement their own overlay rendering within the game engine. This is why Discord overlay often fails in "true" exclusive fullscreen.
Technologies like G-Sync and FreeSync require direct control of the display’s scanout timing. Exclusive mode provides the cleanest signal for VRR.
If exclusive mode is so great, why do we have borderless windowed mode?
The Alt-Tab Tax. Switching out of an exclusive fullscreen application requires a "mode change." The monitor has to re-sync, the GPU has to reinitialize the desktop heap, and the OS has to rebuild the compositor. This causes the dreaded 2-3 second black screen delay when tabbing out. viewerframe mode exclusive
Multi-Monitor Headaches. Exclusive mode works best on a primary monitor. Trying to drag a mouse cursor from an exclusive fullscreen game to a secondary monitor with Discord often fails unless the game minimizes.
Why would developers hide this setting behind a command line or config file? Because of three critical benefits:
1. Latency Reduction (The Big One) In exclusive mode, the render queue bypasses the OS compositor. This shaves off milliseconds of input lag. For competitive gamers or real-time interactive simulations, the difference between 15ms and 8ms of latency is the difference between a hit and a miss. Because the OS compositor isn't running, standard overlays
2. Tearing Control (VSync Optimization) Windowed modes rely on DWM’s forced triple-buffering, which can introduce stutter. Exclusive mode allows the application to change the display resolution and refresh rate on the fly and implement standard double-buffered VSync or G-Sync/FreeSync much more reliably.
3. Memory Bandwidth The OS no longer needs to keep a copy of the back buffer for "peek" functionality (like the volume overlay). That reclaimed memory bandwidth goes straight to texture streaming and geometry processing.
Due to compositor improvements, many applications no longer strictly require exclusive mode: motion-to-photon latency would make users vomit.
Nonetheless, for professional latency-critical or custom timing applications, exclusive mode remains relevant.
| Metric | Exclusive Mode | Windowed (Shared) | |--------|----------------|--------------------| | Latency | Usually 1-2 frames less | Higher due to compositor | | Tearing | Controllable via swapchain | Compositor often adds vsync (may increase lag) | | Refresh rate | Can switch dynamically | System-defined | | Color depth | Full control (10-bit, HDR) | May be clamped by compositor | | Performance | No compositing overhead | Extra copy/blend pass |
VR headsets rely entirely on exclusive mode. If you have ever tried to use Oculus Link or SteamVR with a game running in a window, you saw a black screen or frozen image. VR requires "Direct Mode," which is a modern form of Viewerframe Exclusive applied to the headset’s two displays. Without it, motion-to-photon latency would make users vomit.