Why does my flight simulator feel choppy at high FPS?

A flight simulator can feel choppy despite high FPS when frames arrive unevenly. The counter shows an average, not frame-time consistency. CPU main-thread spikes, scenery streaming, shader compilation, add-ons, a refresh-rate mismatch, or badly configured V-Sync, VRR or frame generation can all produce visible judder while the reported FPS remains high.

This applies across Microsoft Flight Simulator, X-Plane, Prepar3D, FSX and older simulators. The causes differ, but the useful measurement is always the same: how long each frame takes to appear.

What does high FPS but choppy motion mean?

High average FPS with poor motion means the frame times are inconsistent or the display cadence does not match them. A steady 60 FPS delivers one frame every 16.7 ms; a steady 30 FPS delivers one every 33.3 ms. If frames alternate between short and long delivery times, the average can remain high while camera pans and ground movement visibly hesitate.

A brief 80 ms pause may barely affect an FPS counter that averages results over a rolling interval, yet it is obvious to the eye. The same applies when one CPU core is saturated: overall CPU usage may show only 30 or 40 per cent even though the simulator's main thread cannot prepare frames consistently.

How do I diagnose uneven frame times?

The fastest diagnosis is to separate CPU, GPU, streaming and display problems in a repeatable test.

1. Create a fixed test. Use the same aircraft, airport, weather, traffic and camera movement. A demanding airport is more useful than an empty cruise because it reveals the performance level the simulator must sustain.
2. Display frame times. Use the simulator's developer performance display or a trusted graphics-driver overlay where available. Look for CPU and GPU frame time, not just average FPS.
3. Disable frame generation temporarily. Also turn off VR motion reprojection while testing. Otherwise the displayed FPS may include synthetic frames and hide the simulator's native frame rate.
4. Test a stock configuration. Temporarily disable third-party aircraft, scenery, traffic injectors, weather tools, plugins and external telemetry. In Microsoft Flight Simulator, this means testing without Community packages rather than deleting them.
5. Change one variable at a time. Lower resolution first. If performance barely changes, the CPU or streaming system is probably limiting the sim; if it improves substantially, investigate GPU-heavy settings.
6. Set a sustainable frame cap. Choose a rate the simulator can hold in the demanding test, not the maximum seen at altitude. Consistent spare capacity helps scenery loading and background simulation work complete without interrupting frames.

Repeated pauses in the same locations usually indicate scenery loading or an add-on. Spikes at precise time intervals point more strongly towards autosave, traffic updates, weather injection or a monitoring application. Stutter that appears only after a graphics-driver or rendering-mode change may be shader compilation; it should reduce after the same content has been displayed, whereas a persistent repeatable pause needs further investigation.

Why does frame generation look choppy?

Frame generation can raise the FPS counter without fixing the uneven native frames underneath it. Generated frames are inserted between frames rendered by the simulator; they do not remove a main-thread pause, scenery-loading hitch or delayed control update.

Use frame generation only after the native frame-time graph is reasonably stable. It can improve visual fluidity, but a reported 80 FPS composed from an uneven 40 FPS base may still feel worse than a stable native rate. Fast camera movement can also expose generated-frame artefacts, especially around cockpit frames, propellers and on-screen displays.

Should I cap FPS or use V-Sync or VRR?

A frame cap usually improves flight-simulator smoothness when it is set to a rate the system can maintain, but it must be matched to the display and synchronisation method.

• Fixed-refresh display: with V-Sync enabled, use a sustainable rate that divides evenly into the refresh rate. On a 60 Hz display, 30 or 60 FPS normally paces better than a constantly fluctuating 45–60 FPS. A 120 Hz display also accommodates 40 FPS evenly.
• VRR display: enable variable refresh on both the display and platform, then keep performance inside the supported VRR range. On PC, a cap slightly below the display's maximum refresh can prevent the system repeatedly hitting the upper boundary.
• No synchronisation: this can minimise latency, but tearing may make otherwise consistent performance look choppy during turns and camera pans.
• VR headset: target a stable native or reprojection cadence supported by that headset. Crossing repeatedly between full-rate and reprojected operation is usually more distracting than remaining at one stable mode.

Check that the operating system is actually driving the monitor at its intended refresh rate. We also recommend using one frame limiter at a time. Stacking the simulator limiter, graphics-driver limiter and an overlay limiter can create its own pacing problems.

Settings that improve frame pacing

The right settings depend on which component produces the longest frame time. Lowering everything can damage image quality without touching the actual bottleneck.

• CPU or main-thread limited: reduce terrain and object detail distance, AI traffic, ground vehicles, airport activity and other simulation-heavy features. Test a default aircraft because complex avionics and systems can consume substantial main-thread time.
• GPU limited: reduce render resolution or scaling, anti-aliasing cost, volumetric clouds, shadows, reflections and ambient occlusion. Our practical MSFS graphics-setting priorities explain which adjustments target the CPU and which target the GPU.
• VRAM or memory pressure: lower texture resolution and remove overlapping high-detail scenery. Exhausting VRAM can cause abrupt pauses as assets move between memory pools even when average FPS looks healthy.
• Streaming limited: compare online scenery with a default or offline scenery test. Do not repeatedly clear caches as a routine fix; rebuild or disable a cache only when the comparison indicates corruption or storage-related pauses.

Simulator-specific causes

Each simulator has characteristic bottlenecks that can narrow the search.

• Microsoft Flight Simulator 2020: photogrammetry, rolling-cache behaviour, dense airports, traffic and Community add-ons can produce spikes independently of average FPS. Use our focused MSFS 2020 stutter checklist when the problem involves micro-pauses rather than a continuously low frame rate.
• Microsoft Flight Simulator 2024: check CPU, GPU, VRAM and content-streaming behaviour separately. Our MSFS 2024 bottleneck diagnosis covers the settings appropriate to each limit.
• X-Plane: third-party plugins, complex aircraft and scenery loading are common sources of isolated frame-time spikes. Disable plugins by category and test default scenery rather than assuming the GPU is responsible.
• FSX, FS2004 and Prepar3D: these older engines are often constrained by one CPU thread. An unlimited frame-rate setting can consume time needed for scenery loading, so a sensible internal cap may feel smoother despite showing fewer FPS. Legacy users can follow our FS2004 frame-cap and graphics guidance.

Choose consistency over peak FPS

The best target is the highest frame rate your flight simulator can hold during the demanding parts of a flight. A locked 30 FPS with flat 33.3 ms frame times can look smoother than a counter swinging between 45 and 70 FPS, particularly when 30 divides cleanly into the display's refresh rate.

Once the frame-time graph is stable, re-enable add-ons, traffic, frame generation and online scenery one category at a time. The first change that restores the spikes identifies the component to tune or remove; chasing a higher headline FPS before fixing those spikes will not make the simulator feel smooth.