AutoOrtho vs X-Plane Map Enhancement for XP11 and XP12: compare imagery, caching, performance, scenery order, offline use and Ortho4XP.
For most X-Plane users, choose AutoOrtho for the established streamed regional workflow, X-Plane Map Enhancement when its application and available imagery work better in your flying areas, and Ortho4XP when you need fixed offline scenery and maximum control over source, zoom level, mesh and tile preparation.
AutoOrtho X-Plane 11 and X-Plane 12 compatibility
The documented desktop releases of AutoOrtho and X-Plane Map Enhancement cover both X-Plane 11 (XP11) and X-Plane 12 (XP12), but compatibility is release-specific. Install the package or configure the application for the correct simulator generation, and check its release notes before updating.
| Simulator | AutoOrtho | X-Plane Map Enhancement | Scenery order |
|---|---|---|---|
| X-Plane 11 (XP11) | Use a release and regional support data documented for XP11. Point it at the XP11 installation and have the mounted scenery available before starting the simulator. | Configure the application against the XP11 installation and use any XP11-specific profile or support data supplied by that release. | Keep airports and overlays above the active streamed orthophoto base mesh. |
| X-Plane 12 (XP12) | Use the XP12-compatible release and regional packages. The mount and scenery entries must be ready before XP12 scans Custom Scenery. | Configure its scenery integration for XP12 rather than reusing an XP11 setup blindly. | The same rule applies: airports and overlays above, streamed or generated base mesh below. |
Do not share version-specific support data between XP11 and XP12 unless the tool's documentation explicitly permits it. X-Plane 12 also handles terrain, coastlines, water and seasonal effects differently, so an XP11 package merely appearing in the scenery list does not prove that it is suitable for XP12.
When should an XP11 user choose a different workflow?
An XP11 user should choose Ortho4XP or conventional downloaded scenery when the AutoOrtho or Map Enhancement release being installed no longer lists XP11, the required mounting component does not work on that system, or dependable offline coverage matters more than streaming convenience.
Fixed tiles are also safer when an older XP11 airport or scenery package relies on a particular mesh. Never force an XP12-targeted package into XP11 to work around missing support; retain a compatible release or build local Ortho4XP tiles for XP11 instead.
AutoOrtho vs Map Enhancement vs Ortho4XP at a glance
Delivery method, rather than the product name, is the most useful way to choose between these three X-Plane scenery options.
| Option | XP11 and XP12 | How scenery is delivered | Image quality | Best choice when |
|---|---|---|---|---|
| AutoOrtho | Supported with a release and regional package intended for the selected simulator. | Regional support packages are installed locally; photographic textures are streamed through a mounted filesystem and retained in a cache. | Depends on the selected imagery source, local coverage and requested resolution. | You want broad regional coverage and accept a more technical initial installation. |
| X-Plane Map Enhancement | Supported where the chosen application release lists the selected X-Plane version. | Its application manages the imagery integration, streaming and cache. | Also source-dependent; it may beat AutoOrtho in one country and look worse in another. | Its application workflow or available imagery is a better match for your regular routes. |
| Ortho4XP | Tiles can be built for XP11 or XP12; build and install them for the intended simulator. | The user downloads and processes complete tiles before flying. Finished scenery remains on disk. | You choose the available source, zoom levels and build settings, but source defects remain visible. | You need reliable offline use, repeatable visuals or detailed control over individual tiles and mesh. |
Source-image quality is separate from delivery method. AutoOrtho does not inherently receive sharper photography than Map Enhancement, and streaming does not reduce baked-in clouds, colour seams, blurred security areas or old imagery. Ortho4XP gives you more control over source and resolution, but it cannot repair defects already present in that photography.
Imagery providers can be removed, renamed, throttled or made unavailable to a particular release. Before relying on any named source, check the tool's latest release notes and provider list rather than following an old video or configuration copied from another user.
Which one should you choose?
AutoOrtho is the sensible first choice for streamed regional flying, but Map Enhancement and Ortho4XP are better answers to specific requirements.
- Choose AutoOrtho if you fly long routes across several tiles, want its established regional-package workflow and do not mind configuring the mount, cache and scenery entries. XP12 users can follow our practical guide to AutoOrtho mounting, caching and scenery order.
- Choose X-Plane Map Enhancement if its available source looks cleaner around your usual airports, or you prefer controls managed through its application. Use our Map Enhancement application and cache setup instructions rather than copying an AutoOrtho configuration.
- Choose Ortho4XP if a route must remain available without a network connection, you want to mix zoom levels around airports, or you need control over tile construction and mesh-related settings.
All three provide photographic ground scenery, not a complete replacement for airports, buildings, roads or vegetation. Those features still come from airport packages and overlay scenery placed above the orthophoto base mesh.
Ortho4XP vs X-Plane Map Enhancement
Ortho4XP is the better offline and customisation option, while X-Plane Map Enhancement avoids the long preparation and large fixed storage commitment of pre-built tiles.
| Criterion | Ortho4XP | X-Plane Map Enhancement |
|---|---|---|
| Offline reliability | A completed tile is stored locally and does not need its imagery provider during the flight. | Only material already present in the cache can be expected to work offline; uncached terrain still needs the application and network. |
| Preparation time | Each area must be downloaded, processed, checked and installed before use. | Initial preparation is shorter, but new areas are fetched while flying or through any pre-caching facility offered by that release. |
| Disk use | High and predictable once the required tiles and zoom levels have been built. | Starts smaller but grows as the cache accumulates; eviction or cache limits may remove older material. |
| Mesh and customisation | Provides control over tile building, source selection, zoom-level allocation and supported mesh-related settings. | Uses the application's supplied integration and offers less per-tile construction control. |
| Imagery consistency | A built tile remains unchanged until you rebuild or replace it. | Uncached areas may reflect provider changes, while older cached areas retain previously fetched textures. |
| Provider dependence | The provider is needed while building or rebuilding the tile, not during normal use of the completed scenery. | Continued access is required whenever scenery is missing from the cache. |
The same offline distinction applies when comparing Ortho4XP with AutoOrtho. If fixed tiles fit your needs, our step-by-step Ortho4XP tile-building guide for X-Plane 12 covers creation, installation and scenery priority.
How do you compare AutoOrtho and Map Enhancement fairly?
A fair XP11 or XP12 comparison uses the same route, weather, simulator settings, overlays and nearest equivalent imagery quality, with only one streamed base mesh active.
- Match the simulator workload. Use the same aircraft, departure point, altitude, rendering settings and weather conditions.
- Keep overlays identical. Leave the same airports, roads, buildings and vegetation packages active so that only the ground imagery changes.
- Test representative terrain. Include a city, coastline and rural or mountainous area near somewhere you fly regularly.
- Compare cold and warm caches. Make one pass through uncached terrain, then repeat it after both tools have cached the route. Do not compare one tool's first download with the other's stored textures.
- Inspect defects as well as sharpness. Check for baked-in clouds, colour changes, shoreline alignment, blurry patches, loading pauses, graphics-memory pressure and cache growth.
A sharper source may require more bandwidth, storage and graphics memory. Screenshots made with different providers or resolution settings establish which source looked better in that test, not which application is universally superior.
Which has better X-Plane 12 performance?
Neither AutoOrtho nor Map Enhancement is inherently faster on every XP12 or XP11 system because uncached performance depends mainly on provider response, connection speed, storage, texture processing and selected quality.
- Pauses over new terrain usually mean imagery is being downloaded or processed. Put the cache on fast local storage, maintain free disk space and reduce the selected quality if the application offers that control.
- Default or patchwork terrain usually means the streaming process or AutoOrtho mount was not ready when X-Plane started, the download failed, or another base mesh has higher priority.
- Missing roads and buildings indicate an absent, disabled or incorrectly ordered overlay package, not poor orthophoto imagery.
- Black, repeated or low-resolution tiles can follow a failed request, provider throttling or an incomplete cache entry. Check the application's status and X-Plane's
Log.txtbefore deleting the entire cache or reinstalling everything. - Performance that worsens over time can indicate a full disk, an oversized cache on slow storage or texture settings that exceed available graphics memory.
A mistake we see constantly is judging frame rate while one tool is fetching a new area and the other is reading a warm cache. That measures two different workloads.
Can AutoOrtho and Map Enhancement be installed together?
AutoOrtho and Map Enhancement can remain installed in XP11 or XP12, but they should not both provide the same base-mesh tile during a normal flight or comparison.
X-Plane does not blend overlapping base meshes. The higher-priority entry in Custom Scenery/scenery_packs.ini wins for a given DSF tile, sometimes producing abrupt changes at tile boundaries. Disable the unused package with SCENERY_PACK_DISABLED, keep airports and overlays above the selected orthophoto mesh, and place that mesh below them.
Do not place another mesh package below an orthophoto mesh expecting X-Plane to combine the elevation from one with textures from the other. One base mesh wins. An airport package containing its own mesh can also override a much larger area than expected; our guide to X-Plane 12 base-mesh and global-scenery compatibility explains these conflicts.
Running both streaming applications in the background wastes network capacity, memory and cache writes without improving the scenery X-Plane displays.
Will streamed scenery work offline?
Previously cached AutoOrtho or Map Enhancement imagery may work offline, but neither should be trusted for a completely uncached route without an internet connection.
A cache contains only textures the application has successfully obtained, unless that release includes a pre-caching function and the whole route has been prepared. Test offline coverage before a flight rather than assuming that viewing an area once at cruise altitude cached every required resolution.
For guaranteed offline coverage, build and verify Ortho4XP tiles in advance. Keep the finished textures and mesh on local storage, retain the required overlays, and confirm the complete route in X-Plane before depending on it away from a network connection.