Learn why screen recording lowers flight simulator FPS and fix CPU, GPU, VRAM, encoder, frame-pacing and storage bottlenecks.
Screen recording reduces flight simulator FPS because the simulator and recorder compete for GPU time, CPU time, VRAM, memory bandwidth and storage throughput. Use hardware encoding, cap the simulator below its maximum frame rate, record at a lower resolution or frame rate, and remove unnecessary overlays or duplicate capture sources.
This applies to Microsoft Flight Simulator, X-Plane, Prepar3D, DCS World and older simulators such as FSX. Hardware encoding reduces the cost substantially, but capture is never completely free: frames still have to be copied, composed, encoded and written to storage.
What causes the FPS loss while recording?
The source of the slowdown is usually the resource that was already near its limit before recording began. Flight simulators often saturate one CPU thread or the GPU, so even modest capture overhead can push frame time over the edge.
| Symptom | Likely bottleneck | Best first change |
|---|---|---|
| FPS falls immediately and GPU utilisation is close to full | GPU rendering or capture composition | Cap simulator FPS, reduce output resolution and lower GPU-heavy settings |
| CPU usage rises sharply with a software encoder | CPU encoding or main-thread contention | Select a hardware encoder |
| Regular pauses occur as the recording grows | Slow or heavily used storage | Record to a fast local drive and avoid cloud-synchronised folders |
| Performance worsens in complex airports or aircraft | VRAM, traffic, scenery or avionics load | Reduce the relevant simulator settings and close GPU-accelerated applications |
| The simulator looks smooth but the video judders | Frame-pacing mismatch or encoder overload | Use a stable 30 or 60 FPS recording cadence |
A common mistake we see is changing the recording bitrate first. Bitrate mainly controls compression quality and file-writing demand; it does not release much rendering capacity unless the encoder or storage device is the actual bottleneck.
How can I record a flight simulator without losing FPS?
The best fix is to identify the limiting resource and leave it enough headroom before recording starts. Work through these changes one at a time so you can tell which one solved the problem.
- Measure a repeatable baseline. Load the same aircraft, airport, weather and camera view, then compare frame rate and frame time with recording off and on. Check the simulator’s performance display and the recorder’s rendering-lag, encoding-lag or dropped-frame statistics where available.
- Choose hardware encoding. Select an encoder labelled Hardware, NVENC, Intel Quick Sync or AMD hardware encoding rather than CPU-based x264 when the processor is already busy. A hardware encoder still uses some GPU resources, but it normally leaves far more CPU time for avionics, traffic and the simulator’s main thread.
- Start with 1080p at 30 FPS. This is a useful diagnostic setting for a demanding simulator. Move to 60 FPS or a higher resolution only after confirming that both rendering and encoding have headroom. FSX users can follow our practical OBS and Windows Game Bar capture settings.
- Cap the simulator frame rate. An uncapped GPU may sit near full utilisation, leaving nothing for capture composition. For 30 FPS video, a stable simulator rate of 30 or 60 usually produces cleaner pacing than an unrestricted rate that swings continuously.
- Use one capture method. Game or window capture is often lighter than recording the entire desktop, although some older simulators require a compatibility or display-capture method. Remove duplicate game, window and display sources; disable the preview after confirming the framing; and simplify browser overlays, webcams and filters.
- Check the recording drive. Keep adequate free space and avoid a slow external drive or a folder being synchronised while recording. A separate fast local drive can help when the simulator is also loading scenery or cache data from its installation drive.
- Reduce settings according to the bottleneck. Lower resolution, render scaling, clouds, shadows or anti-aliasing for a GPU limit; reduce traffic, object detail and scenery distance for a CPU limit. Our bottleneck-first flight simulator performance checklist covers the diagnosis, while MSFS users can apply settings that recover recording headroom in MSFS 2020 and 2024.
- Close competing capture and overlay tools. Disable unused replay recorders, GPU instant-replay features, animated desktop software and extra monitoring overlays. Do not assign Real-time process priority to the simulator or recorder; that can starve audio, input and system tasks.
Does lowering the recording bitrate improve FPS?
Lowering bitrate helps mainly when the encoder or recording drive cannot keep up. If the recorder reports rendering lag, reduce capture resolution, frame rate or scene complexity first; if it reports encoding lag, use a faster encoder preset or hardware encoding.
Do not cut bitrate so far that cockpit labels and small instruments become unreadable. Flight-simulator footage contains fine text and slowly changing scenery, so output resolution and a stable frame cadence usually matter more than chasing the smallest possible file.
Why is the recording choppy when simulator FPS is high?
A high average FPS can still produce choppy video when frame delivery is uneven or does not match the recording rate. A variable-refresh monitor may hide those fluctuations during flight, while the fixed 30 or 60 FPS recording exposes duplicated or dropped frames.
Check frame time rather than relying only on the FPS counter. If the simulator alternates between fast and slow frames, set a sustainable cap and test again. If stutters remain after recording is disabled, treat them as a simulator problem and use our steps for isolating flight simulator freezes and frame-time spikes.
Do I need a second PC or capture card?
Most simmers do not need a second PC once hardware encoding, sensible capture settings and an FPS cap are configured. A dual-PC setup becomes useful for high-resolution 60 FPS production with cameras, browser overlays and live streaming when the simulator already consumes nearly all available resources.
A capture card does not remove much load if the same PC still composites and encodes the result. It provides the greatest benefit when a separate machine performs those jobs, but that adds audio-routing, display and frame-synchronisation complications.
What about recording on Xbox or PlayStation?
Console capture is managed by the platform rather than a selectable PC encoder. On Xbox Series X|S—and with Microsoft Flight Simulator 2024 on PlayStation 5—use the built-in capture system, lower capture quality if the console exposes that option, and reduce simulator load if complex airports or weather trigger slowdowns.