Fix OBS Studio Game Capture Overlay Conflicts

When streaming or recording with OBS Studio, the Game Capture source can conflict with third-party software overlays—such as those from Discord, Steam, GeForce Experience, or RivaTuner. These conflicts often result in a black screen, severe FPS drops, or game crashes because multiple programs are trying to hook into the same graphics rendering pipeline simultaneously. This guide provides direct, actionable solutions to resolve these overlay conflicts and restore smooth capture performance.

Disable Unnecessary Third-Party Overlays

The most effective way to resolve a conflict is to disable the overlay in the conflicting application. Identify which background programs are running and disable their overlay features:

• Discord: Go to User Settings > Game Overlay, and toggle off “Enable in-game overlay.”
• GeForce Experience: Open the application, go to Settings (gear icon), and toggle off the “In-Game Overlay” option.
• Steam: Go to Steam > Settings > In-Game, and uncheck “Enable the Steam Overlay while in-game.”
• RivaTuner Statistics Server (RTSS) / MSI Afterburner: Set the “Application detection level” to “None” for the specific game, or close the application while streaming.
• AMD Radeon Software: Go to Settings > General, and disable the “In-Game Overlay” under the Preferences section.

Adjust OBS Game Capture Properties

OBS Studio includes built-in settings designed to manage how it interacts with other hooks. You can adjust these settings to prevent OBS from fighting other applications for hook priority:

1. Open OBS Studio and locate your Game Capture source in the Sources dock.
2. Double-click the source to open its Properties.
3. Scroll down and uncheck Capture third-party overlays (such as Steam). This prevents OBS from attempting to record the overlay layer, reducing resource conflicts.
4. Ensure Use anti-cheat compatibility hook is checked. This is required for most modern games and helps OBS hook into the game engine safely.
5. Click OK to save the changes.

Run OBS Studio as Administrator

Running OBS Studio with administrator privileges allows it to bypass certain permission barriers and hook into the game’s graphics API more reliably than third-party background applications.

1. Right-click on the OBS Studio shortcut on your desktop or Start menu.
2. Select Properties.
3. Go to the Compatibility tab.
4. Check the box that says Run this program as an administrator.
5. Click Apply and then OK.

Change the Hook Rate in RivaTuner (RTSS)

If you must use RivaTuner Statistics Server for hardware monitoring alongside OBS, you can delay its hook so it does not conflict with OBS during game startup:

1. Open RivaTuner Statistics Server.
2. Hold the Ctrl key and click the Add button in the bottom left to open the hidden properties, or locate the Global profile.
3. Look for the Injection delay setting (measured in milliseconds).
4. Set the delay to 15000 (15 seconds). This gives OBS Studio enough time to hook into the game first before RTSS attempts to hook.

Use Window Capture as a Workaround

If the game capture source continues to conflict despite disabling overlays, switching the capture method in OBS is a highly reliable workaround:

1. In OBS, hide or delete your Game Capture source.
2. Add a new Window Capture source.
3. Select your game from the Window dropdown menu.
4. Set the Capture Method to Windows 10 (1903 and up) or Graphics Capture. This capture method bypasses direct hook injection entirely, eliminating overlay conflicts at the cost of slightly higher CPU/GPU overhead.