How can I improve FPS in X-Plane 12?
To improve FPS in X-Plane 12, first identify whether the CPU or GPU has the longer frame time. Lower CPU-heavy world detail, traffic and scenery settings, or GPU-heavy resolution, anti-aliasing, shadows and clouds. Test one change at a time with the same aircraft, weather, location and cockpit view.
How do I find the X-Plane 12 performance bottleneck?
X-Plane's CPU and GPU frame times reveal which component is preventing a higher frame rate. Open Settings, select Data Output, find the frame-rate entry and enable its on-screen display. The exact presentation can vary, but the important figures are CPU time and GPU time per frame.
- CPU time is higher: the processor is the main limit. Reduce world objects, rendering distance, vegetation, AI traffic and parked aircraft before lowering resolution.
- GPU time is higher: the graphics card is the main limit. Reduce rendering resolution, anti-aliasing, shadow quality and cloud quality.
- Both times are low but the sim pauses: investigate scenery loading, insufficient memory, plug-ins, thermal throttling or frame pacing rather than reducing every graphics option.
Use a repeatable test rather than judging performance during unrelated flights:
- Choose a baseline. Load the same default aircraft, airport, weather, time and cockpit view. Let scenery loading settle before recording FPS.
- Record CPU and GPU times. Note which is higher and how far it is from your target frame-time budget.
- Change one setting. Moving several sliders at once makes it impossible to identify which adjustment helped.
- Test a demanding case. After tuning the baseline, repeat the test at a detailed airport with clouds and the aircraft you normally fly.
Which X-Plane 12 settings improve FPS most?
The best setting to lower depends on the measured bottleneck; reducing GPU options will achieve little when the main simulation thread is already CPU-limited.
| Bottleneck or symptom | Lower first | Why it helps |
|---|---|---|
| High CPU frame time | World objects, rendering distance, vegetation, AI traffic and parked aircraft | Reduces scenery preparation, draw calls and aircraft simulation work |
| High GPU frame time | Rendering resolution, anti-aliasing, shadows and clouds | Reduces pixel processing and complex visual effects |
| VRAM exhaustion or severe texture stutters | Texture quality and high-resolution add-on scenery | Reduces texture swapping between system memory and VRAM |
| Good FPS except in complex weather | Cloud quality, shadows and weather-related visual detail | Reduces the cost of rendering layered clouds and lighting |
Resolution and anti-aliasing are usually the first controls to adjust when the GPU is overloaded, especially at 4K. Lower the rendering resolution in small steps before making the image unnecessarily soft. High anti-aliasing levels become particularly expensive when the simulator is already drawing millions of pixels per frame.
World detail and traffic are better targets for a CPU bottleneck. Complex airports, dense cities, AI aircraft and detailed add-on airliners can all increase main-thread time. Temporarily disable AI traffic while tuning so it does not distort the result.
Texture quality mainly controls memory use. Lowering it may cure hitching when VRAM is full, but it often provides little extra FPS when textures already fit comfortably. Our explanation of how each X-Plane 12 visual setting affects image quality helps identify which compromises are visible and which are not.
Multiple displays multiply the number of pixels being rendered, and separate views can add CPU work as well. If performance dropped after expanding the cockpit, check the resolution and view configuration against our X-Plane 12 multi-monitor setup advice.
Why does X-Plane 12 stutter when average FPS is good?
Stuttering with acceptable average FPS usually indicates uneven frame delivery, memory pressure, scenery loading or an add-on that performs work intermittently.
- VRAM or RAM pressure: reduce texture quality, close memory-heavy applications and test without high-resolution orthophotos or scenery. A high average FPS does not prevent pauses caused by texture swapping.
- Scenery loading: an SSD improves loading and can reduce storage-related pauses, although it rarely raises steady-state FPS by itself. Brief hitches can still occur when crossing into a new scenery area.
- Plug-in activity: weather engines, traffic systems, avionics and scripts may run tasks at intervals. Disable them in groups, restart X-Plane and then re-enable them individually.
- Thermal or power limits: use mains power on a laptop, ensure X-Plane runs on the high-performance GPU and check that cooling is not clogged or restricted.
- Unstable frame pacing: a steady 30 FPS often feels smoother than a frame rate that repeatedly jumps between 35 and 60. A suitable frame cap or synchronisation setting can reduce those swings.
Do not routinely delete preferences or caches as a general performance fix. That can reset controls and graphics settings without addressing the real bottleneck. After a graphics-driver or simulator update, some temporary shader-related stutter may also settle once common scenes and effects have been rendered again.
Do aircraft, scenery and plugins reduce X-Plane 12 FPS?
Aircraft, scenery and plugins can substantially reduce performance, so every investigation should include a comparison against a default aircraft and default scenery.
Complex glass cockpits and systems tend to increase CPU load. Detailed airports increase object count and draw calls, while large textures and orthophotos consume VRAM and system memory. A mistake we see constantly is blaming the graphics sliders when the slowdown appears only with one aircraft or airport.
- Test a default aircraft at the same airport and with the same weather.
- Temporarily disable plugins from
Resources/pluginsand restart X-Plane; not every plugin unloads completely during a running session. - Compare default and custom scenery under identical conditions.
- Restore add-ons one at a time until the slowdown returns.
X-Plane's plugin performance information can provide a useful clue, but it may not expose every indirect cost. For safe folder locations and isolation methods, use our guide to managing X-Plane aircraft, scenery and plugin add-ons.
A realistic FPS target
A stable 30 FPS or better is a sensible target for conventional monitor flying, while VR and high-refresh displays require higher, steadier rates. X-Plane may reduce simulation speed if it cannot sustain roughly 20 FPS, so settings should not be tuned around prolonged operation below that level.
At 30 FPS, both CPU and GPU frame times need to remain below about 33 milliseconds. At 60 FPS, each must stay below about 16.7 milliseconds. Tune for the demanding parts of a flight rather than an empty runway under clear skies.
Match hardware upgrades to the measured limit
Hardware should be upgraded only after frame-time testing identifies the limiting component. A faster GPU helps resolution, anti-aliasing, shadows and multi-monitor rendering; it will not solve a high CPU frame time caused by objects, traffic or aircraft systems.
- CPU-limited: prioritise strong main-thread performance, even though X-Plane also uses additional cores.
- GPU-limited: prioritise graphics performance and enough VRAM for the chosen resolution and add-ons.
- Memory-limited: add RAM only when system memory is genuinely exhausted; unused extra RAM does not increase FPS.
- Storage-limited: move X-Plane and large scenery packages to an SSD to improve loading and reduce storage-related hitching.
Our X-Plane 12 hardware selection guide explains how CPU, GPU, VRAM, RAM and storage affect different performance problems.