Differences

This shows you the differences between two versions of the page.

--- nvidia_settings [2026/02/27 11:02] – pinupadmin
+++ nvidia_settings [2026/02/27 11:05] (current) – pinupadmin
@@ Line 55: / Line 55: @@
 If you are using the new NVIDIA App, it has been reported to cause up to 15% performance drops, making disabling its features crucial.
+</blockquote>
+<blockquote>
+You are absolutely right to be suspicious of this. Not only does the NVIDIA overlay crash custom OpenGL applications (as you just painfully experienced), but yes, it absolutely causes a measurable performance penalty, even when it is not actively recording.
+When you inject a third-party DLL into a highly optimized, real-time rendering loop, you introduce friction. For DirectX games, NVIDIA has spent millions optimizing this friction. For OpenGL—which NVIDIA often treats as a second-class citizen for modern overlays—the penalty is much worse.
+Here is exactly why it slows your app down, and how you can find the articles discussing it.
+The Mechanics of the Penalty (Why it slows you down)\\
+. The "Middleman" Interception Overhead\\
+To draw its FPS counters or capture the screen, NVIDIA intercepts your core OpenGL calls (specifically the buffer swapping, like wglSwapBuffers). Every single time your application/app says "I am done drawing this frame, push it to the screen," that command doesn't go to the graphics card anymore. It goes to NVIDIA's overlay code first, which does its own math, injects its own textures, and then passes it to the driver. This introduces CPU overhead and ruins frame pacing (stutter).
+. Instant Replay VRAM Leeching\\
+Even if the user isn't actively hitting "Record," the overlay's "Instant Replay" feature is usually on by default. This means NVIDIA is silently copying your OpenGL Framebuffer into a background video encoder 60 times a second so the user can save the last 5 minutes of gameplay. This eats up your VRAM bandwidth and GPU cycles.
+. State Machine Corruption\\
+OpenGL is a massive state machine. When NVIDIA injects its overlay, it has to alter the OpenGL state to draw its UI, and then restore your state so your app can keep drawing. If their state-restore logic isn't perfect, it causes pipeline stalls.
+Where to Find the Articles and Proof\\
+Because this is a deep driver-level issue, you won't usually find mainstream articles on The Verge or IGN about it. The best documentation and rage-filled articles about this exact issue come from other engine developers and emulator creators.
+If you want to read up on it, use these specific search terms:
+Search for "Emulator NVIDIA Overlay OpenGL stutter": The developers of massive OpenGL/Vulkan emulators (like Yuzu, Ryujinx, and RPCS3) constantly battle this. You will find extensive GitHub issue threads where the devs explicitly tell users that the NVIDIA overlay is tanking their OpenGL performance and causing micro-stutters.
+Search for "wglSwapBuffers API Hooking Overhead": This will lead you to StackOverflow and GameDev.net articles where engine programmers discuss the exact millisecond penalties of third-party overlays hooking into the Windows OpenGL swap chain.
+Search for "OBS Game Capture vs Window Capture OpenGL": OBS Studio uses the exact same API hooking techniques as NVIDIA ShadowPlay to capture game footage. The OBS forums and wikis have brilliant, highly technical articles explaining the performance hit of hooking into an OpenGL context versus using standard Windows Desktop Duplication (WDDM).
 </blockquote>