Why does Prepar3D v4 stutter, and how do I fix it?

Prepar3D v4 usually stutters because frame times are uneven, not simply because average FPS is low. Common causes are an overloaded main CPU thread, scenery loading, AI traffic, add-on aircraft, limited VRAM, background tasks and a mismatched frame-rate cap. Isolate the cause, then lower or disable the setting responsible.

How can I identify what is causing the stutter?

The quickest diagnosis is to reproduce the stutter in a controlled flight and change one subsystem at a time. An FPS counter alone is not enough: Prepar3D v4 can report 40 FPS while occasional slow frames make movement look jerky.

1. Create a clean baseline. Load a built-in aircraft at a default airport in clear daytime weather. Set airline, general aviation, road and water traffic to zero, then close any external weather, traffic, recording or moving-map software.
2. Repeat the same view and route. Save the flight and note whether the pauses occur constantly, at a particular location, while turning the camera or only near a detailed airport.
3. Watch the limiting component. Check individual CPU-thread activity, GPU load and dedicated graphics memory while reproducing the problem. Total CPU utilisation can be misleading because one saturated main thread can limit Prepar3D while the other cores remain partly idle. Our guide to separating CPU, GPU, VRAM and frame-pacing limits explains how to interpret those readings.
4. Test settings in groups. Reduce traffic first, then autogen and scenery distance, followed by shadows, dynamic lighting, clouds and anti-aliasing. Restore a group if it makes no measurable difference.
5. Reintroduce add-ons gradually. Enable scenery regions, traffic tools, weather software and complex aircraft one category at a time. A smooth default flight followed by stuttering with one category enabled is far more useful than changing ten graphics options together.

Which Prepar3D v4 settings should I lower first?

Reduce the settings that affect the component reaching its limit rather than applying a generic low preset. The following order catches most Prepar3D v4 stuttering without unnecessarily degrading the whole image.

• AI and vehicle traffic: Airline and general aviation AI can burden the main CPU thread, particularly around hubs. Road traffic, ships and ferries add further work. External traffic injectors may continue generating aircraft even when Prepar3D's own sliders are at zero.
• Autogen and scenery: Lower autogen density, scenery complexity and object draw distance one step at a time. Large terrain and autogen radii increase the amount loaded while flying; use our safer guidance for adjusting Prepar3D draw distances before editing configuration values.
• Shadows and dynamic lighting: Reduce shadow-casting categories and shadow distance. Dynamic lighting can be especially expensive at detailed add-on airports at night because many lights affect the scene simultaneously.
• Clouds and reflections: Reduce cloud draw distance, weather detail and reflection options if stuttering appears in heavy weather but not under clear skies.
• Anti-aliasing and resolution: These are primarily GPU costs. Prefer a moderate multisample anti-aliasing setting over supersampling when the GPU is saturated, particularly at high display resolutions.
• Texture resolution: Lower it when dedicated VRAM is close to full or camera turns trigger loading pauses. High-resolution aircraft, airport and ground textures accumulate even when each product runs acceptably by itself.

For the wider trade-offs between traffic, shadows, autogen, clouds and reflections, see our setting-by-setting Prepar3D performance priorities.

Should I use unlimited FPS, V-Sync or a frame cap?

A single sustainable frame cap usually gives smoother motion than an unlimited rate that constantly rises and falls. The correct target is one the computer can maintain in the demanding parts of the flight, with some CPU and GPU headroom left for scenery and weather updates.

On a fixed 60 Hz display, a steady 30 FPS can look smoother than an unstable 40–55 FPS because each frame is presented for an even number of refresh cycles. If the system cannot hold the chosen target at a large airport, reduce the relevant workload rather than letting it repeatedly hit and miss the cap.

• Use either Prepar3D's limiter, a driver-level limit or another frame limiter, not several at once.
• Test V-Sync both on and off. It removes tearing, but missing the refresh target can create obvious cadence changes on a fixed-refresh display.
• With a variable-refresh display, keep the frame rate inside its supported range and below its maximum refresh rate.
• Treat unlimited FPS as a diagnostic option. It can expose maximum performance, but it may keep the CPU or GPU fully occupied and leave too little headroom for scenery loading.

Why does Prepar3D v4 stutter near airports?

Airport stutters usually come from a sudden combination of scenery objects, AI aircraft, high-resolution textures and dynamic lights. If the pause happens at the same position every time, disable the suspected airport scenery and repeat the approach with default scenery.

Night-only stuttering points strongly towards dynamic lighting or shadows. Daytime stuttering that becomes worse with AI enabled usually indicates traffic or CPU load. A pause while crossing a scenery boundary can indicate slow storage, an exceptionally heavy scenery layer or a damaged asset; keeping Prepar3D and frequently used scenery on an SSD helps with loading, but it will not cure a saturated CPU thread.

Do affinity masks or configuration tweaks fix v4 stuttering?

Affinity masks and copied configuration tweaks are not reliable first-line fixes for Prepar3D v4 stuttering. Prepar3D uses a main thread plus worker threads, and restricting them to the wrong logical processors can reduce scenery throughput or create worse frame times.

Start with no custom AffinityMask entry. Test one only after establishing a repeatable baseline, and keep it only if the same flight shows a consistent improvement; our explanation of when a Prepar3D v4 affinity mask can help or hurt covers the decision in detail.

If the configuration may be damaged, close Prepar3D and rename %APPDATA%\Lockheed Martin\Prepar3D v4\Prepar3D.cfg so the simulator generates a clean file. Back up the original first, and expect to reapply graphics and simulator preferences. Do not paste an entire configuration from another computer because hardware, add-ons and display arrangements differ.

A shader-cache rebuild is appropriate after a graphics-driver change, visual corruption or a suspected damaged cache. With Prepar3D closed, rename the Shaders folder under %LOCALAPPDATA%\Lockheed Martin\Prepar3D v4. The first flight after rebuilding may load more slowly or stutter while shaders are recreated, so judge the result on a second repeat of the test.

How do I know whether an add-on is responsible?

An add-on is the likely cause when the controlled default flight is smooth and the stutter returns immediately after that aircraft, scenery area or external utility is enabled. Confirm that the add-on explicitly supports Prepar3D v4 and the installed v4 point release, especially when it includes gauges, DLLs or external processes rather than scenery alone.

The useful target is not the highest average FPS shown in an empty area. Aim for stable frame times through the busiest airport and weather combination you normally use, then retain enough performance headroom for the approach, where scenery, traffic and cockpit workload peak together.