Compare the best scenery add-ons for flight simulators, including MSFS, X-Plane, FSX and Prepar3D, with layering and conflict-fix advice.
The best scenery add-ons are a layered mix of accurate terrain mesh, regional ground imagery or landclass, object overlays and detailed airports you actually use. For most simmers, Microsoft Flight Simulator World Updates, SimHeaven X-World with Ortho4XP, and FreeMeshX with selected FSX or Prepar3D airports deliver the largest practical improvement.
No single package improves every part of a flight simulator. The right choice depends on whether the weakness is flat terrain, inaccurate ground textures, sparse buildings or an outdated airport.
Best scenery add-ons by simulator
| Simulator | Recommended starting point | Main caveat |
|---|---|---|
| Microsoft Flight Simulator 2020 and 2024 | Official World and City Updates, We Love VFR and carefully chosen airport replacements. Our recommended MSFS airport, city and VFR enhancements cover the strongest options in more detail. | Check whether each package explicitly supports MSFS 2020, MSFS 2024 or both. On Xbox, and on PlayStation 5 for MSFS 2024, use console-supported in-sim content rather than PC Community-folder packages. |
| X-Plane 12 | SimHeaven X-World for object placement, Ortho4XP or AutoOrtho for photographic ground coverage, compatible HD or UHD mesh, and a custom airport. See our comparison of X-Plane 12 mesh, orthophoto and overlay options. | X-World has several regional and layer folders that must remain in the specified order. X-Plane 11 scenery may also need updating for X-Plane 12 vegetation, lighting or terrain behaviour. |
| FSX | FreeMeshX, a good landclass or photoreal region, and detailed scenery for frequently used airports. Our FSX layering recommendations for terrain, regions and airports explain how those components fit together. | Dense autogen, large textures and complex airports can exhaust the limited address space of 32-bit FSX. Install gradually and test the same demanding flight after each addition. |
| Prepar3D | A global base or landclass product approved for the installed Prepar3D version, followed by terrain mesh and selected airports. | Compatibility must match the exact major Prepar3D version. An older FSX installer recognising Prepar3D is not proof that its scenery, effects or configuration method remains compatible. |
| DCS and similar combat simulators | The official terrain module covering the operations and aircraft you intend to use. | These maps are self-contained theatres rather than interchangeable civil-simulator scenery layers. |
What type of scenery add-on should you install first?
Install the layer that corrects the most visible problem, then test it before adding another.
- Terrain mesh: Choose this when mountains, coastlines or valleys have the wrong shape. Mesh changes elevation geometry; it does not add photographic textures, terminals or city buildings.
- Landclass or orthophoto scenery: Use landclass to improve the type and placement of generic ground textures, or orthophotos when recognisable roads, fields and towns matter most. Orthophotos require considerable storage, and their imagery licences may prohibit redistribution of generated tiles.
- Object overlays and landmarks: Add these when roads are present but towns, pylons, chimneys, aerials or other VFR objects are missing. An orthophoto layer may look empty without a compatible overlay.
- Airport scenery: Add detailed airports last and only where the default version is inadequate. A single high-quality home airport usually provides more value than dozens of places you rarely visit.
Conceptually, mesh belongs at the bottom, followed by ground coverage, object overlays and airports at the top. That does not mean every simulator exposes those layers through the same priority system.
How should scenery layers be ordered?
Airports and local corrections should normally override regional scenery, while mesh and broad base layers should remain underneath them.
- X-Plane: In
scenery_packs.ini, keep custom airports above landmarks and overlays, with orthophoto and mesh packages below them. Follow X-World's supplied internal order rather than alphabetising its folders. - FSX: Place detailed airports and their local corrections above regional landclass, photoreal scenery and mesh in the Scenery Library. Remove obsolete elevation fixes left by an airport you have uninstalled.
- Prepar3D: Use the add-on package method when the developer supplies it. Do not activate a second manual copy of scenery already registered through an
add-on.xmlpackage. - Microsoft Flight Simulator: Avoid installing two packages that replace the same airport or landmark. MSFS does not benefit from copying an old FSX-style scenery stack; conflicting packages must usually be disabled or removed.
Common scenery problems and their fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Two terminals, duplicated jetways or overlapping runways | Two airport replacements are active, or an enhancement package also modifies the airport. | Keep one airport version and disable the conflicting package. Check broad regional enhancements as well as obvious airport folders. |
| Sunken runway, plateau or ridge across the airport | The airport elevation conflicts with mesh, an older elevation correction or another airport version. | Update the airport, place it above lower scenery layers where the simulator permits, and remove stale elevation fixes. |
| Trees or buildings on a runway | An object overlay is overriding an outdated airport boundary or exclusion area. | Update the airport first, then test without the regional overlay to identify which package supplies the unwanted objects. |
| Pink, blank or missing textures | A required library is absent, files were not copied completely, or the package targets another simulator version. | Reinstall from a complete package, add only the dependencies named by its documentation and verify version compatibility. |
| Stutters near a detailed airport | Heavy objects, large textures, photogrammetry and AI traffic are competing for processor, graphics memory or bandwidth. | Reduce object density or texture resolution, test with traffic lowered, and remove overlapping scenery rather than immediately reducing every graphics setting. |
Are free or payware scenery add-ons better?
Freeware is often the best choice for broad mesh, object overlays and community airport corrections; payware makes most sense for a specific airport, city or region that you use repeatedly.
Judge an airport by layout accuracy, performance, night lighting, ground markings, active developer support and compatibility with your simulator version—not simply by texture size. For commercial options, our payware scenery shortlist by simulator and use case narrows the choices without requiring an all-payware setup.
Can scenery add-ons reduce frame rate?
Yes, although each scenery type stresses a different part of the computer. Object-rich airports and city overlays tend to increase CPU load; large textures use graphics memory; streamed imagery needs reliable bandwidth and cache space; orthophotos consume storage and can increase loading time.
Terrain mesh alone is rarely the main frame-rate culprit. The mistake we see constantly is stacking several packages that cover the same airport or region, then trying to solve the resulting stutters through graphics settings. Add one layer at a time, keep a record of what it replaces and retest a repeatable flight after every change.