Baldurs Gate 3 Gameplay Reaction With Facecam

Setting Up a Facecam Overlay for Baldur's Gate 3 Recording

I've done this setup dozens of times now, and every single person who asks me about it ends up hitting the same wall within the first twenty minutes. The core problem isn't the software — it's how the game handles its own overlay layer and then collides with whatever webcam solution you're trying to run on top of it.

Baldurs Gate 3 Gameplay Reaction With Facecam

The basic workflow is straightforward: you capture your gameplay through OBS or XSplit, run your webcam feed through the same program, and layer them together for export. The tricky part is making sure the facecam doesn't get swallowed by Larian's own streaming overlay system, which sits on top of the DirectX 11 pipeline at a different priority level than most capture cards expect.

Here's what actually works. I use OBS Studio with the Window Capture source set to the game window, not the full desktop. Game mode capture breaks the facecam sometimes, and I learned that the hard way after spending three hours troubleshooting a black screen that turned out to be a simple mode conflict. You want to go to your Sources panel, add a Window Capture, and then select the Baldur's Gate 3 window directly. Make sure the game is running in Borderless Windowed mode, not Fullscreen Exclusive. This is non-negotiable. Fullscreen mode will fight you for the capture handle and you'll end up with either a black feed or a 30-second delay before the image appears. For the webcam itself, you're better off using a hardware-capture device if you have one. A decent USB 3.0 capture card like the Elgato Cam Link or even a budget VGNB unit gives you a completely separate video pipeline that doesn't interfere with the game capture at all. If you're running the webcam directly through OBS as a Video Capture Device source, you need to make sure the resolution matches between the two. I usually set the game to 1920 by 1080 and the webcam to the same. Mismatched resolutions cause the facecam to stretch or pillar-box inside the frame, and it looks amateurish. Fix it at the source, not in the scaling filters. One specific thing nobody mentions: Baldur's Gate 3's in-game camera zoom and pan settings will interfere with your facecam positioning if you're using a green screen or chroma key filter. When the game's camera zooms in during dialogue closeups, the perspective shift between your face and the game creates a disconnect that makes the chroma key bleed at the edges. The workaround is simple — don't use chroma key for this game. Use the Alpha Blend filter in OBS instead, which composites the webcam feed more forgivingly. It's slightly heavier on CPU but it looks infinitely better in practice.

Audio is another place where people mess this up. The game has its own voice track, your microphone has ambient room noise, and they sit on different frequencies. If you don't apply a noise gate to the mic channel, the background hum from your computer fan comes through loudly during quiet conversation scenes. Set your noise gate threshold to around -40dB and the expansion to 6dB. This means the mic is essentially muted unless you're actually speaking, which keeps the audio clean without killing natural cadence. If you're recording for YouTube and want the facecam to be clickable or interactive, you're going to run into a limitation. OBS stream output doesn't support clickable overlays natively. Some people try using Streamlabs or custom plugins, but those tend to introduce latency spikes of 200 milliseconds or more. The honest answer is that clickable overlays don't work reliably with BG3 because the game's rendering loop prioritizes gameplay frame delivery over any overlay processing. If you need interactivity, your only real option is to produce a two-window layout in post and let YouTube's end-screen features handle the linking. For the actual recording quality, I recommend 60 frames per second for the game capture and 30 for the webcam. There's no point pushing the facecam to 60fps because most webcams max out around 30fps anyway, and you'll just be generating unnecessary disk I/O. Your bitrate should be set to 12,000 kilobits per second if you're encoding in H.264. Anything lower and the game's particle effects — particularly the spell effects in combat scenes — will artifact badly. I've seen recordings at 8,000 kbps turn fireball animations into pixel soup. That's the difference between watchable and unwatchable.

The biggest mistake I see is people trying to use built-in Windows Game Bar or Xbox Game Bar for capture. Those tools literally cannot handle facecam overlays in the same pipeline as the game. You'll get the gameplay recorded fine, but the webcam feed will be missing entirely or appear as a frozen frame. There's no setting to fix this. It's a architectural limitation of how those built-in tools layer their capture sources. Stick with OBS or XSplit and you won't have this problem. Finally, save your scene presets. I have one preset configured specifically for BG3 with the Window Capture source locked to the game, the webcam positioned in the bottom right corner at 40% scale, and the audio filters already applied. Setting this up from scratch for each recording session takes about twelve minutes. Having it pre-saved cuts that down to about forty-five seconds. That matters when you're working on content that needs to go out on a schedule.