FAQ Guide

Application Initialization Failure#

The Windows installer normally includes the required .NET runtime. Keep the exact startup error and check the installer log and antivirus protection history before reinstalling. A missing runtime and a quarantined application file need different remedies; do not disable antivirus protection just because the application fails to start.

If the Windows error specifically reports a missing .NET or ASP.NET runtime, install the required runtime from Microsoft:

• .NET 10 Runtime download link: https://builds.dotnet.microsoft.com/dotnet/Runtime/10.0.2/dotnet-runtime-10.0.2-win-x64.exe
• ASP.NET 10 Runtime download link: https://builds.dotnet.microsoft.com/dotnet/aspnetcore/Runtime/10.0.2/aspnetcore-runtime-10.0.2-win-x64.exe

Windows 10 Related Issues#

Map Enhancement does not work, saying background service can’t connect#

This message alone does not identify the cause. Update to the current XPME release and save the startup error, Windows version, and any antivirus quarantine or protection-history entry. Use these details to check for a missing runtime or blocked application file.

Do not disable Hardware-enforced Stack Protection (UserShadowStack) or other Windows exploit protections as a general workaround. If the failure persists, send the details to support for version-specific diagnosis. Keep existing protections enabled while the cause is unknown.

Differences Between Free and Professional Versions#

Regarding maps:

• The Free version provides access to ArcGIS, Bing, and Google Maps.
• The Professional version offers additional map sources with superior image quality and more frequent updates.

Regarding features:

• The Free version is limited to medium image quality, while the Professional version supports high-quality settings.
• The Free version does not include map color adjustment capabilities.
• The Free version does not support the preloading feature.
• The Free version does not support high-resolution ground textures.

New features and optimizations are typically introduced in the Professional version first.

WinFSP Mounting Errors (Windows)#

Please check if the base package and X-Plane are on NTFS drives. Other file systems like exFAT are not supported for mounting.

If you have installed other versions of WinFSP, please uninstall them and keep only the latest version.

Fuse-T or base-package downloader errors (macOS)#

Reinstall Fuse-T first if mounting fails. If the base-package downloader reports that aria2 cannot load libsqlite3.dylib, libssh2, or gettext, check that Apple Silicon Homebrew is installed under /opt/homebrew, then run:

brew reinstall sqlite libssh2 gettext aria2

An Intel/Rosetta Homebrew installation under /usr/local may not provide the ARM libraries required by the application. See issue #599 for the confirmed example.

max_threads is an unknown FUSE option (Linux)#

This option requires libfuse 3.12 or later. In XPlane Map Enhancement 4.7.10 or later, open Advanced Settings and remove options unsupported by your installed libfuse version. Alternatively, upgrade to a supported Linux distribution instead of manually replacing system libraries. See issue #557.

Trees on Runways#

Please upgrade to the latest base package >=3.2.0

Why do tree colors not match the season?#

This issue has been resolved in the new version. Please update to the latest software and base package.

Why is my runway uneven, and how do I fix it?#

Work through these steps in order:

1. Enable the “Airport Flattening” feature first. Use the software to flatten the affected airport. This adjusts terrain within the airport area so runways and airport facilities display correctly.
2. If the problem remains, submit a report. Open a GitHub Issue and include the airport name or coordinates and a screenshot so the problem can be investigated.

Upgrade the base package#

If you have an older version of the base package, you can safely download the new version. The software will automatically overwrite the old files with the new ones. However, if you have made any modifications to the base package, please back up your files before proceeding.

Base-package download repeatedly fails or restarts#

Check these items before changing download-thread settings:

• Make sure the target disk has enough free space. A full disk can make a download stop or repeatedly fail verification.
• Keep the base package, cache, and custom data outside the application installation directory. Installers replace the application directory during a clean update.
• Check directory permissions and whether antivirus, a proxy, or a VPN is scanning or modifying downloaded files.
• Retry the operation; compatible partial files are kept so the download can continue.
• On macOS, also check the Homebrew/aria2 dependencies described above.

If you only noticed .zip.aria2 files or ZIP files disappearing after installation, first read Confirm installation is complete. These observations do not necessarily mean installation failed. If the standard download is slow, use manual installation and offline downloads.

Reported X-Plane Running, But It’s Not#

Please check if there is a process named X-Plane running. If so, terminate it in the Task Manager. Sometimes, certain plugins may prevent X-Plane from exiting properly, causing the interface to close while the process remains active.

My XPlane Crashed#

First identify whether X-Plane, XPME, or both closed. A crash alone does not establish whether the cause is the simulator, scenery, enhancement application, other plugins, or system resources.

1. Save the logs first: before restarting, copy the complete Log.txt from the X-Plane installation folder for the affected session, along with error screenshots. If a crash report was generated, keep the corresponding files in Output/Crash Reports. Do not send only the last log line; the last scenery or plugin named is not necessarily the cause.
2. Retest the same scenario: record the airport, aircraft, crash stage, and recent version or settings changes. Change one thing at a time. Confirm X-Plane has exited, then use Stop Service in XPME before adjusting settings. For each retest, start the XPME service before launching X-Plane.
3. Check scenery and plugins: check the relative positions of airports, overlays, and base packages using the scenery ordering guidance. Save plugin settings and back up Custom Scenery/scenery_packs.ini, then temporarily disable suspected plugins or scenery packs one at a time and restore them after testing. Follow the reversible scenery test; do not delete purchased scenery or plugin folders.
4. Try clearing the cache: exit X-Plane and stop the XPME service, then use the application’s cache settings to clear the cache and test the same scenario for another crash. Images must be downloaded again, so the first load will take longer. Do not delete base packages or entire scenery folders as a cache-clearing step.
5. Check resources and stability: monitor RAM, VRAM, free disk space, and disk I/O errors when reproducing the crash. If memory is tight, try Memory Optimization, which may increase stuttering. On Windows, check whether virtual memory is system-managed. Record XPME, X-Plane, and graphics driver versions. If you use CPU/GPU overclocking, save the settings and test at default clock speeds.

If the crash persists, provide X-Plane’s complete Log.txt, operating system and application versions, base-package version and mode, primary and fallback maps, airport and aircraft, reproduction steps, and the result of each test when asking for help.

Blurry Maps#

Blur can come from imagery still loading, limited source detail, texture settings, or VRAM pressure—not only the network.

• Check loading status first: if Failed keeps increasing or text appears on black tiles, run Diagnostics for both providers. If you only see default scenery, follow scenery-loading troubleshooting to check base packages and their order.
• Compare providers at the same location: wait for imagery to load before comparing clarity. Offline scenery such as Ortho4XP stores imagery in advance, so its loading speed is not directly comparable to streaming. For a clarity comparison, also consider whether the source imagery and resolution match.
• Distinguish the two quality settings: XPME’s Ground Resolution and X-Plane’s Texture Quality are separate. Low simulator texture quality can reduce clarity; check VRAM use before increasing it. If VRAM is tight, try lowering XPME’s ground resolution or other demanding graphics options, then retest the same scenario.
• Test preloading separately (Pro): if enabled, turn it off for comparison. Try enabling it when loading is stable and network, CPU, and memory capacity allow. Restore the previous setting if it makes loading slower or less smooth.
• Old imagery after switching maps: follow When a map change takes effect to reload scenery; an unchanged frame does not establish a network failure. See network parameter guidance below.

Slow Map Loading#

Loading time depends on the flight area, cache, quality settings, computer performance, storage, and network. There is no universal loading time or required image count.

Read Loaded, From Cache, and Failed alongside the simulator’s loading progress; see Checking initial loading status. If Failed keeps increasing, run Diagnostics to check the primary and fallback providers. If Loaded or From Cache increases, failures are not steadily rising, and the simulator is progressing, you can continue to observe.

If loading stalls or is noticeably slower than previous runs of the same scenario, work through these checks:

• Check whether antivirus scanning is actually affecting the base package. Keep protection enabled and follow Setup antivirus software before considering any narrow exception.
• Save the current configuration, then temporarily disable suspected plugins one at a time using their supported controls. Restore each setting after the test; do not delete Resources\plugins.
• For suspected scenery conflicts, back up the load-order file and use the reversible scenery test below.
• Users of VPN software such as NordVPN have reported slow scenery loading. If you use it, check its connection, routing, and network-protection settings. If your selected map providers are directly reachable, record your settings, temporarily disconnect the VPN, and compare loading in the same area. Restore the connection afterwards. If the issue occurs only with the VPN enabled, report your settings and test results to the VPN provider.

Adjusting network parameters#

Record your current settings and change one at a time in the same scenario. Restore each setting if it does not help. Current defaults are a troubleshooting starting point, not necessarily the best values for every connection.

If the disk is continuously busy or low on space, check the base-package and cache storage too; network settings alone may not help. Before relocating directories, exit X-Plane and stop the XPME service, then select the correct paths in the application settings.

Why is My Gigabit Network Still Slow?#

Your home broadband rate is not the same as actual map-server download speed. Routing, proxies, and server responses affect downloads; imagery processing and scenery reads also depend on CPU, memory, and storage performance.

Use Diagnostics to compare access to the primary and fallback providers, then check loading counters and system resource use to decide whether to investigate the network or the computer. A successful broadband speed test does not rule out loading problems.

Scenery order and SimHeaven / Overlays#

What each scenery type provides#

Ordering scenery_packs.ini#

Load order is controlled by X-Plane/Custom Scenery/scenery_packs.ini; entries nearer the top have higher priority. Before editing, exit X-Plane, stop the XPME service, and back up the file.

With XPME regional packages, the main entries should appear from top to bottom as follows:

1. Custom airports, Global Airports, and local scenery that needs priority, following each scenery author’s ordering instructions.
2. Third-party overlays such as SimHeaven. Keep SimHeaven’s own layers in the order specified by the manual for your installed version.
3. XPME_Overlays, only when installed and enabled, above the other XPME regional packages.
4. Installed and enabled XPME regional packages, forming the XPME group at the bottom.

With automatic scenery reordering enabled, XPME reorders base packages each time it starts. Disable that option first if you need to manage a special order manually. Do not delete the entire scenery_packs.ini to reset the order.

When X-Plane Original Base Package Enhancement is enabled, the application switches modes instead of enabling XPME regional packages and XPME_Overlays alongside it. Do not add those entries manually to match the regional-package order above. See the feature guide for the difference between modes.

Using SimHeaven#

Install the SimHeaven regions you need and the libraries required by your version. X-WORLD’s vegetation library must be installed and linked as instructed. If Log.txt reports missing simheaven/forests/... resources, check the vegetation library using the SimHeaven FAQ.

If you choose SimHeaven as your overlay provider, you can disable the buildings/trees overlay package (XPME_Overlays) in the XPME downloader without deleting its files. First check that SimHeaven covers the regions you fly in; areas without another overlay may lack buildings or roads after disabling XPME’s overlay. Layer names and requirements can differ between X-WORLD and X-WORLD Pro versions, so follow the manual supplied with your version.

Diagnostics report a missing XPME_Overlays entry#

Check the base-package mode and the package’s installed/enabled status in the downloader:

• An entry is not required when the package is uninstalled, disabled, or you are using Original Base Package Enhancement. XPME removes manually added entries for disabled packages when it starts.
• If installed and enabled, start the XPME service before running diagnostics; the application adds the relevant entries at startup. If the entry is still missing, provide the diagnostic results and scenery_packs.ini.
• If diagnostics report a non-XPME entry after the XPME entries, check the exact path named in the message. Airports and overlays belong above the XPME group. For overlapping Ortho4XP or HD Mesh scenery, use the test below to choose the terrain you want, rather than moving a line solely to pass diagnostics.

For more on load order, see the official X-Plane guide.

Game Images Not Loading, Still Showing Default Scenery#

• Confirm that the package for your flight area is installed and enabled, and start the XPME service before launching X-Plane.
• Check the active base-package mode and load order using the scenery-order guide. Visible buildings or roads and increasing imagery counters do not, by themselves, prove that X-Plane is using the XPME terrain.
• Ortho4XP or another base mesh covering the same area can take priority over XPME. Test only the suspected conflicting scenery rather than deleting it.

For a reversible test:

1. Exit X-Plane, then stop the XPME service and exit the app. Back up Custom Scenery/scenery_packs.ini.
2. Locate the specific third-party scenery entry for the affected area. Change only its SCENERY_PACK prefix to SCENERY_PACK_DISABLED, keeping the path unchanged. Do not disable XPME or default global scenery indiscriminately.
3. Start XPME and X-Plane in the usual order and test the same location.
4. After exiting X-Plane and stopping XPME again, restore that entry’s original prefix unless you have chosen to leave the confirmed conflicting pack disabled. Keep its files for future use.

If you cannot identify the entry, ask for help before editing. X-Plane documents this mechanism in Prioritization of Scenery Packs.

Examples of scenery that can take priority in overlapping areas:

• Ortho4XP
• X-Plane HD Mesh Scenery

Network Errors#

A few network errors are normal. However, if you encounter many errors in a short period, it indicates network access or configuration issues. Please refer to the previous settings for troubleshooting.

Black Squares with Text#

Black squares with text appear when map tiles fail to load, typically due to network connectivity issues. If only a few appear occasionally, this is not a concern. However, if numerous black squares persist, consider switching to a different map provider or troubleshooting your network connection.

Sudden Terrain Gaps#

Possible causes:

• Network connectivity issues are the most common cause. These gaps typically resolve themselves after a short period.
• Insufficient system memory. If you’ve disabled or significantly limited your system’s virtual memory, this can lead to memory shortages. Enhanced maps require substantial memory resources to function properly.

High CPU Usage During Loading#

High CPU usage during map loading is expected behavior. The process involves handling and processing a large number of high-resolution images, which is computationally intensive. While ongoing optimizations are being implemented, this remains a resource-intensive operation.

Note that the preload feature may cause particularly high CPU usage when high-resolution ground textures are enabled. If you experience performance degradation in the simulator, consider temporarily disabling this feature.

Occasional Stuttering During Gameplay#

X-Plane is designed to load scenery assets from local storage, which offers consistent access times. However, with enhanced maps, these assets are retrieved over the network. When network conditions are suboptimal, request times may exceed 10 seconds, resulting in temporary stuttering.

Additionally, the processing and compression of numerous images contribute to CPU load, which can affect performance. To mitigate these issues, it’s strongly recommended to enable the “Preload” feature, which caches map data in advance.

How to fix terrain issues using Ortho4XP#

The base package is built with Ortho4XP. To create the tile that contains an affected airport and repair terrain, follow these steps:

1. Download and install the public Ortho4XP project.
2. Use the airport coordinates to generate the corresponding zOrtho4XP_+latitude+longitude tile. Use Z16 to match the XPME base package.
3. Close XPME and back up the base-package files that you are about to replace.
4. Copy the generated tile’s .dsf files from Earth nav data, preserving their latitude/longitude grouping folders, into the Earth nav data directory of the XPME_* base package that owns the tile.
5. Copy the generated tile’s textures files into the _textures directory of the same XPME_* base package.
6. Start XPME and confirm whether the issue is resolved. If you do not know which XPME_* package owns the tile, do not overwrite files; submit a report with the airport name, coordinates, and screenshot instead.

If you fixed the terrain and you’d like to share the tile with others, please create a pull request on the GitHub repository. We welcome contributions from the community.

Is XP11 Supported?#

X-Plane 12 is recommended. X-Plane 11 is not officially supported; although some users have run it with older base packages, compatibility and loading performance are not guaranteed.

If you continue using X-Plane 11, use only base-package version 3.1.0; later base-package versions are incompatible. Here, 3.1.0 is the base-package version, not the XPME application version. Check the base-package version and directory guidance when downloading and installing; do not use a base-package version intended for X-Plane 12.

Why is CPU Usage So High?#

X-Plane 12 doesn’t natively optimize for enhanced map processing, requiring the application to handle substantial image processing and DDS file operations. This naturally results in elevated CPU utilization. Continuous optimization efforts are ongoing, but the resource-intensive nature of these operations remains a challenge.

Device Blocked#

First distinguish the exact message:

• Version is too old: update XPlane Map Enhancement and retry.
• Network connection failed, a timeout, or HTTP 500: keep the full error, check the application’s network and proxy settings, and try another network if possible. A status code alone does not identify the cause.
• Device blocked / License blocked: check the device and activation guidance and contact the author. Do not repeatedly purchase or unlink to try to restore access.

License activation, renewal, and devices#

See the license guide for full instructions. MSFS and XPlane licenses are not interchangeable.

• Purchase and activation: start at the official license website and follow the purchase instructions. Check the name, email, and product in your license confirmation, then click Link Device on the application’s License page. See the activation steps.
• Renewal: use the same product, name, and email as your existing license, then link in the application and check the expiry date. Follow the renewal instructions if the date has not changed; do not unlink or pay again to refresh it.
• Hardware changes or OS reinstall: these can change the device ID. Try linking with your existing name and email. If the device is blocked or the license is already in use, contact the author.
• Moving or using multiple computers: one license is for one device. Linking a new computer invalidates the previous activation and blocks the old device ID from linking that license again. Each computer needs a separate license; follow the multiple-device instructions.
• Forgotten name or email: check your license confirmation and spam folder. If you cannot find it, follow the support instructions and send order details privately, not in a public group or GitHub issue.

Additional Support#

For any other questions or issues not addressed in this manual, please submit an issue at: https://github.com/derekhe/xplane-map-enhancement-release/issues