Setting Up a Facecam Stream for Man 2
I've recorded enough walkthrough content to know that getting the facecam right takes more than just slapping a webcam in the corner of your screen. Most people underestimate the audio sync issues, lighting problems, and performance hits until they're already midway through a recording and realize half their footage is unusable. Here's how to actually do it without losing your mind. First, let me be clear about what you're working with. Man 2 (Manhunt 2) runs fine on modern hardware, but the game itself isn't exactly optimized for capture overhead. If you're running OBS or Streamlabs alongside it, you're looking at roughly a 10 to 15 percent frame time hit depending on your encoding settings. That doesn't sound like much until you're trying to maintain consistent 60fps for a smooth recording. For the facecam, I use a Logitech C920 or similar mid-range webcam at 1080p and 30fps. The reason I don't push to 60fps is simple: at 30fps, your encoding bitrate budget goes entirely toward the gameplay feed instead of being split between two streams. A facecam doesn't need 60fps unless you're doing fast-moving reaction content, which this genre of game doesn't really call for. The lighting on your face matters far more than frame rate.
Recording Setup and Configuration
Launch the game first, then add your capture source. If you're using Game Capture in OBS and it comes up black, the anti-cheat or overlay blocking is the culprit. The workaround I found was to run the game in windowed borderless mode at a custom resolution matching your monitor's native aspect ratio, then capture that window directly instead of using full-game capture. This adds maybe two seconds to your loading times and eliminates the black screen issue entirely. Set your facecam as a separate source above the game capture. Position it in the lower-right or lower-left corner, keep it around 25 to 30 percent of the screen width so it's visible without dominating the frame. I've seen beginners make it way too small and then regret it during editing when they can't read their own reactions. Audio is where most people mess this up. You need two separate audio tracks: one for game audio and one for your microphone. Route them separately in OBS so you can adjust levels independently during post. Set your mic gain so your normal speaking volume hits around minus twelve decibels on the meter. If it's hitting zero or clipping, you'll get distortion that no amount of filtering will fix cleanly. I learned this the hard way on my first three walkthroughs before I started monitoring levels properly.
Encoding Settings That Actually Work
Use x264 encoding if you're recording locally rather than streaming live. It produces significantly smaller file sizes at equivalent quality compared to NVIDIA NVENC or QSV encoders. Set your preset to veryfast, bitrate around 6000 to 8000 kbps, and a keyframe interval of 2 seconds. This gives you clean playback and makes scrubbing through the timeline in your editor much easier. Record to MKV format, not MP4. If your system crashes or OBS crashes mid-recording — and it will, especially when running a game alongside capture software — MKV preserves everything you've recorded so far. You can remux to MP4 afterward with a tool like MKVToolNix, which takes about ten seconds and won't re-encode anything. I made the mistake of recording in MP4 format on a twenty-minute session once. OBS froze during a particularly intense stealth section. The entire file was corrupted. Never again.
Get the Full Details
A Real Problem I Faced
During my second recording session, I noticed that my facecam was subtly desynchronizing from the gameplay audio over the course of a long playthrough. It started around the five-minute mark and got worse from there. The issue turned out to be a mismatch between the game's internal audio sampling rate and my microphone's reported sampling rate in OBS. The game was outputting at 44100Hz while my mic was locked to 48000Hz, and the tiny drift accumulated into a noticeable gap by the end of a chapter. The fix was straightforward but not obvious if you don't know what to look for. I went into my Windows sound settings, set both the game output and microphone input to the same sample rate — I chose 48000Hz since that's the standard for video work — and then confirmed OBS was set to 48000Hz in its global audio settings. After that, the drift disappeared completely. I didn't know about this issue until I'd already wasted a full day of recording trying to fix it in post with manual sync points, which is a miserable experience.
Lighting and Camera Tips
Your face needs to be evenly lit. A single light source from above or behind creates harsh shadows that make your facecam look like an afterthought. Two soft light sources at roughly forty-five degree angles on either side of your camera work well. I use cheap LED panels from Amazon for this — nothing expensive. The difference between good lighting and bad lighting is usually the gap between viewers stopping to watch versus scrolling past within two seconds. Don't mount your webcam on top of your monitor. The downward angle looks stiff and unflattering. Position it at eye level or slightly below, pointing up just a fraction. It's a minor detail but it shows in the final product.
Performance Considerations
If you're running on a mid-range system, you may need to lower in-game settings to compensate for the capture overhead. Turn off motion blur, lower shadow quality, and reduce particle effects. These are the first things to go and they have the least visual impact on gameplay clarity while freeing up GPU headroom for encoding. Man 2 is an older title, so even integrated graphics can handle low settings at 720p if you need to prioritize smooth recording over visual fidelity. Closing background applications is standard advice, but it's worth emphasizing specifically for this type of setup. Browser tabs, Discord overlays, and RGB software can silently consume enough resources to cause frame pacing issues that aren't obvious until you watch the recording back and notice micro-stutters.
Post-Recording Workflow
Once you've finished recording, review the footage before exporting. Check for moments where the facecam might be blocked, where your audio dips too low, or where technical issues snuck in. Fixing these in post is faster than re-recording an entire chapter. Trim the dead air at the beginning and end — that initial startup period where you're adjusting your camera or checking your mic levels. Viewers won't wait for it. When uploading, the video quality settings matter. Use a high bitrate for the upload if your platform allows it. YouTube recompresses everything, and starting with a cleaner source file means the final result looks noticeably better. There's a noticeable difference between uploading at 1080p with a low bitrate and uploading at the same resolution with a proper bitrate setting.
What This Approach Won't Fix
This method doesn't solve every problem. If your hardware struggles to run the game at acceptable frame rates while encoding, no amount of tweaking will change that. You'd need to upgrade your GPU or accept lower recording quality. Similarly, if your internet connection is unstable, live streaming becomes unreliable regardless of your local encoding settings. In those cases, recording locally and uploading later is the only viable path. Also, the facecam adds a personal presence that some viewers appreciate and others find distracting. There's no universal answer here. Pay attention to what your audience responds to rather than assuming more facecam presence always equals better engagement. I've had people subscribe after seeing a facecam segment and others leave comments saying they prefer game-only footage. Both reactions are legitimate, and neither is something you can predict in advance.
