Install X-Plane 11 and 12 mods correctly: aircraft, scenery, plugins, liveries and FlyWithLua scripts, plus fixes when nothing appears.
To install mods in X-Plane 11 or 12, extract the archive, identify the add-on type, and copy its complete folder to the correct location: Aircraft, Custom Scenery, Resources/plugins, or the matching aircraft's liveries folder. FlyWithLua scripts go in FlyWithLua/Scripts. Restart X-Plane and check Log.txt if nothing appears.
A browser download does not install itself. Save the archive to a temporary location, extract it completely, and inspect the contents before copying anything into X-Plane. Our X-Plane aircraft, scenery and add-on downloads are organised by content type, but each package can still have its own requirements and instructions.
Where do I put an aircraft mod in X-Plane 12, and where do other mods go?
Put an X-Plane 12 aircraft mod under the simulator's Aircraft folder, keeping the aircraft's .acf file, objects, sounds and plugins together in their original folder structure. X-Plane 11 uses the same destination.
The starting point is the X-Plane root folder: the directory containing the simulator application and folders such as Aircraft, Custom Scenery and Resources. It is not necessarily your Downloads folder, Steam library root or desktop shortcut location. If you have several installations, our instructions for identifying the X-Plane 11 folder that is actually being launched help prevent copying a mod into an inactive installation.
| Add-on type | Destination inside the X-Plane folder | How to recognise it |
|---|---|---|
| Aircraft | Aircraft/Aircraft Name, optionally inside a category folder | The aircraft folder contains one or more .acf files plus its supporting content |
| Airport, overlay, mesh or scenery library | Custom Scenery/Package Name | Common contents include Earth nav data, objects, terrain, textures or library.txt |
| Global plugin | Resources/plugins/Plugin Name | A complete plugin folder containing binaries and supporting files |
| Aircraft-specific plugin | Aircraft/Aircraft Name/plugins | Supplied as part of one aircraft and loaded only with that aircraft |
| FlyWithLua framework | Resources/plugins/FlyWithLua | The complete FlyWithLua plugin, not an individual Lua script |
| FlyWithLua script | Resources/plugins/FlyWithLua/Scripts | Usually one or more .lua files, sometimes with support folders |
| Livery | Aircraft/Aircraft Name/liveries/Livery Name | A paint scheme made for one specific aircraft and variant |
| Sound, cockpit or systems patch | Inside the specified existing aircraft folder | Replacement files intended to merge with a particular aircraft |
Do not create one general Mods folder and put everything there. X-Plane has no universal mod directory. It discovers each content type through the locations shown above.
A livery is not a standalone aircraft, and a plugin is not installed by moving only its executable file. Likewise, ordinary third-party scenery belongs in Custom Scenery, not Global Scenery.
How do I install an X-Plane mod step by step?
The reliable method is to extract the package outside X-Plane, find the actual add-on folder, and copy that folder without flattening or rearranging its contents.
- Close X-Plane. Plugins, scripts and scenery may remain loaded while the simulator is running. Installing or removing them with X-Plane closed avoids locked files and incomplete reloads.
- Check the requirements. Confirm X-Plane 11 or 12 support, the required operating system, any base aircraft and all dependencies. Compiled plugins must support your operating system and processor architecture.
- Extract the archive completely. X-Plane cannot load a mod from a compressed
.zip,.raror.7zfile. Do not drag selected files directly from an archive preview. - Find the real package root. Downloads often contain an outer wrapper with documentation, screenshots and the folder that must actually be installed. For aircraft, find the folder containing the
.acffile. For scenery, find each folder containing its scenery data. Ignore documentation-only and system-generated folders. - Read the supplied instructions. A trusted package's documented layout takes priority over the general paths above, especially for installers, linked scenery, aircraft patches and add-ons that generate files.
- Back up anything that will be overwritten. Standalone aircraft and scenery are easy to remove. Sound packs, cockpit replacements and systems modifications may merge into an existing aircraft, so duplicate that aircraft folder first.
- Copy the complete add-on folder. Preserve all subfolders. Do not move an aircraft's
.acffile by itself, scatter plugin files intoResources, or separate Lua scripts from required modules. - Check for accidental double nesting. A path such as
Custom Scenery/Downloaded Package/Actual Airport/Earth nav datais normally one folder too deep. The actual airport folder should be directly underCustom Scenery. Global plugins have the same problem when installed asResources/plugins/Plugin Name/Plugin Name. - Restart and test the right content. Select the installed aircraft or livery, load the affected airport, or start a flight if the plugin activates only after loading completes.
- Inspect
Log.txtafter a failure. The file is in the X-Plane root and records aircraft, scenery, plugin and script loading errors from the latest session.
Plugins contain executable code. Use packages from a source you trust, scan downloaded archives, and do not follow instructions that require disabling operating-system security globally.
X-Plane 11 mod compatibility with X-Plane 12
If you mean X-Plane 11 rather than X-Plane 12, the main installation folders and procedure are the same. Compatibility is the part that changes.
An X-Plane 11 mod is not automatically an X-Plane 12 mod. Liveries and uncomplicated scenery often transfer when their base aircraft and dependencies match, but aircraft flight models, lighting, sounds, systems plugins and Lua scripts may rely on features that changed. Check our practical compatibility checks for X-Plane 11 add-ons in X-Plane 12 before moving an older package across.
Do not assume that an aircraft is compatible merely because it appears in the selector. It may load while its displays, controls or aircraft-specific plugin fail.
Installing FlyWithLua in X-Plane 12
Install an X-Plane 12 compatible FlyWithLua framework under Resources/plugins, then place compatible scripts in its Scripts folder.
- Verify the FlyWithLua download. The framework package must explicitly support X-Plane 12 and your operating system. A lone
.luascript is not the FlyWithLua framework. - Extract the framework. Locate the actual
FlyWithLuafolder inside the archive. - Copy it into the plugin directory. The resulting path should be
X-Plane 12/Resources/plugins/FlyWithLua, notResources/plugins/FlyWithLua/FlyWithLua. - Launch X-Plane once. Confirm in
Log.txtthat the framework loaded before adding third-party scripts. This separates framework installation errors from script errors. - Close X-Plane and install the script. Put its
.luafiles inResources/plugins/FlyWithLua/Scripts. Preserve any modules, configuration files or support folders specified by the script's instructions. - Load a flight and check the result. Many scripts initialise only after an aircraft and flight have loaded.
FlyWithLua compatibility and script compatibility are separate. The framework can load correctly while an old script fails because it uses changed datarefs, commands or unsupported functions. If you used a Lua tool and still nothing happens, confirm that FlyWithLua loaded first, check whether the script was disabled or quarantined after an error, and read both its messages and Log.txt.
Scenery and scenery_packs.ini
Install each actual scenery package directly under Custom Scenery, then adjust scenery_packs.ini only if scenery is disabled, hidden or loading at the wrong priority.
Keep custom airports above the simulator's global airports, overlays above orthophoto or base-mesh packages, and base meshes near the bottom. Missing buildings or objects usually indicate an absent scenery library rather than an airport load-order problem. Our detailed X-Plane 12 scenery installation and load-order procedure covers packages containing several folders, required libraries and competing meshes.
Close X-Plane before editing Custom Scenery/scenery_packs.ini in a plain-text editor. Any entry beginning with SCENERY_PACK_DISABLED will not load.
Why is my X-Plane mod not showing up or still doing nothing?
If a mod is not showing up, check the active X-Plane installation, folder depth, version compatibility and dependencies before reinstalling anything.
Reproduce the problem, quit X-Plane, and open the root Log.txt. Search for the add-on name and terms such as ERROR, failed and not found. The log is rewritten by later sessions, so inspect it before launching X-Plane again.
- Wrong X-Plane copy: confirm that the application you launch belongs to the same root folder where you installed the mod. This is especially common when separate X-Plane 11, X-Plane 12, test or backup installations exist.
- Archive not extracted: files left inside a compressed archive cannot be loaded by X-Plane.
- Extra folder level: find the folder containing the
.acf, scenery data or plugin files and remove any unnecessary wrapper above it. - Unsupported version: an old aircraft, plugin or Lua script may appear but fail partly or completely in a newer simulator.
- Missing dependency: scenery may need object libraries, while a script may need FlyWithLua and additional modules.
- Wrong test conditions: scenery changes only its covered location, a livery appears only with its matching aircraft, and some plugins activate only after a flight loads.
- Security or architecture failure: a compiled plugin may be blocked or may not support the operating system or processor in use.
- Conflict: two plugins or Lua scripts may try to control the same datarefs. Temporarily remove one suspect add-on at a time and retest.
Symptom-specific fixes
The symptom usually indicates which part of the installation failed.
- Aircraft is absent: verify that its folder contains an
.acffile, clear aircraft-selector filters and check that it is inside the active installation'sAircraftfolder. - Aircraft loads with dead displays or systems: its aircraft-specific plugin probably failed, was blocked or lacks a required component. Search
Log.txtfor the aircraft and plugin names. - Airport has runways but no buildings: install the required scenery libraries and look for unresolved object paths in the log.
- Default terrain covers downloaded scenery: check for a disabled entry, incorrect
scenery_packs.inipriority or competing base mesh. - Plugin has no menu entry: some plugins run in the background. Use
Log.txtto establish whether it loaded instead of relying on the menu alone. - FlyWithLua script does nothing: verify that the framework loads, confirm the script is in
Scripts, and test it without other scripts that alter the same controls or datarefs. - Livery is missing: use the exact aircraft and variant for which it was painted, then check for a duplicated folder level beneath
liveries.
Windows, macOS and Linux failures
The main X-Plane folder layout is the same across supported desktop operating systems, but plugin loading can fail for platform-specific reasons.
- Windows: protected folders, security controls or incomplete extraction can prevent a plugin from loading or writing its configuration.
- macOS: system security may block an untrusted downloaded binary. Verify the package and use the operating system's normal approval process rather than disabling protection globally.
- Linux: filename capitalisation, file permissions and missing system components can affect plugins. Paths that differ only by upper- and lower-case letters are not interchangeable.
The mistake we see most often is reinstalling the whole simulator before checking the active X-Plane path and Log.txt. A failed third-party add-on rarely requires a complete X-Plane reinstall.
How do I uninstall an X-Plane mod?
Uninstall a standalone X-Plane mod by closing the simulator and removing the complete folder or script that you originally added.
- Aircraft: remove its complete folder from
Aircraft. - Scenery: remove every associated package from
Custom Scenery. With X-Plane closed, remove any stale entry fromscenery_packs.iniif it remains. - Global plugin: remove its complete folder from
Resources/plugins. - FlyWithLua script: remove the script and any support files created specifically for it. Remove the entire
FlyWithLuafolder only if you want to uninstall the framework and all of its scripts. - Livery: remove that paint scheme's folder from the matching aircraft's
liveriesdirectory. - Shared scenery library: remove it only when no remaining scenery package depends on it.
If a cockpit, sound or systems patch overwrote original aircraft files, deleting the new files may leave the aircraft incomplete. Restore the backup made before installation or reinstall a clean copy of the base aircraft. Do not erase all X-Plane preferences to remove one mod unless its documentation identifies a specific preference or configuration file that it created.