Use X-Plane 12 Addon Linker correctly: organise an external library, build profiles, repair broken links, and preserve scenery and plugin order.
X-Plane 12 Addon Linker manages add-ons by keeping their real folders in an external library and creating filesystem links in X-Plane’s normal add-on folders. Set the simulator and library paths, classify each package, enable the required items or profile, then check scenery order, dependencies and X-Plane’s Log.txt before flying.
What does X-Plane 12 Addon Linker actually do?
The utility acts as a switchboard between an external add-on library and your X-Plane 12 installation. Enabling an item creates a symbolic link or directory junction that X-Plane treats as an ordinary folder; disabling it removes the link without deleting the source package.
This is different from a Windows .lnk shortcut, which X-Plane cannot use as an add-on directory. Addon Linker also does not make incompatible packages work, install missing libraries or automatically determine scenery priority.
A linked package remains writable. If an aircraft updater, plugin or X-Plane itself changes files through the link, it changes the copy in your external library, so keep a separate backup.
How do I set up and use Addon Linker?
The safest setup uses a stable library location, one clearly identified package per folder and no duplicate physical copy inside X-Plane.
- Close X-Plane 12. Back up third-party content and
Custom Scenery/scenery_packs.inibefore moving an existing installation. Our folder-by-folder X-Plane add-on installation guide explains where each package would normally go. - Create an external library. Use a permanent local path such as
D:\X-Plane Addons, with subfolders for aircraft, scenery, plugins, scripts and liveries. Avoid removable drives or drive letters that may change. - Extract each download completely. Remove unnecessary wrapper folders so the directory you register is the actual package root. Do not place archives directly in the library and expect the linker to extract them.
- Configure the paths. Select the main X-Plane 12 directory and add your external library folders as sources. Where the utility asks for an add-on type or destination, assign the normal X-Plane folder shown below. Button and field names can vary between releases.
- Scan and enable one test package. Confirm that a filesystem link appears in the expected X-Plane folder. If a physical folder with the same name already exists there, remove or rename the duplicate before creating the link.
- Build a profile or preset. Start with a small group and include every required library, plugin or companion scenery package. Switch profiles only while X-Plane is closed.
- Launch X-Plane and verify the result. Check the aircraft browser, airport scenery or plugin list as appropriate. If the package is missing, search
Log.txtin the X-Plane root for its folder name or an associated loading error.
Which X-Plane folders should linked add-ons use?
Every linked package must appear at the same destination and folder depth it would use during a manual installation.
| Add-on type | Link destination | Key check |
|---|---|---|
| Aircraft | X-Plane 12/Aircraft | Link the folder containing the aircraft’s .acf file, not an outer download wrapper. |
| Scenery | X-Plane 12/Custom Scenery | Multi-part airports, overlays and meshes may need several separate linked folders. |
| Global plugin | X-Plane 12/Resources/plugins | Link the plugin’s own root folder. Aircraft-specific plugins must remain inside that aircraft package. |
| FlyWithLua script | X-Plane 12/Resources/plugins/FlyWithLua/Scripts | The required scripting plugin must already be installed; a Lua script is not a standalone global plugin. |
| Livery | Aircraft folder/liveries | Target the correct aircraft and variant. Similar aircraft names do not guarantee livery compatibility. |
Scenery deserves extra attention. Addon Linker controls whether a pack is present, but X-Plane still reads scenery_packs.ini to decide its priority. After enabling new scenery, follow the normal hierarchy for airports, overlays and mesh described in our scenery ordering and overlay instructions.
How should profiles be organised?
Profiles work best when they represent a region, aircraft type or flying setup rather than a random collection of packages.
- Always-on items: shared libraries, essential utilities and plugins used by several profiles.
- Regional scenery: airports, overlays, orthophotos and mesh for one operating area.
- Aircraft groups: airliners, general aviation, helicopters or test aircraft that need not all remain active.
- Troubleshooting profile: one aircraft and minimal scenery or plugins, useful for finding conflicts.
If your release supports only one active preset at a time, include common dependencies in every relevant preset. Disabling a scenery library while leaving airports that require it enabled typically produces missing objects or loading warnings.
Why is an enabled add-on missing or broken?
Most Addon Linker failures come from an incorrect folder level, a broken source path, a destination collision or an unresolved dependency.
| Symptom | Likely cause and fix |
|---|---|
| Enabled aircraft is absent | The link points to a wrapper folder above the package. Re-link the directory that directly contains the .acf file. |
| Two copies of an aircraft or airport appear | A manually installed copy and a linked copy are both active. Keep only one installation. |
| Link is broken after restarting the PC | The external drive is unavailable, its letter changed or the source folder was moved. Restore the path, then rescan or recreate the link. |
| Link creation reports an access error | A same-named destination exists, or the utility lacks permission to create filesystem links. Remove the collision and use the operating system’s required link permissions. |
| Airport has missing buildings or terrain | A library, overlay or mesh component is disabled, incompatible or in the wrong scenery_packs.ini position. |
| Plugin does not appear | The plugin is nested too deeply, lacks a compatible platform binary or failed during loading. Use these plugin verification and reload checks and inspect Log.txt. |
| Disabled item remains active | X-Plane already loaded it into the running session. Close the simulator, change the profile and restart. |
Moving a source package after it has been linked breaks the existing link. Disable it first, move it within the external library, update or rescan the source path, and then enable it again.
Can Addon Linker make X-Plane 11 add-ons work in X-Plane 12?
No; the linker changes where an add-on is stored, not its simulator compatibility. Before adding older aircraft, scenery or plugins to a profile, check the X-Plane 11-to-12 compatibility issues, including flight-model changes, deprecated plugins and scenery differences.
Does Addon Linker need to stay open?
No, it normally does not need to remain open after the filesystem links have been created. Close X-Plane before disabling packages or changing profiles, however, because loaded aircraft, scenery and plugin code will not reliably disappear from an active session.