Compare the best scenery add-ons for X-Plane 12, including X-World, Ortho4XP, AutoOrtho, UHD Mesh and HD Mesh, with setup and load-order advice.
The best X-Plane 12 scenery setup combines X-World regional overlays for buildings and roads with either Ortho4XP tiles or AutoOrtho for aerial imagery. Add hand-crafted airports for places you fly often. UHD Mesh v4 suits selected mountain regions, while HD Mesh v4 provides broader, lighter terrain coverage, although both are legacy meshes.
Best X-Plane 12 scenery add-ons by use
No single package improves every scenery layer. For most users, we recommend choosing one ground-imagery or terrain option, placing a compatible 3D overlay above it, then adding detailed airports only where they matter.
| Add-on or scenery type | Best for | Main benefit | Important limitation |
|---|---|---|---|
| X-World regional overlays | Buildings, roads, forests and regional detail | Produces much more convincing towns and transport networks than imagery alone | It does not replace ground textures or terrain mesh. Install its regional folders, vegetation library and required dependencies in their documented order. |
| Ortho4XP | Local VFR flying and carefully selected regions | Lets you build aerial-imagery tiles with control over coverage and detail | Consumes substantial storage, and every tile includes its own base mesh. Follow our Ortho4XP creation and installation steps to avoid misplaced overlays and tiles. |
| AutoOrtho | Large-area aerial imagery without downloading complete regions first | Streams and caches imagery as required | Needs a reliable connection, a working mount process and room for its growing cache. Our AutoOrtho streaming and cache setup covers the required workflow. |
| UHD Mesh v4 | Mountain flying in supported regions | Detailed terrain shaping in areas such as the Alps, Japan, New Zealand and the western United States | Coverage is selective and storage demands are high. You can download the higher-detail UHD terrain package, but test it against X-Plane 12's default mesh because it is a legacy mesh. |
| HD Mesh v4 | Broader terrain coverage on a more modest system | Improves mountains, valleys and land-class detail across larger areas | It is less detailed than UHD and is also a legacy base mesh. The broader HD terrain package is the better choice when coverage matters more than maximum terrain density. |
| Hand-crafted airports and landmarks | IFR destinations and regularly visited cities | Improves runways, taxiways, terminals, gates and recognisable local objects | Check that each package supports X-Plane 12 and that all listed libraries are installed. |
Which scenery setup should I choose?
Choose the stack according to what you fly and what your storage and connection can support.
- Best for VFR: X-World over selected Ortho4XP tiles, plus detailed airports. This gives recognisable ground imagery and useful 3D buildings.
- Best for broad coverage: X-World over AutoOrtho. It reduces the initial storage requirement but depends on the streaming helper, cache and network connection working before X-Plane starts loading the area.
- Best for offline reliability: X-World over X-Plane's default terrain, or HD/UHD Mesh in selected regions. This avoids streamed textures and their associated loading failures.
- Best for airline flying: Prioritise accurate departure and arrival airports, then add city landmarks. High-resolution orthophotos offer less benefit when most of the flight is above cruise altitude.
Photoreal scenery is not automatically the most convincing option. Source imagery can contain colour changes, cloud shadows or seasonal inconsistencies, while X-Plane's default terrain remains visually consistent across a much larger area.
How should scenery_packs.ini be ordered?
Put airports and overlays above imagery, and keep terrain meshes at the bottom. In Custom Scenery/scenery_packs.ini, the practical order from highest to lowest priority is:
- Custom airports, cities and landmarks — replacement airports must be above the default Global Airports entry.
- Global Airports — keep this above regional overlays and base meshes.
- X-World or another 3D overlay — preserve the package's own folder sequence rather than rearranging its numbered components.
- Ortho4XP or AutoOrtho scenery — these provide imagery and a base mesh.
- HD Mesh, UHD Mesh or another terrain mesh — pure base-mesh packages belong at the bottom.
A mistake we see constantly is installing a new package, launching X-Plane and assuming its automatically generated position is correct. X-Plane may place a newly discovered folder near the top, so close the simulator and check the order after its first scenery scan.
Can I combine orthophotos, X-World and mesh scenery?
Yes, X-World can sit over Ortho4XP or AutoOrtho, but two base meshes cannot be blended for the same one-degree tile. X-Plane loads the highest-priority matching base mesh and ignores the lower one.
An Ortho4XP tile already contains terrain mesh as well as imagery. If UHD Mesh is placed above that tile, the orthophoto disappears; if UHD Mesh is below it, the UHD terrain is ignored. To use different elevation data with orthophotos, the tile must be built with that data rather than stacked over a separate mesh package.
Avoid running X-World and another full building-and-road overlay over the same area unless their instructions explicitly support it. Duplicate overlays cause doubled buildings, overlapping roads, flickering objects and unnecessary CPU load.
Why is my new X-Plane scenery missing or broken?
Most broken scenery comes from load order, incomplete extraction, a missing library or two packages covering the same tile.
- Default terrain still appears: another base mesh has higher priority, the package is marked
SCENERY_PACK_DISABLED, or the installed region does not cover that tile. - Imagery appears without buildings: orthophotos replace the ground but do not automatically provide 3D objects. Add one compatible overlay and check that object density is not set too low.
- Objects are missing or errors appear: inspect
Log.txtfor the named library or asset. Confirm that the package root contains items such asEarth nav dataorlibrary.txtrather than another identically named folder nested inside it. - AutoOrtho textures are absent: its helper or mounted scenery was not ready before X-Plane scanned the area, or the cache location is inaccessible.
- Buildings or runways flicker: disable the duplicate airport or overlay rather than repeatedly moving both packages higher.
- An airport is floating or buried: the airport and base mesh disagree about elevation. Changing airport priority cannot repair terrain geometry; use a compatible airport or mesh combination.
Install one scenery layer at a time and test the same airport after each change. That makes load-order conflicts, missing dependencies and performance problems far easier to identify than installing an entire scenery stack at once.