Find out why MSFS pop-out cockpit panels reduce FPS and how to minimise the hit with fewer windows, lower refresh rates and better frame pacing.
Pop-out cockpit panels reduce FPS in Microsoft Flight Simulator because each detached display becomes another rendered and composited window. Glass-cockpit graphics must still update, while Windows and the GPU present extra surfaces, sometimes across monitors with different refresh rates. Minimise the loss by opening fewer panels, lowering avionics refresh and preserving CPU/GPU headroom.
This mainly concerns the PC versions of Microsoft Flight Simulator 2020 and 2024. Consoles do not use the normal Windows desktop workflow for placing detached instrument windows on separate displays.
Why do pop-out cockpit panels affect performance?
A detached instrument is not a free copy of the cockpit texture. Microsoft Flight Simulator must draw its display into another render or UI surface, update the avionics behind it and pass the resulting window through the Windows desktop compositor.
The cost depends heavily on the aircraft. A basic analogue gauge normally demands less than a large navigation display containing a moving map, terrain, weather and traffic. Aircraft-specific avionics can also perform extra calculations at every refresh, so two panels of similar size may have very different effects.
Moving a panel out does not usually stop the original cockpit display from being rendered. Some aircraft can blank or disable the original screen, but that only saves performance if the aircraft's implementation actually suspends its rendering or updates.
| Observed behaviour | Likely limitation | Best first test |
|---|---|---|
| Each additional panel causes a smaller FPS loss | Avionics updates and extra rendered surfaces | Open panels individually and keep only the essential display |
| FPS drops to a stable fraction when the first panel opens | VSync, frame presentation or compositor timing | Test without VSync, then use a sustainable frame cap |
| The loss becomes worse on another monitor | Mixed refresh rates, scaling or cross-GPU presentation | Test the panel on the main display and match monitor settings |
| The simulator reports a main-thread limit | Avionics, traffic and simulation work competing for CPU time | Reduce avionics refresh, traffic or CPU-heavy detail |
| The simulator is GPU-limited | Extra surfaces added while the GPU is already saturated | Reduce render scaling or another GPU-heavy setting |
How can I identify what is causing the FPS loss?
Measure the effect one panel at a time under an unchanged test condition. This separates the panel's real cost from normal variation caused by scenery, weather, traffic and camera movement.
- Establish a baseline. Use the same aircraft, airport, cockpit view and weather, then let the frame rate settle.
- Open one instrument. Record the immediate change before detaching another. Our panel-detaching and window-management instructions explain the normal controls and how to test panels separately.
- Check the active limiter. Use the simulator's performance display briefly to see whether the main thread or GPU is holding back the frame rate. The exact labels and presentation differ between MSFS versions.
- Move the same window. Compare it on the main monitor and the intended secondary display without changing its size.
- Close it completely. Do not merely minimise it; a minimised or obscured panel may continue updating. Confirm that FPS returns close to the baseline.
If opening the first panel causes an almost exact step down rather than a gradual loss, test frame synchronisation before reducing visual quality. VSync and multiple window presentation can force the simulator towards a lower refresh-rate interval even when the hardware has spare processing capacity.
How do I minimise the pop-out panel FPS impact?
The largest reliable improvement comes from reducing the number and update rate of detached displays, then creating enough headroom for their remaining workload.
- Open only the displays you use. Close hidden, duplicate and minimised pop-outs rather than leaving them running throughout the flight.
- Lower the avionics refresh setting. Look for a glass-cockpit or avionics screen refresh option in the simulator or aircraft. Wording varies by version and aircraft. A lower rate reduces display smoothness but can relieve both CPU and GPU pressure.
- Leave rendering headroom. An uncapped simulator can consume nearly all available GPU time before a panel opens. Use a stable limit below the frame rate your system can sustain; our guidance on choosing an appropriate MSFS frame cap covers the available approaches.
- Adjust the correct bottleneck. When GPU-limited, reduce render scaling, clouds or another costly graphics option. When main-thread limited, reduce traffic, terrain detail or avionics refresh instead. Lowering random settings rarely helps.
- Keep panel windows practical. Reducing their pixel dimensions can lower drawing and compositor work, although it does not remove the avionics calculations. Avoid oversized panels when a smaller readable window will do.
Do not expect blanking the instrument inside the 3D cockpit to guarantee a gain. Some aircraft keep calculating and rendering it internally, while others provide their own display-quality or refresh controls that work better than the global setting.
Why can a second monitor make the drop worse?
A second monitor provides screen space, not another renderer; the GPU running Microsoft Flight Simulator normally still draws and presents every panel. Different refresh rates, resolutions, Windows scaling levels or display adapters can add frame-pacing and copying overhead.
Test both monitors at compatible refresh rates and place the pop-out on the primary display for comparison. On desktops, check that both displays are connected to the GPU running the simulator rather than splitting them between integrated and dedicated graphics. Laptop display routing is hardware-dependent, so the available arrangement may be fixed.
If interacting with a detached window leaves the cockpit unable to pan or accept mouse input, that is usually window focus rather than lost performance. Follow our steps for restoring cockpit mouse focus after using a pop-out.
When the loss appears later in the flight
An immediate drop when a panel opens points to rendering, avionics or presentation overhead. A progressive decline over several hours is a different pattern: memory use, traffic, scenery, add-ons or accumulated main-thread load may be involved. Use our long-flight FPS troubleshooting process rather than blaming the detached panel alone.