How do I improve FPS and performance in Prepar3D?

To improve FPS and smoothness in Prepar3D, lower the settings that dominate your bottleneck: shadows, dynamic lighting, reflections, antialiasing and clouds for GPU load; AI traffic, autogen and scenery complexity for CPU load. Test one change at a demanding airport, then cap the frame rate at a value your system can hold consistently.

What settings improve FPS most in Prepar3D?

Shadows, traffic, autogen, dynamic lighting and clouds usually produce the largest gains in Prepar3D. A mistake we see repeatedly is lowering every slider slightly instead of targeting the few settings responsible for the slowdown.

The exact labels and available options differ between Prepar3D generations. The decision remains the same: reduce lighting and image-quality settings for a GPU-bound system, or object counts and traffic for a main-thread-bound system.

Do not begin with mesh resolution or basic terrain texture detail unless testing shows they are responsible. They can damage the view without recovering much performance. For a practical explanation of balancing object density and autogen, see the performance and settings guidance in the Netherlands 2000 scenery manual.

How should you tune Prepar3D without guessing?

The reliable method is to use one demanding saved scenario and change one setting group at a time.

1. Create a repeatable stress test. Use the aircraft, airport, weather, time and cockpit view that expose the problem. A clear day at a default regional field says little about an approach to a detailed hub in an airliner.
2. Check for an existing limit. Record the target frame rate, V-Sync setting and any external limiter. If P3D is already locked to 30 FPS, lower settings may create useful headroom without changing the displayed number.
3. Record the starting settings. Screenshots work, or use our checklist for recording and comparing FSX and P3D performance settings. This prevents endless slider changes with no reliable baseline.
4. Target the likely bottleneck. Start with shadows, dynamic lighting and antialiasing for poor night performance; traffic and autogen for busy approaches; clouds for weather-related slowdowns.
5. Use the add-on's own options. Complex aircraft may offer lower display refresh rates. Airports may let you disable terminal interiors, static aircraft, 3D grass, landside vehicles or other detailed objects.
6. Retest the same scenario. Change one group, reload if required and compare the same part of the flight. Do not judge from menus or the first seconds while scenery and shaders are still loading.
7. Choose a sustainable frame cap. Set the limit below the worst sustained rate, not the highest number seen while parked at an empty field.
8. Reset generated files only if normal tuning fails. Shader and configuration resets are troubleshooting measures, not routine performance tweaks.

Is Prepar3D CPU-limited or GPU-limited?

Prepar3D is probably CPU-limited when traffic, cities and complex cockpit systems hurt most; it is probably GPU-limited when resolution, shadows, clouds, antialiasing and night lighting cause the larger loss.

Overall CPU utilisation can be misleading. Prepar3D may saturate one main processing thread while the operating system reports a moderate percentage across all cores. Watch individual logical processors and GPU utilisation, but treat them as evidence rather than a complete diagnosis.

Why does Prepar3D stutter when the FPS looks acceptable?

Stutters are uneven frame delivery, so raising the average FPS may not fix them.

• Pauses during turns or on approach usually point to scenery, autogen, traffic or texture loading.
• Regular rhythmic judder often comes from a poor combination of frame cap, V-Sync and monitor refresh rate.
• A hitch when a view or effect appears for the first time can be shader compilation or texture loading.
• Performance that degrades during a long flight can indicate growing memory pressure, an add-on problem or thermal throttling.
• Good FPS with rough panning is usually a frame-pacing problem rather than a need for higher visual settings.

An SSD can shorten loading and reduce storage-related pauses, but it rarely transforms sustained FPS. Clearing the shader cache can also create temporary first-run hitches while Prepar3D rebuilds it, so do not clear it before every flight.

Why does Prepar3D run badly at only one airport?

A slowdown limited to one airport usually comes from that scenery package, surrounding autogen, duplicate scenery or the combination of airport, aircraft and weather.

Check for two airport packages covering the same location, duplicate traffic systems and static aircraft displayed alongside live AI. Scenery complexity only removes objects that the developer assigned to complexity levels; autogen controls the generated buildings and vegetation surrounding the bespoke airport, not the terminal model itself.

Should you cap frames in Prepar3D?

A stable frame cap usually feels smoother than an unlimited rate that swings widely.

• On a 60 Hz display, 30 FPS is a sensible starting point when the system cannot maintain a higher rate through the demanding parts of a flight.
• Use a higher cap only when the simulator can sustain it at the airports, in the aircraft and in the weather you actually use.
• With adaptive synchronisation, choose a cap that stays inside the monitor's effective operating range and test panning as well as the FPS counter.
• Avoid stacked limiters. Running P3D's cap, a driver cap and another frame limiter together can produce erratic pacing.
• Use unlimited briefly for diagnosis if necessary, but do not assume it is the smoothest permanent setting.

If the frame rate snaps between exact fractions of the display refresh rate, V-Sync behaviour may be responsible. Change one synchronisation control at a time; otherwise it becomes impossible to identify which limiter is setting the pace.

Should you edit Prepar3D.cfg or clear the shader cache?

Manual configuration edits and shader resets should come after ordinary settings and add-on checks.

1. Exit Prepar3D completely. Do not alter generated files while the simulator or an add-on manager is running.
2. Back up the existing file. The main configuration is normally under %APPDATA%\Lockheed Martin\Prepar3D vX\Prepar3D.cfg, where vX is the installed version folder. Rename it rather than deleting it.
3. Reset shaders separately if needed. The cache is normally under %LOCALAPPDATA%\Lockheed Martin\Prepar3D vX\Shaders. Rename the folder, start P3D and allow the cache to rebuild. Expect temporary first-use stutters.
4. Test a clean configuration before restoring tweaks. If P3D creates a fresh configuration and performs normally, rebuild your settings through the interface rather than copying every old line back.
5. Use a generated-files reset only for wider corruption. Where the installed P3D version provides such a reset, back up settings and add-on configuration first because it can affect much more than graphics preferences.

Do not apply copied FSX-era affinity, fibre or texture-bandwidth tweaks unless you understand the setting and know it applies to your P3D version. Many old recipes were written for another simulator generation and can make frame pacing or scenery loading worse.

Prepar3D v3 and earlier are 32-bit applications and are much more vulnerable to virtual address-space exhaustion. Prepar3D v4 and later are 64-bit, which removes that particular ceiling but does not eliminate CPU, system-memory or VRAM limits.

Which Windows and hardware checks matter?

Windows settings cannot rescue an overloaded P3D scenario, but power limits, background software, storage and heat can make a correctly tuned installation behave badly.

• Power: run a laptop from mains power and disable battery-saving modes. A high-performance profile can prevent conservative clock behaviour on some systems, but it cannot create extra hardware capacity.
• Background software: close browsers, recording tools, overlays, sync clients and hardware-monitoring utilities while testing. Do not permanently disable security software merely to gain frames.
• Graphics driver: use a stable driver and change it for a reason. Repeatedly swapping drivers complicates troubleshooting and may rebuild caches.
• Storage: place P3D and large scenery packages on an SSD when possible. This mainly helps loading, texture delivery and scenery-transition pauses.
• Cooling: check CPU and GPU clock speeds during a long session. Overheating can reduce clocks and create a slowdown that appears only after departure.
• Memory: leave the Windows page file enabled and system-managed unless there is a specific technical reason not to. Exhausted RAM or VRAM can cause hitching, blurry textures, instability or device errors.

Our Windows and system-level optimisation guide for flight simulators covers the broader PC checks without requiring random Prepar3D configuration edits.

What should you do if performance suddenly gets worse?

A sudden regression is more likely to be an add-on, cache, configuration, driver or background-process problem than a need to lower every setting.

A full reinstall should be the last resort. Per-user configuration and add-on files may survive an application reinstall, so reinstalling without checking those files can reproduce the same fault.

For the quickest useful gain, lower shadows, dynamic lighting, AI traffic, autogen and clouds first. Preserve mesh and terrain clarity until testing proves they are the problem, and judge success by consistent frame delivery at the most demanding point of the flight rather than the highest FPS seen in an easy scenario.