How I Record Clean FC 24 Gameplay at 4K 60fps Without Commentary
I've been making blind playthrough recordings for years across various titles, and EA Sports FC 24 has been one of the smoother ones to work with when it comes to output quality. The catch is that the game doesn't make it easy to hit consistent 60fps at 4K without tweaking a few things most people overlook. Your GPU matters far more than your CPU here. I run this on an RTX 4080, and even then I have to make specific compromises. You need at least 12GB of VRAM to handle the upscale reliably without stuttering in crowded stadiums. The lighting passes on the newer EA engine choke on lower memory cards once you push beyond 1440p. You'll also want OBS Studio set up with NVENC encoding, or if you have an AMD card, AMF VCE works too. Both encode well at 4K 60fps, but the quality ceiling differs. NVIDIA still gives cleaner results with fewer macroblocking artifacts during rapid camera movements, which happens constantly in FC 24 matches.
Ea Fc 24 Gameplay 4K 60fps Blind Playthrough
In-Game Settings That Actually Matter
Start by going into the graphics menu. Set resolution to your native panel resolution, not a lower one you plan to upscale later. The game's internal renderer does a better job with motion clarity at native than any upscaler will. Motion blur has to be turned off completely. It looks fine in trailers but destroys readability in a recording and makes the footage feel muddy at 60fps regardless of bitrate. Set the frame rate target to 60fps locked. If your monitor supports 120Hz, do not set it to 120. The in-game camera interpolation at 120fps adds a layer of ghosting that shows up clearly in screen recordings. 60fps locked looks cleaner and plays back fine on any platform. Turn off vertical sync inside the game. You want the frames to queue naturally rather than the game trying to synchronize with your display, which can cause micro-stutters during transition cuts between gameplay and menu navigation.
Recording Software Configuration
In OBS, switch your video output resolution to match your game resolution exactly. Do not try to do a resolution conversion on the fly unless you have a second machine handling the encoding. A single machine rescaling from 1440p to 4K while simultaneously running the game and encoding introduces enough overhead to drop frames inconsistently. For the encoder, use NVENC H.264 or HEVC depending on your target platform. H.264 stays compatible everywhere but needs a higher bitrate for clean 4K. I run it at 50 megabits per second for H.264 and about 35 for HEVC. Anything below 40 on H.264 and you will see the compression artifacts during goal celebrations where the crowd animation gets heavy and chaotic. Set your keyframe interval to 2 seconds. This is one of those small settings that most people ignore, but it matters a lot for long match recordings. A longer keyframe interval reduces file bloat without affecting playback quality noticeably.
Get the Full Details
I record directly to an NVMe drive, not a mechanical hard drive. Writing 4K 60fps footage to a spinning disk will bottleneck the stream after about twenty minutes and cause dropped frames that manifest as subtle freezes in the final video. Your drive needs to sustain at least 2000 megabytes per second write speed to stay comfortable.
The Problem I Hit and How I Worked Around It
About six months into making these videos, I started noticing that cutscenes during gameplay transitions would occasionally soft-lock my recording. Not crash, just freeze while audio kept playing for about eight seconds before the game caught up. This happened during player substitution cutscenes and referee VAR checks specifically. The engine seems to prioritize loading the player model animation over the encoding buffer, and the buffer overflows. My workaround was simple: I enable hardware acceleration in the OBS source properties so the cutscene scenes get their own encoding thread, separate from the main gameplay feed. It is not a perfect fix. The first half second of a cutscene can still stutter slightly, but the recording no longer locks up. If you are seeing the same behavior, check your OBS scene layout and make sure your game capture source is set to grab exclusive fullscreen mode rather than windowed or borderless. Another issue I ran into is audio desync creeping in during long matches. After about forty minutes of continuous recording, the audio would drift about 150 milliseconds ahead of the video. This is a known issue with the NVENC encoder when the GPU thermal throttles during extended encoding sessions. I solved it by adding a small fan curve adjustment in my GPU utility and capping the max temperature target to 72 degrees Celsius instead of letting it run unchecked. The encoder maintains consistent clock speeds and the sync holds for full ninety-minute matches now.
Common Pitfalls Most Beginners Miss
Most people try to record directly from the console version if they are playing on PlayStation or Xbox. The consoles cap output at 30fps in most game modes, and the 4K mode comes with dynamic resolution scaling that drops to around 1080p internally during heavy scenes. You will end up with a blurry upscaled mess. PC is effectively the only clean path to genuine 4K 60fps blind playthrough footage on FC 24. Another thing: do not use Replay Mode to generate your footage. Replay mode in FC 24 exports at a lower resolution than live gameplay. The replay engine is separate and renders at roughly 1440p internally before outputting. You will think you are getting 4K but the detail falls apart when you look at stadium textures and crowd density in the final upload. Match length also matters more than you might expect. Recording a full ninety-minute match plus extra time generates enormous files. A typical sixty-minute blind playthrough at my settings runs around eighty to one hundred gigabytes depending on how many cutscenes and substitutions happen. Plan your storage accordingly before you commit to a full season run.
When This Approach Fails Completely
If you are on integrated graphics or a GPU with less than 8GB of VRAM, this method will not work for you at all. The game will not sustain 60fps at 4K in the first place, so recording at that resolution just captures a struggling framerate. In that case, record at 1440p instead. The visual difference on screen is minimal and the file sizes become manageable. You lose the literal 4K label but gain a smooth watchable recording. If you are trying to record with commentary layered in real time, forget it. Running voice processing alongside 4K 60fps encoding pushes the system to its limit. Record the gameplay clean first, then add your commentary pass afterward. The workflow takes longer but the output quality stays consistent throughout.
Quick Settings Checklist
Resolution: native display resolution, no upscaling Frame rate target: 60fps locked, not 120 Motion blur: off
Vertical sync: off OBS encoder: NVENC H.264 at 50Mbps or HEVC at 35Mbps Keyframe interval: 2 seconds
Output drive: NVMe SSD Exclusive fullscreen capture mode enabled GPU thermal target capped at 72C for long sessions
That is about it. The process is not complicated once you know what settings fight against you. The main thing is patience with the initial configuration and accepting that you cannot do everything in one pass without sacrificing quality.
