Why does scenery load in chunks or appear late in Prepar3D v5?

Scenery loads in chunks or appears late in Prepar3D v5 when terrain, textures, autogen or scenery objects cannot be prepared before the camera reaches them. The usual causes are an excessive Level of Detail Radius, heavy autogen, an unsustainable frame rate, slow storage, VRAM pressure or a broken scenery add-on.

Prepar3D processes terrain mesh, ground textures, autogen and scenery-library objects separately. One layer can therefore fall behind while the others remain visible. Fast low-level flight, slewing, teleporting and abrupt view changes make this especially obvious.

What does each Prepar3D scenery-loading symptom mean?

The shape, location and persistence of the missing scenery usually reveal which part of the loading process is struggling.

A visible object ring is not automatically a fault: all scenery has a finite draw range. The problem is abnormal pop-in close to the aircraft, persistent missing cells or loading that becomes progressively later during an otherwise ordinary flight.

How do I stop Prepar3D v5 scenery loading in chunks?

The reliable fix is to distinguish a temporary loading backlog from missing content, then remove one bottleneck at a time.

1. Run the pause test. When a tile is missing, pause the flight or reduce speed and wait briefly. If the area fills, the files exist but the loader is behind. If it never appears, suspect an installation, registration or file problem.
2. Create a repeatable baseline. Use the same location, aircraft, weather and view for each test. Compare the problem flight with a default aircraft and default scenery; a complex aircraft can consume enough CPU and VRAM to affect scenery even when the scenery itself is sound.
3. Set a finite frame-rate target. Choose a target Prepar3D can maintain in the busiest part of the route. Running unlimited can consume the processing headroom needed for terrain and object preparation. Avoid applying two different frame limiters at once.
4. Lower the setting that matches the symptom. Reduce Level of Detail Radius for late terrain cells, Autogen Draw Distance and density for delayed trees or buildings, and Texture Resolution when high-resolution imagery is exhausting VRAM or storage bandwidth.
5. Check every drive used by the flight. Prepar3D may be on an SSD while an add-on library sits on a slower hard disk, sleeping external drive or unavailable network path. Low free space, cloud synchronisation, indexing and a security scan can also delay thousands of small texture reads.
6. Reduce VRAM use. Prepar3D v5 uses a DirectX 12 renderer, so exceeding the available dedicated graphics memory can lead to heavy stuttering, texture eviction and instability. Lower texture resolution, anti-aliasing, display resolution and shadow load before reducing unrelated settings.
7. Test a clean configuration. Close Prepar3D, back up and rename %APPDATA%\Lockheed Martin\Prepar3D v5\Prepar3D.cfg, then start the simulator so it creates a new file. This resets display and performance options, so record any controls or settings that matter first.
8. Re-enable add-ons individually. If default scenery loads correctly, restore scenery packages one at a time. Test the same route after each change rather than enabling the entire library and guessing which package caused the delay.

Which scenery settings should I lower first?

Lower settings in symptom order; a blanket low preset often hides the cause without identifying it.

• Late terrain squares: reduce Level of Detail Radius first. It controls how much detailed terrain Prepar3D prepares around the aircraft.
• Soft photo scenery: reduce Texture Resolution if storage throughput or VRAM is saturated. Moving the imagery to an SSD may help when disk reads are the limiting factor.
• Late trees and generic buildings: lower Autogen Draw Distance, then autogen density.
• Missing or delayed custom buildings: test Scenery Complexity. This setting affects many placed scenery objects but does not repair missing package files.
• Stutters before each new tile: reduce shadows, traffic and other CPU or GPU workloads to leave capacity for scenery preparation.
• Incorrectly shaped hills or coastlines: adjust mesh resolution. Mesh settings affect elevation geometry; they are not the correct first fix for blurry textures or late autogen.

Our explanation of how scenery distance, autogen, mesh and texture settings affect loading provides the wider trade-offs without requiring every option to be reduced.

Is Prepar3D CPU- or GPU-bound when scenery pops in?

Prepar3D scenery pop-in can be CPU-, GPU-, VRAM- or storage-bound, and the setting that fixes it is the clearest diagnostic.

• If reducing Level of Detail Radius, autogen or traffic helps, the CPU and scenery-preparation workload were probably the limit.
• If reducing texture resolution, anti-aliasing or display resolution helps, GPU load or VRAM pressure was more likely.
• If the delay improves after moving scenery to an SSD, storage latency or throughput was involved.
• If only one geographical area fails, treat it as an add-on problem, not a whole-system performance problem.

For a more detailed diagnosis, see our guide to identifying CPU, GPU, VRAM and scenery-distance bottlenecks in Prepar3D.

When is an add-on scenery responsible?

An add-on is the likely cause when the problem starts at a clear regional boundary, affects one airport or disappears when that package is disabled.

Prepar3D v5 scenery may be installed through a traditional Scenery Library entry or an add-on.xml package. Check that the package points to an available folder, required texture and library files are present, and the same airport or terrain is not registered twice. Our Prepar3D v5 scenery installation and duplicate-package checks cover both installation methods.

Priority only decides which overlapping layer wins; it cannot make absent files load. If an area is enabled but appears in the wrong order, check where Prepar3D stores scenery configuration and how library priority is managed.

A mistake we see repeatedly is copying unidentified textures into a global Texture folder. That may conceal one broken package while causing conflicts elsewhere. Repair or reinstall the affected add-on instead.

Is chunk loading normal during fast or low-level flight?

Brief loading after slewing, changing location or flying very fast at low altitude can be normal because the camera reaches new terrain before Prepar3D has prepared it.

Large areas should not remain absent during an ordinary flight with default scenery. If pausing consistently allows the terrain to catch up, reduce workload or improve storage performance. If pausing changes nothing, investigate missing files, scenery registration and package conflicts.

Should I clear caches or reinstall Prepar3D?

Reinstalling Prepar3D should be a last resort because late scenery is usually caused by workload, configuration or one add-on rather than the simulator installation.

Regenerating Prepar3D.cfg is a useful configuration test. Clearing generated shader data may help rendering artefacts after graphics changes, but it is not a primary fix for terrain that simply cannot load quickly enough.

If one package fails, repair that package. If stock scenery still contains permanent blank areas with a clean configuration and no third-party scenery enabled, repair the relevant Prepar3D content or scenery component before considering a full reinstall.