OBS lists Counter-Strike 2 and Destiny 2 among games that do not allow its Game Capture hook. Use the documented windowed or borderless route with Window Capture and verify the actual match footage.
Use a borderless or windowed game and a targeted Window Capture when OBS documents that Game Capture cannot hook the title.
In this guide
Before you start
- Windows and the game running with non-private test content.
- Access to its display-mode settings and an OBS test scene.
Use the documented capture path for the title
When a game blocks the capture hook, a black Game Capture source is not necessarily a broken OBS installation. OBS’s game troubleshooting page specifically identifies Counter-Strike 2 and Destiny 2 and recommends a windowed or borderless workflow with Window Capture.
Keep the workaround narrow. You do not need to disable security features or install an unofficial hook to follow the documented route. Record the game version and display mode in your notes so a future change can be compared with a known arrangement.
Prepare the window you actually want to show
Enter the game itself and choose a windowed or borderless display mode appropriate for the documented capture method. Use a practice or private session where possible. A launcher, loading screen and active game may not behave identically, so the test needs to reach actual movement.
Create a clearly named capture source for this route instead of layering it over several failed experiments. Keep private windows and notifications out of the rehearsal. Although a targeted window is narrower than desktop capture, the game’s own menus and overlays can still contain information you do not want to publish.
Build the targeted Window Capture
Select the active game window
Add Window Capture and select the running game. Begin with the default capture method and verify the title points to the game rather than its launcher.
Look for: Preview contains the game window’s actual picture.
Check the window boundary
Inspect the image for borders, unwanted client areas or scaling. Fit the source to the intended scene while preserving the game’s aspect ratio.
Look for: The composition includes the intended game region without stretching it.
Record a realistic passage
Play a short sequence with movement, menus and one focus change. Stop recording and inspect the file instead of judging only a paused preview.
Look for: The saved sample confirms the route works during the actions expected in the real session.
Change capture settings only when the test gives a reason
If the selected window is still blank, check that it is open, active and the correct target. OBS documents capture-method alternatives in Window Capture, but a method change should be a specific comparison. Keep the initial setting in your notes and revert any experiment that does not improve the result.
If the game updates or changes its window identity, reselect the target and repeat the same short passage. Avoid treating a renamed window as proof that the entire configuration needs rebuilding. The first useful question is whether the source is still attached to the intended process and window.
Check sound and performance independently
The window route establishes picture capture. Test the game audio through its chosen capture source and recording track separately, especially if you previously used an application-specific audio route tied to another process. Listen for one game sound rather than duplicate desktop and app capture.
Keep the final configuration small and save the tested source. If the picture stutters under full load, investigate scene rendering and output performance with the same sample. A compatible capture path and a sustainable workload are separate requirements, and both should be demonstrated before a real broadcast.
Still stuck?
The window source captures the launcher instead of the match.
Select the active game window after entering a practice session, then repeat the recorded movement test.
Sources & references
Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.
- OBS — Game Capture Troubleshooting ↗Checked 2026-11-04
- OBS — Window Capture Sources ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗