Running NBA 2K24 on Hard with a facecam on screen isn't as simple as you'd think
I've been doing this for about three years now, mostly on YouTube and occasionally on Twitch. The short version: you need to balance CPU/GPU load between the game, the streaming software, and the webcam feed, and if you don't get it right you'll either look terrible on camera or your frames will drop during clutch moments. I learned that the hard way, during a stream where my facecam started stuttering at the exact moment I needed to make a free throw with the game on the line. Here's how it actually works in practice. NBA 2K24 on MyCareer or MyLeague mode running at high settings will consume roughly 60-70% of a single GPU core on most modern cards. When you add OBS or XSplit on top with a 1080p webcam feed, you're pushing that into territory where frame times can jump from 16ms to 33ms during transition sequences. The game renders differently depending on whether you're in the locker room, on the court during a fast break, or in the crowd camera. I noticed that the cutscenes and menu screens are actually more demanding than gameplay in some cases because they have higher resolution textures loaded in memory. The common mistake people make is running the game at Ultra settings while also encoding at 1080p30 with a facecam. You should drop the game to High or Medium and run the webcam at 720p30 instead. This usually gives you enough headroom to keep the game stable while still looking presentable on camera. I tried the other way once and my stream quality dropped so badly that people couldn't tell whether I was celebrating or just having a seizure, which isn't great for viewer retention.
One specific thing that catches people out: the game's temporal anti-aliasing tends to conflict with webcam compression. When you enable TAA in-game while also having a facecam running through a hardware encoder, you can get weird artifacting that makes your face look like it's melting on screen. The workaround is to either disable TAA in the graphics settings or switch to a software encoder for the stream. I found that disabling TAA actually improved both the visual quality and the performance, which was unexpected since most people assume it's purely a quality feature. Hardware considerations matter more than most guides admit. A Ryzen 5 5600X with an RTX 3060 can handle this setup fine at 1080p, but a Ryzen 3 3100 with a GTX 1650 will struggle even at Medium settings. If you're on a laptop, you're basically out of luck unless you're willing to run the game at 720p internal resolution and stretch it to 1080p for the stream. I made this mistake early on and spent $400 on a second monitor just to run the game fullscreen on one screen and OBS windowed on the other, which cut my frame drops by about 60% compared to trying to run everything on a single display. The real bottleneck is usually RAM, not GPU. NBA 2K24 loads a lot of audio and video assets into memory during gameplay, and if you're also running a webcam feed through a software encoder you'll run out of RAM before you run out of VRAM on most cards. 16GB is the absolute minimum; 32GB will make this setup feel smooth even when you have Discord, Chrome with tabs, and a facecam running simultaneously. I upgraded from 16GB to 32GB on my main machine and saw about a 15% improvement in average frame times during transition sequences, which was enough to make the difference between a watchable stream and something I wouldn't want to share with anyone.
Audio routing is another thing nobody mentions. If you're using a separate microphone alongside your facecam, you need to make sure the game audio doesn't bleed into your mic input. This usually means using a physical audio interface or at least enabling noise gate in your streaming software. I spent about two weeks trying to fix this before realizing that my players were complaining they could hear my keyboard clicks during quiet moments in the game, which was more distracting than the actual gameplay. The fix was enabling a noise gate set to around -40dB with a fast attack time, which cut the keyboard bleed by about 80% compared to not having any gate at all. If you're streaming to multiple platforms simultaneously, you're going to need a much more powerful machine. The game alone will consume roughly 60-70% of a single GPU core, and when you add dual-encoding with a facecam on each stream you'll need at least an RTX 3070 or better to keep things stable. I tried streaming to both YouTube and Twitch at the same time with a GTX 1080 Ti and ended up with about 20fps drops during every playoff sequence, which was more embarrassing than anything I've experienced in my life. The only real solution was upgrading to an RTX 3080 and running the streams at 720p30 instead of 1080p60, which cut my encoding errors by about 70% compared to trying to push both at maximum quality. The webcam choice matters more than most people think. A Logitech C920 will look fine at 720p30, but a C920 at 1080p30 will start showing compression artifacts that make your face look like it's been through a meat grinder. I found that running the C920 at 720p30 actually looked better than 1080p30 when compressed through OBS, which was counter-intuitive since most people assume higher resolution always looks better. The reason is that the C920's sensor is only 2MP, so 1080p is just interpolation and doesn't actually add any real detail.
Get the Full Details
I'll be honest about the limitations here. This setup will not work well on anything less than a mid-range PC from 2020 or later. If you're on an older machine, you'll need to either run the game at 720p internal resolution or skip the facecam entirely. I tried running this on my old i5-4590 with a GTX 970 and ended up with about 15fps drops during every free throw sequence, which was more frustrating than anything I've experienced in my life. The only real solution was upgrading to a Ryzen 5 5600X with an RTX 3060, which cut my frame drops by about 85% compared to trying to run everything on the old hardware. There's also the issue of monitor refresh rate. If you're playing on a 60Hz monitor while also trying to stream at 30fps with a facecam, you'll notice that the game feels less responsive than it should. This usually means either buying a 144Hz monitor or accepting that your stream quality will be lower than your local gameplay. I made this mistake early on and spent $200 on a 144Hz monitor just to realize that my stream viewers were complaining they could see the difference between my local 60fps and the streamed 30fps, which was more annoying than anything I've experienced in my life. The fix was running the game at 120fps internally while streaming at 30fps with a facecam, which cut the perceived input lag by about 50% compared to not having the extra headroom. I won't recommend this for casual players. If you're just trying to record some gameplay for fun, you can probably get away with running the game at High settings and using a built-in webcam without any encoding software. But if you want to stream or record consistently with a facecam on screen, you'll need to invest in proper hardware. I tried this on my old laptop with a built-in webcam and ended up with about 10fps drops during every transition sequence, which was more embarrassing than anything I've experienced in my life. The only real solution was building a proper desktop setup, which cost me about $800 but has paid for itself in terms of stream quality and viewer engagement.
