AutoOrtho X-Plane 12: how do I install and use it?

To install AutoOrtho in X-Plane 12, download the packaged Windows or Linux build from the official AutoOrtho project’s GitHub Releases page, install WinFsp or FUSE, set the X-Plane root and cache paths, install a region, then mount AutoOrtho before launching X-Plane. Keep it mounted throughout the flight.

How does AutoOrtho work in X-Plane 12?

AutoOrtho presents streamed and cached aerial imagery to X-Plane 12 as a virtual scenery filesystem. It is an external application, not an X-Plane plug-in, so it does not belong in Resources/plugins.

Its regional packages provide the scenery structure and coverage, but installing a region does not necessarily download every image tile. AutoOrtho fetches much of the imagery when required, writes it to a local cache and supplies it through the mounted scenery folders.

This reduces the initial download compared with conventional orthophotos, but adds four dependencies: a working filesystem driver, a successful mount, a writable cache and sufficient network performance for uncached tiles.

How do I download and install AutoOrtho for X-Plane 12?

Download AutoOrtho from the Releases page of the official kubilus1/autoortho GitHub project, not from the repository’s general source-code download button or an unofficial mirror.

1. Open the latest supported release. Read its notes for operating-system requirements and any upgrade warnings.
2. Select the packaged asset for your operating system. Choose the Windows or Linux application package supplied under the release’s assets. Do not choose the automatically generated Source code (zip) or Source code (tar.gz) archive unless you deliberately intend to build and maintain the application yourself.
3. Verify the download. Confirm that the asset name identifies your operating system and architecture, that it is attached to the intended release tag, and that the version shown by the extracted application or startup log matches that release. Compare a published checksum if the project supplies one.

Search results sometimes use the name AutoOrtho-Continued. Do not assume that any similarly named fork is an official replacement: use a continued release only when the original project’s own documentation or release notice directs users to it. Mixing executables, configuration files and regional packages from unrelated builds can produce mount and upgrade failures.

Windows prerequisites: install WinFsp first

AutoOrtho on Windows requires WinFsp to provide the virtual filesystem used by X-Plane.

1. Install WinFsp. Use its normal filesystem components and restart Windows if the installer requests it. If AutoOrtho’s packaged installer offers the required WinFsp component, allow that step to finish before configuring X-Plane.
2. Install or extract AutoOrtho outside X-Plane. Use a normal user-writable application folder rather than Custom Scenery or a protected system directory.
3. Run both applications at the same privilege level. We recommend running AutoOrtho and X-Plane normally under the same Windows account. Running one as administrator and the other as a standard user can prevent X-Plane from seeing the mount.
4. Allow cache writes. Check security software if AutoOrtho can start but cannot create or update files in its cache directory.

Linux prerequisites: configure FUSE and mount permissions

AutoOrtho on Linux requires FUSE support and permission for the desktop user running X-Plane to create and read the mount.

1. Install FUSE through the distribution’s package manager. Maintained Linux packages use FUSE 3; follow the release notes if a particular build names an additional compatibility library.
2. Grant user mount access. Ensure your account belongs to any FUSE-related group required by the distribution, then sign out and back in after changing group membership.
3. Check the FUSE configuration. If AutoOrtho’s log reports that allow_other is not permitted, enable user_allow_other in /etc/fuse.conf. Do not change this setting unless the mount configuration requires it.
4. Use user-writable locations. The application, mount point and cache must be accessible to the same account that starts X-Plane. Avoid launching AutoOrtho with sudo while running X-Plane as an ordinary user.
5. Start the packaged application. Give the downloaded executable permission to run if required by the package format, then confirm that it opens without FUSE or library errors.

Can I install AutoOrtho on macOS?

No supported native AutoOrtho Mac setup is provided by the official project for either Apple Silicon or Intel Macs. The published installation workflow and packaged releases support Windows and Linux, with WinFsp or FUSE respectively.

Installing macFUSE by itself does not make the Linux package compatible, and Linux terminal instructions should not be treated as macOS mount instructions. We do not recommend Wine, a virtual machine or an unmaintained community script as the normal setup because filesystem access, paths and performance differ from the supported workflow.

On a Mac, use X-Plane 12’s default terrain or install conventional, pre-generated orthophoto scenery directly in Custom Scenery. Our manual orthophoto installation instructions cover folder structure, mesh conflicts and load order without relying on AutoOrtho’s virtual mount.

How do I configure AutoOrtho for X-Plane 12?

Set AutoOrtho’s X-Plane location, cache and regional coverage before attempting the first mount.

1. Close X-Plane and back up the load order. Copy X-Plane 12/Custom Scenery/scenery_packs.ini to a safe location.
2. Choose a cache location. Use a fast, writable drive with ample free space. The cache grows as you visit new areas, so placing it on a nearly full system drive is a common cause of incomplete tiles.
3. Select the X-Plane root folder. When AutoOrtho asks for the X-Plane path, choose the directory containing the X-Plane executable, Aircraft, Custom Scenery and Resources. Select Custom Scenery only if the particular field explicitly asks for the scenery directory.
4. Install one test region. Choose a region containing a familiar airport and wait for downloading and extraction to finish. Testing one region makes path, mount and scenery-order faults much easier to isolate.
5. Start the virtual mount. Wait until AutoOrtho reports a mounted or running state. Its generated scenery locations should then be visible and readable within X-Plane’s scenery path.
6. Let X-Plane detect the entries. Start X-Plane while AutoOrtho remains mounted, reach the main menu, then close the simulator. X-Plane should add the detected packages to scenery_packs.ini.
7. Correct the scenery priority. Reopen scenery_packs.ini in a text editor and place airports above the overlay, and the overlay above AutoOrtho’s base terrain.

Do not manually move or rename mounted regional folders while AutoOrtho is running. If a scenery entry is not detected, check for a nested extraction folder or a disabled entry; our guide to finding X-Plane scenery folder and installation errors explains those common faults.

What should I verify before the first AutoOrtho flight?

Complete these checks after installation and before loading an airport in X-Plane 12.

• Region: the installed region covers the departure airport and surrounding flight area, and its download completed without an error.
• Mount: AutoOrtho reports a successful mounted or running state, and its generated scenery folders are readable.
• Cache: the cache directory is writable by the current user and has adequate free space.
• X-Plane path: AutoOrtho points to the intended X-Plane 12 installation, not an old copy or merely its Custom Scenery folder.
• Scenery order: airport packages are above the AutoOrtho overlay, and the overlay is above the AutoOrtho base or mounted regional terrain.
• User account: AutoOrtho and X-Plane are running under the same account and privilege level.

Where should AutoOrtho go in scenery_packs.ini?

AutoOrtho’s object overlay must be above its streamed base terrain, while airport packages should normally remain above both.

The top of scenery_packs.ini has the highest priority. Generated folder names can vary by release and region, so identify packages by their role instead of copying an old list verbatim.

X-Plane cannot blend two base meshes covering the same one-degree tile. Another orthophoto or terrain mesh placed above AutoOrtho can hide it completely. Also confirm that required entries begin with SCENERY_PACK, not SCENERY_PACK_DISABLED.

For more complex installations, our guide to ordering X-Plane 12 overlays and terrain explains how roads, buildings, airports and mesh packages interact.

How do I use AutoOrtho for each flight?

Mount AutoOrtho before starting X-Plane and unmount it only after X-Plane has closed.

1. Open AutoOrtho and confirm that the required region is installed.
2. Start the mount and wait for a successful mounted or running status.
3. Launch X-Plane 12 under the same user account and privilege level.
4. Load an airport inside the installed region. The first visit to an uncached area may take longer, and lower-resolution imagery may appear temporarily while tiles are fetched.
5. Monitor errors if scenery is missing. Check both AutoOrtho’s log and X-Plane’s Log.txt before changing folders or reinstalling packages.
6. Exit X-Plane first. Stop or unmount AutoOrtho only after the simulator has fully closed. Removing the virtual filesystem while X-Plane is reading it can cause missing-file errors or a crash.

Why is AutoOrtho not showing or loading correctly?

Missing AutoOrtho scenery is usually caused by a failed mount, incorrect X-Plane path, disabled entry, competing base mesh or incomplete regional installation.

If performance remains poor over fully cached terrain, the limiting factor may be X-Plane’s texture quality, world objects, antialiasing, rendering resolution or available VRAM rather than AutoOrtho’s network activity.

Can AutoOrtho be used offline?

AutoOrtho should not be treated as dependable offline scenery, even though previously downloaded imagery can remain in its cache.

An installed regional package does not guarantee that every aerial tile has been downloaded. Unvisited areas may still need internet access, while cache limits or maintenance can remove older files. For an offline computer or a flight where scenery availability must be predictable, conventional orthophoto packages are the safer option.

Should I use AutoOrtho or downloaded orthophotos?

Choose AutoOrtho for broad coverage with a smaller initial download; choose packaged orthophotos when offline reliability and fixed local files matter more than storage use.

Static packages use a different installation workflow and should not be mounted through AutoOrtho. Simmers considering another streaming approach can also use our comparison of AutoOrtho and X-Plane Map Enhancement to assess caching, performance and offline-use trade-offs.