Compare the best X-Plane 12 scenery add-ons: X-World, Ortho4XP, AutoOrtho, mesh, airports and 3D grass, plus load order and fixes.
For the most realistic X-Plane 12 scenery, use X-World regional overlays with selected Ortho4XP tiles; this gives the best local detail and works offline once installed. For broad photoreal coverage, pair X-World with AutoOrtho instead, accepting dependence on a reliable connection, mount process and cache in exchange for lower initial storage.
Best X-Plane 12 scenery add-ons by use
No single package improves every scenery layer. The best setup combines one ground-imagery or terrain source, one compatible 3D overlay and detailed airports for the places where you regularly depart or land.
These scenery add-ons, often called scenery mods, perform different jobs. An overlay adds buildings, roads or vegetation; a base mesh defines the terrain surface and ground textures. Confusing those layers is the source of many installation problems.
| Add-on or scenery type | Best for | What it adds | X-Plane 12 compatibility, dependencies, performance and layer |
|---|---|---|---|
| X-World regional overlays | Buildings, roads, forests and city detail | Produces more convincing towns, transport networks and regional objects than imagery alone | Use the release intended for XP12 and install its documented vegetation and library folders. It is an overlay, not terrain. Dense cities can increase CPU and object-rendering load. |
| Ortho4XP | Local VFR flying and carefully selected regions | Locally stored aerial imagery with control over tile coverage and detail | Works in XP12 when tiles and overlays are generated and installed correctly. Each tile includes a base mesh. High-detail tiles consume substantial storage and can increase texture-memory use, but they remain available offline. |
| AutoOrtho | Broad photoreal coverage with a smaller initial download | Streams and caches aerial imagery as the simulator needs it | Requires an XP12-compatible setup, its helper and mount process, network access and a writable cache. It provides base scenery rather than a 3D city overlay. Connection or cache delays may cause missing or late-loading textures. |
| UHD Mesh v4 | Mountain flying in supported regions | Detailed terrain shaping in selected areas such as the Alps, Japan, New Zealand and western North America | A legacy base mesh with no object-library requirement. Storage and terrain density are high, and only one base mesh can appear per tile. The higher-detail terrain package for supported mountain regions should be compared with XP12's default terrain before committing to a large installation. |
| HD Mesh v4 | Broader offline terrain coverage | Sharper terrain relief and land-class detail without streamed imagery | A legacy base mesh that generally places less demand on storage than UHD. It cannot be blended with an Ortho4XP or AutoOrtho base mesh covering the same tile. |
| Hand-crafted airports and landmarks | Airline destinations, local aerodromes and recognisable city features | Improved runways, taxiways, terminals, signs, gates and local objects | XP12 support, library requirements and performance vary by package. Airport scenery normally sits above overlays, although some packages include their own mesh or vegetation and require a specific internal order. |
| Optional vegetation and 3D grass | Low-level VFR, helicopters and close-up airport detail | Denser forests, shrubs or individual grass around compatible airports | Use an XP12-native package and install every stated library. This is an overlay or object layer, not a base mesh. Dense 3D grass can be expensive near the ground, and overlapping airport vegetation causes duplicate trees or grass on paved surfaces. |
Our comparison of compatible global scenery layers explains the main conflicts between X-World, photoreal scenery and legacy terrain meshes.
Which scenery setup should I choose?
Choose according to the type of flying you do, the space available on your drives and how dependable your internet connection is.
- Maximum local realism for VFR: X-World over selected Ortho4XP tiles, followed by compatible airports and landmarks. This provides recognisable ground imagery, 3D buildings and reliable offline use once everything is installed.
- Broad photoreal coverage: X-World over AutoOrtho. Initial storage use is lower, but the cache grows and the streaming helper must be mounted and ready before X-Plane loads the area.
- Best offline reliability: X-World over X-Plane 12's default terrain, with HD or UHD Mesh used selectively. This avoids network and streaming failures.
- Airline and IFR flying: Prioritise accurate departure and arrival airports, then city landmarks. High-resolution orthophotos provide less benefit during the cruise.
- Modest hardware: Use the default terrain with selected airports and a regional overlay. Reduce dense objects or vegetation before sacrificing airport accuracy.
There is no single most realistic one for every location. Orthophotos can make coastlines, roads and fields immediately recognisable, but source imagery may contain cloud shadows, colour boundaries or outdated construction. X-Plane's default terrain is less geographically exact but often more visually consistent.
If you choose locally generated imagery, follow our practical Ortho4XP tile creation and installation workflow. Build a small test area before allocating storage to an entire country.
Recommended scenery for Canada and Quebec
For Canada, including Quebec, a practical setup is X-World America over either selected Ortho4XP tiles or the corresponding AutoOrtho coverage.
- Install the regional overlay: use the X-World America package and preserve its documented folder sequence. This provides the buildings, roads and vegetation that flat aerial imagery does not contain.
- Choose local or broad photoreal coverage: use Ortho4XP around Montréal, Québec City, the St Lawrence corridor, the Laurentians or another regular VFR area when offline reliability and control matter. Choose AutoOrtho when you fly across large parts of Quebec or Canada and prefer streaming to storing every completed tile in advance.
- Add airports selectively: check that each Canadian or Quebec airport explicitly supports X-Plane 12, lists all required libraries and is compatible with your chosen base mesh. Older airport packages may contain flattening, ground textures or vegetation that conflicts with orthophotos.
- Test one location first: confirm runway elevation, building placement, frame rate and winter appearance before adding more tiles or airports.
Ortho4XP requires more storage up front but is dependable offline. AutoOrtho reduces the initial footprint, although its cache expands and reliable loading depends on the connection, mount and cache remaining available.
Does photoreal scenery improve the city itself?
Photoreal imagery improves the ground beneath a city, but it does not create three-dimensional buildings or landmarks.
For a city such as Viña del Mar, aerial imagery can make the coastline, road pattern and urban footprint recognisable. The appropriate X-World America coverage supplies generic buildings, roads and vegetation; a compatible local airport or landmark package adds details that the regional overlay cannot reproduce.
This distinction explains why a new orthophoto tile may appear flat even though its textures are working. To improve the city itself, add one compatible object overlay and keep the simulator's object density high enough to display it. Additional airport and regional packages can be found in our X-Plane scenery downloads library.
Best 3D grass and vegetation scenery for X-Plane 12
The best vegetation package is one built for X-Plane 12 and specifically compatible with the airport or regional overlay beneath it.
3D grass is most worthwhile for helicopters, general aviation and screenshots taken close to the ground. It contributes little during an airline flight and can impose a disproportionate rendering cost around large airports, especially when dense objects, shadows and anti-aliasing are already demanding.
Regional forest replacements can improve tree variety and density, but check how they interact with X-World's own vegetation components. Airport-specific grass must respect runways, taxiways and exclusion zones. If two packages populate the same airport, grass may appear through aprons while doubled trees increase CPU and GPU load.
Older vegetation can also remain bright green in winter or look wrong under XP12 snow and seasonal conditions. Treat grass and vegetation as an optional visual overlay: they do not replace X-World, orthophotos, land-class textures or terrain mesh.
How should scenery_packs.ini be ordered?
Put airports and object overlays above imagery, with pure terrain meshes at the bottom of Custom Scenery/scenery_packs.ini.
- Custom airports, cities and landmarks — replacement airports must be above the default Global Airports entry. Keep airport-specific grass or vegetation components in the order supplied with that airport.
- Global Airports — place this above broad regional overlays and base meshes.
- X-World and other regional overlays — preserve X-World's documented folder sequence. A standalone regional vegetation layer belongs in this overlay band, below airports rather than at the bottom as terrain.
- Ortho4XP or AutoOrtho scenery — these provide imagery and base terrain for their covered tiles.
- HD Mesh, UHD Mesh or another pure terrain mesh — base-mesh packages belong at the bottom because only the highest-priority matching mesh is loaded.
A mistake we see constantly is installing a package, launching X-Plane and assuming its automatically generated position is correct. Newly discovered folders may be placed near the top, so close the simulator and inspect the file after its first scenery scan.
Before installing any scenery package, read its own priority instructions. Multi-folder products often depend on a precise internal sequence that should not be rearranged to match a generic alphabetical order.
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 across the same one-degree tile.
An Ortho4XP tile includes terrain mesh as well as imagery. If UHD or HD Mesh has higher priority, the orthophoto base is not displayed; if the orthophoto has higher priority, the separate mesh is ignored. Different elevation data must be incorporated while building the orthophoto tile rather than stacked underneath it.
Avoid using X-World and another complete building-and-road overlay over the same region unless their documentation explicitly supports the combination. Duplicate overlays cause doubled buildings, overlapping roads, flickering objects and unnecessary CPU load. The same rule applies to a regional vegetation overlay and an airport package that already supplies its own grass and trees.
Why is my new X-Plane scenery missing or broken?
Most broken scenery is caused by load order, incomplete extraction, missing libraries or two packages competing for the same tile.
- The scenery remains unchanged: check whether the package covers that tile, whether another base mesh has higher priority and whether its entry is marked
SCENERY_PACK_DISABLED. - Imagery appears without buildings: orthophotos replace the ground but do not automatically create 3D objects. Add one compatible overlay and check that object density is not too low.
- Objects are missing or errors appear: inspect
Log.txtfor the named library or asset. Confirm that the package root contains folders or files such asEarth nav dataorlibrary.txt, rather than another identically named folder nested inside it. - AutoOrtho textures are absent: the helper or mounted scenery was not ready before X-Plane scanned the area, the cache is inaccessible or the connection failed.
- Grass covers a runway or trees are doubled: disable the overlapping vegetation package, or keep the custom airport above a single regional vegetation layer. Do not solve this by repeatedly moving both packages higher.
- Buildings, markings or runways flicker: two airport or overlay packages cover the same location. Disable the duplicate rather than leaving both active.
- An airport is floating or buried: the airport and selected base mesh disagree about elevation. Changing airport priority cannot repair terrain geometry; use a compatible airport and mesh combination.
- Performance drops only near the ground: test without optional 3D grass, dense vegetation and duplicate overlays before reducing orthophoto quality. Object-heavy layers are often the cause.
Install one layer at a time and reload the same airport after each change. This isolates missing dependencies, priority errors and performance costs far more effectively than adding an entire scenery stack at once.