Learn which X-Plane 11 add-ons work in X-Plane 12, what usually breaks, and how to test aircraft, scenery, plugins and liveries safely.
Some X-Plane 11 add-ons work in X-Plane 12, but compatibility is not universal. Liveries, airports and orthophoto scenery have the best chance; aircraft and plugins often need an X-Plane 12 update, while weather, shader and rendering tools are usually version-specific. “Loads successfully” does not necessarily mean “works correctly”.
Which X-Plane 11 add-ons work in X-Plane 12?
Scenery and liveries transfer most reliably, while complex aircraft, plugins and graphics modifications are much more likely to need an XP12-specific release.
| Add-on type | Compatibility prospect | What to check |
|---|---|---|
| Liveries | Often compatible | The XP12 aircraft must use the same model and texture layout. A livery made for an older aircraft revision may show blank, misplaced or incorrect textures. |
| Airport scenery | Usually compatible | Check required object libraries, runway alignment, exclusions, lighting and scenery order. |
| Orthophoto and mesh scenery | Often loads with caveats | Older mesh can replace XP12 terrain data and produce unexpected coastlines, water or elevation changes. |
| Simple aircraft | Mixed | Flight behaviour, instruments, sounds, lighting and cockpit controls may require adaptation. |
| Complex aircraft | Usually needs an update | Custom avionics, systems plugins, deprecated datarefs and flight-model changes are common failure points. |
| Plugins and scripts | Mixed | The plugin binary, script host, datarefs and graphics calls must all remain compatible with XP12. |
| Weather, shader and graphics tools | Usually incompatible | X-Plane 12 changed its weather, lighting and rendering systems, so XP11 modifications should not be assumed to work. |
The simulator generations differ in more than appearance. Our breakdown of the technical differences between X-Plane 11 and 12 explains why scenery often survives the move while aircraft systems and rendering tools do not.
Can I copy my X-Plane 11 add-ons into X-Plane 12?
Copy selected add-ons into X-Plane 12 one at a time; do not transfer the whole XP11 installation or point both simulators at the same writable add-on folders.
- Look for explicit XP12 support. Check the package documentation and file description for an X-Plane 12 build. Compatibility claimed by the author is more meaningful than reports that an add-on merely opens.
- Keep the original untouched. Test a copied folder, not your only copy. XP11 and XP12 editions of the same aircraft should remain in separate folders.
- Confirm the destination. Aircraft belong under
Aircraft, scenery underCustom Scenery, and global plugins underResources/plugins. An installer may still be pointing at the old XP11 directory. - Add only one item. Launch X-Plane 12 after each installation so a warning, crash or performance problem can be traced to a specific package. Our installation checklist for X-Plane add-ons covers the folder structure in more detail.
- Test the complete function. For aircraft, check cold-and-dark start-up, displays, controls, autopilot, sounds and flight behaviour. For scenery, inspect the location by day and night for missing objects, elevation faults and incorrect water.
- Read the log. After closing the simulator, inspect
Log.txtin the X-Plane 12 root folder. Search for the add-on’s name, failed plugin loads, missing libraries, script errors and unavailable datarefs.
Let XP12 maintain its own scenery_packs.ini. Copying the XP11 file blindly can leave invalid paths or put mesh, overlays and airports in the wrong order. Older orthophotos may load, but our XP12 Ortho4XP scenery guidance explains the water, coastline and mesh issues to inspect.
For commercial add-ons, technical compatibility and licensing are separate questions. Copy or install the package only where its licence permits, even if the files themselves work in both simulators.
How can I tell if an XP11 add-on is truly XP12 compatible?
An add-on is truly compatible only when its intended functions work without persistent errors, not simply because X-Plane 12 accepts the files.
- Aircraft: no blank displays, broken manipulators, missing sounds, start-up failures or obviously incorrect handling.
- Plugins: the plugin loads in
Log.txt, appears where expected and performs its actual function without repeated errors. - Scenery: no missing-library messages, floating objects, buried runways, duplicate airports or malformed coastlines.
- Liveries: exterior and cockpit textures align with the XP12 aircraft revision, including normal maps and any model-specific material files.
- Scripts: no continuous error loop, unavailable-command messages or references to datarefs removed or changed in XP12.
A common mistake we see is treating an aircraft that appears on the ramp as compatible. Its custom systems may not fail until the avionics are powered, the autopilot is engaged or a flight is loaded for the second time.
Can an X-Plane 11 aircraft be converted for X-Plane 12?
Opening or resaving an XP11 aircraft does not by itself convert it into a reliable XP12 aircraft.
A proper conversion may require flight-model adjustments, updated airfoils, cockpit and lighting work, new datarefs, revised sounds and replacement plugin code. Systems-heavy airliners generally need an author-supplied XP12 version. Even a simple aircraft should be modified only on a copy, and a commercial model must not be redistributed without permission.
What should I do if the XP11 add-on crashes X-Plane 12?
Remove the last add-on, confirm that X-Plane 12 starts cleanly, and then check Log.txt before changing anything else.
If the log identifies a plugin or script, install its XP12 edition or leave it removed. If the crash continues after the add-on has gone, another shared dependency or configuration file may be involved; follow our X-Plane 12 crash and start-up troubleshooting process to isolate it systematically.