Viewerframe refers to the dedicated window or environment where a remote session or virtual machine is rendered. Unlike a standard application window, a viewerframe must synchronize its internal frame rate with the host's display hardware to prevent visual artifacts. The "Refresh Exclusive" Distinction
The application "locks" the display's refresh cycle to its own output, bypassing the standard desktop composition layers. Why Use Exclusive Refresh Modes?
Set "Monitor Technology" to or G-Sync/FreeSync depending on your preference for exclusive control. Application Level viewerframe mode refresh exclusive
In standard windowed modes, frames often pass through a "compositor" (like Windows Desktop Window Manager). This adds a few milliseconds of delay. Exclusive mode creates a direct path to the GPU, which is vital for gaming or precision design work. 3. Fixing "Micro-Stutter"
The application shares refresh resources with other background tasks. Viewerframe refers to the dedicated window or environment
Configuring this mode typically involves three distinct layers of your setup: Hardware Level
Ensure your monitor supports the intended refresh rate (e.g., 144Hz or 240Hz). If the monitor is capped at 60Hz, exclusive mode cannot push past that physical limit without causing "out of range" errors. Driver Level Within your GPU control panel (NVIDIA or AMD): Navigate to . Locate the specific viewer application. Why Use Exclusive Refresh Modes
If the viewerframe tries to force a refresh rate your monitor doesn't support at its current resolution, the screen may go blank.
Screen tearing occurs when the video feed sends frames faster or slower than the monitor can display them. Exclusive mode forces a 1:1 match between the viewerframe's output and the monitor’s physical refresh rate. 2. Reducing Input Latency
Toggle or "Match Host Refresh Rate." Troubleshooting "Refresh Exclusive" Issues While powerful, this mode can occasionally cause conflicts.