Why does MSFS lose FPS with two monitors?

Microsoft Flight Simulator loses FPS with two monitors when it must render more pixels, draw a second 3D view or pop-out, or synchronise displays with conflicting refresh behaviour. Identify whether the GPU or main thread is limiting performance, then reduce the relevant extra workload and correct display-timing or background-app conflicts.

This applies to MSFS 2020 and MSFS 2024 on Windows PC. Simply connecting another screen should not cause a large FPS drop; what appears on that screen determines the real cost.

What causes MSFS FPS loss with two monitors?

The performance cost depends on what the second monitor is showing, not merely on the number of connected displays.

Pixel count rises quickly. A pair of 4K views requires twice as many rendered pixels as one 4K view, before accounting for extra geometry, glass displays, traffic or scenery. A separate 3D view also creates CPU work, so lowering resolution alone may not recover the lost performance.

How do I fix dual-monitor FPS loss in MSFS?

A controlled three-stage test will show whether the loss comes from Windows display handling, the second-screen application or additional MSFS rendering.

1. Create a repeatable baseline. Park the same aircraft at the same airport with unchanged weather, traffic and cockpit camera. Let scenery loading settle, then test with only the primary display enabled in Windows.
2. Enable the second display but leave it static. Extend the desktop without opening a browser, video, map, pop-out or second simulator view. A substantial drop at this stage points to refresh-rate, driver, compositor or GPU-routing trouble rather than MSFS scene complexity.
3. Add the intended second-screen content. Open one item at a time. This identifies whether the loss begins with a browser, instrument pop-out, wide viewport or separate camera.
4. Check the limiting component. Use the simulator's developer FPS display and watch for Limited by GPU or Limited by MainThread. GPU-limited systems benefit from fewer pixels, lower render scaling, lighter clouds and shadows, or an available upscaler. Main-thread-limited systems need less traffic, lower terrain detail, fewer independent views or reduced avionics refresh. Our GPU-versus-main-thread graphics-setting baseline explains which controls target each bottleneck.
5. Reduce the extra viewport first. If the second monitor carries a 3D view, lower that output's resolution where the chosen display method permits it. If MSFS spans both screens as one large surface, reduce the combined resolution or render scaling. Lowering the resolution of a screen showing only a static desktop will achieve little.
6. Remove competing GPU work. Pause videos, animated maps, live wallpapers, recording tools and hardware-accelerated browser windows. Test browser hardware acceleration both ways: disabling it can help a GPU-limited system but may transfer work to the CPU and worsen a main-thread limit.
7. Check monitor connections. On a desktop PC, connecting both monitors to the same discrete GPU usually avoids cross-adapter copies. Plugging the second display into the motherboard does not divide MSFS rendering between GPUs. Laptop display routing is hardware-dependent and may not be changeable.
8. Set a frame limit last. A cap below the FPS the system can sustain can improve consistency, but it does not restore missing rendering capacity. Apply it only after correcting the underlying bottleneck.

Are MSFS pop-out instruments expensive to render?

Instrument pop-outs can reduce FPS even though they do not show another outside view. MSFS must continue updating the avionics while Windows composites each detached panel as a separate window.

Close panels you are not using rather than moving them off-screen, and select a lower glass-cockpit refresh option if the simulator or aircraft provides one. Resize pop-outs only as large as necessary. Our guide to reducing detached-panel and avionics overhead covers this specific case in more detail.

Should both monitors use the same refresh rate?

Matching refresh rates is a useful diagnostic step, but it is not an absolute requirement for dual-monitor MSFS. Mixed-refresh displays can produce uneven pacing when the second monitor contains video, animation or another accelerated window, even when the FPS counter looks reasonable.

• Confirm that each monitor is running at its intended refresh rate in Windows Advanced display settings.
• Temporarily set both displays to the same refresh rate and retest.
• If they cannot match, keep animated content off the secondary screen and optimise frame timing for the primary monitor.
• Test V-Sync, adaptive sync and frame limits one change at a time. NVIDIA users can follow our MSFS frame-pacing and G-SYNC configuration advice.

A lower FPS reading accompanied by high GPU utilisation usually indicates genuine rendering load. Stutter with spare GPU capacity more often points to the main thread, Windows compositing, refresh interaction or a background application.

Should I stretch MSFS or use a separate second view?

A stretched view normally costs less CPU, while a separate 3D view gives more accurate side-view geometry at a higher rendering cost. Choose stretching when FPS matters more than perspective correction; choose a separate viewport when the second monitor must represent a distinct viewing direction.

Both methods increase total pixel load, but only the independent view must build another camera perspective. The same display-matching and pixel-count principles described in our multi-view monitor configuration guidance also apply to a two-screen installation.