Compare the best X-Plane 12 and 11 aircraft, plugins and scenery, with compatibility checks, install order, fixes and performance caveats.
The best add-ons for X-Plane 12 and 11 are the Zibo 737-800X for a free airliner, ToLiss aircraft for paid Airbus operations, AviTab and BetterPushback for cockpit utility, X-Camera for views, OpenSceneryX for airport dependencies, and carefully selected X-World overlays, mesh or orthophotos for scenery.
Which X-Plane 12 or 11 aircraft add-on should you choose?
For most airline-focused pilots, a ToLiss Airbus or the freeware Zibo 737 is the strongest starting point; business jets, classic long-haul aircraft and general aviation have better specialist choices.
No aircraft wins every category. We favour explicit simulator compatibility, credible flight and systems modelling, usable documentation and a clear advantage over X-Plane’s default fleet.
| Use case | Recommended aircraft | Main caveat |
|---|---|---|
| Airbus narrow-body | ToLiss A320neo or A321 for X-Plane 12; the A319 and A321 are also relevant to X-Plane 11 users | These are paid products. Check the exact simulator edition and included engine or airframe variants rather than assuming every configuration is supplied. |
| Free Boeing airliner | Zibo 737-800X | Install it separately from the default 737 and follow the documented full-package and update sequence. Mixing old base files with a newer patch causes many faults. |
| Business jet in X-Plane 12 | Hot Start Challenger 650 | Its detailed avionics, systems and cockpit preparation create a steep learning curve and make it excessive for quick flights. |
| Long-haul tri-jet in X-Plane 12 | Rotate MD-11 | The automation, handling and operating procedures are specialised; familiarity with a modern Boeing or Airbus does not transfer directly. |
| Long-haul Airbus in X-Plane 12 | ToLiss A340-600 | Choose it specifically for four-engine A340 procedures, not merely because you want any large passenger aircraft. |
| Modern GA and IFR in X-Plane 12 | Aerobask DA42 NG | Its glass cockpit and twin-engine management suit IFR touring, but not pilots seeking analogue instruments or tailwheel handling. |
| Bush and utility flying in X-Plane 12 | Thranda DHC-2 Beaver | Tailwheel technique and careful power management matter more than automation. |
| Earlier-generation Boeing operations in X-Plane 11 | FlightFactor 757 or 767 | Confirm support for your operating system, simulator release and X-Plane 11 graphics mode. |
| Detailed turboprop flying in X-Plane 11 | Hot Start TBM 900 | Its appeal is deeper engine and aircraft management rather than a short start-up and immediate departure. |
| General-aviation enhancement | Reality Expansion Pack | Each paid pack is tied to a specific base aircraft and simulator version; it cannot be transferred freely between models. |
Choose according to the real operating style that interests you. Airbus automation, 737NG flows and MD-11 systems are different enough that buying the most complex product is not automatically the best decision. In VR or on modest hardware, a lighter aircraft may also be more enjoyable than an airliner running several custom displays and aircraft-specific plugins.
What is the best free aircraft for X-Plane 12?
The Zibo 737-800X is the strongest free X-Plane 12 aircraft for pilots seeking detailed airliner systems, displays and flight-management functions.
Keep it in its own folder under Aircraft; never overwrite the default 737. Our curated X-Plane aircraft and add-on library also includes an XP12-specific 737-800 and BBJ2 package with passenger and business-jet configurations, but it is a separate aircraft rather than a Zibo update.
The common freeware mistake is treating “loads in X-Plane 12” as proof of compatibility. An older X-Plane 11 aircraft may appear in Flight Configuration yet still have broken displays, obsolete plugins, incorrect lighting or flight-model problems.
Which utility plugins are most useful?
AviTab, BetterPushback and X-Camera are useful when they solve a specific cockpit problem; FlyWithLua should be installed only when a required compatible script depends on it.
| Add-on | Best for | Main caveat |
|---|---|---|
| AviTab | Viewing maps, PDFs, checklists and flight documents in the cockpit | Aircraft integration varies, and the plugin does not supply licensed charts by itself. |
| BetterPushback | Planning, previewing and controlling airline pushback routes | Use a build intended for your X-Plane version. It adds little to light-aircraft flying. |
| X-Camera | Organised cockpit, external and tracking views | It may be unnecessary when X-Plane’s quick-look system already covers your needs. |
| FlyWithLua NG | Running compatible Lua utilities and aircraft scripts | It is a scripting framework, not an improvement by itself. Old scripts can generate errors or override datarefs, controls and graphics settings. |
| OpenSceneryX | Supplying reusable objects required by many freeware airports | It is a dependency library rather than a visual upgrade and cannot replace every separate library an airport may require. |
A mistake we see constantly is installing every popular plugin at once. Global plugins can consume CPU time, create duplicate commands or compete for the same datarefs, so each one should have a defined purpose.
Which scenery add-ons make the biggest difference?
A detailed airport and one regional terrain upgrade usually improve a familiar route more than a worldwide collection of scenery packages.
- Custom airports: These improve terminals, stands, markings, lighting and nearby objects. Install airports you use rather than filling
Custom Sceneryindiscriminately. - OpenSceneryX: Many freeware airports use its shared objects. Missing libraries can produce empty aprons, absent terminals or scenery-loading warnings; our OpenSceneryX installation and missing-object guide explains where the library belongs and how to diagnose dependency errors.
- Landmark and VFR packages: These are most useful for low-level flying around a particular city or region.
- X-World regional overlays: These add plausible buildings, roads, forests and regional objects to X-Plane 12. Install only the regions you need and retain the package’s documented internal layer order.
- HD Mesh Scenery v4: This is an established X-Plane 11 option for improved terrain shape, roads and landclass in supported regions.
- Orthophoto scenery: Aerial ground imagery is valuable for visual navigation in either supported simulator, but it requires considerable storage and may contain uneven colour, clouds or mismatched source imagery.
Legacy X-Plane 11 mesh and orthophoto packages may load in X-Plane 12 without using its water, vegetation or seasonal behaviour correctly. Read our practical comparison of Ortho4XP, photoreal scenery and terrain mesh before generating a large collection.
What scenery_packs.ini order should I use?
Detailed airports belong above broad overlays, while orthophotos and other base meshes belong near the bottom of scenery_packs.ini.
- Custom airports and airport enhancement packages
- Global Airports
- Regional and generated overlays, including X-World folders in their documented internal order
- Orthophotos and terrain base meshes
Do not alphabetise a multi-folder package when its instructions prescribe a different sequence. HD or UHD mesh and an Ortho4XP tile also cannot combine their terrain detail within the same one-degree tile: the base mesh with higher scenery priority is displayed, while the other is ignored for that tile.
How should you install X-Plane add-ons without conflicts?
The safest installation method is to confirm compatibility, establish a clean baseline and test each aircraft, plugin or scenery package before adding another.
- Check the target version. Confirm explicit X-Plane 11 or X-Plane 12 support, operating-system and processor compatibility, and every required library, framework or data package. For aircraft, also check support for VR, pop-out displays and your throttle hardware if you depend on them.
- Test the unmodified simulator. Load a default Laminar Research aircraft at a familiar default airport and confirm that controls and performance are stable.
- Extract to the correct folder. Aircraft go in a dedicated folder under
Aircraft, scenery inCustom Sceneryand global plugins inResources/plugins. Aircraft-specific plugins normally remain inside that aircraft’s folder. - Check for an extra folder level. The aircraft file and its supporting folders should sit directly inside the aircraft’s own directory. If it does not appear in Flight Configuration, inspect the extraction path before changing anything else.
- Install one package at a time. Restart X-Plane and inspect
Log.txtbefore adding the next package. - Register and order scenery. Let X-Plane detect new scenery, close the simulator, then inspect
Custom Scenery/scenery_packs.iniand correct misplaced airports, overlays or base meshes. - Test in two stages. Load a default aircraft and airport first, then test the new add-on. This separates a global plugin fault from an aircraft-specific or scenery-specific problem.
Most aircraft belong beneath X-Plane 12/Aircraft/ or the equivalent X-Plane 11 folder. Our aircraft folder and installation walkthrough covers nested archives and the checks to make when a new aircraft is missing.
Do not install FlyWithLua NG unless a particular compatible script needs it. An unused framework adds no feature, while old scripts may alter datarefs, graphics settings or controls in ways that are difficult to trace.
Can X-Plane 11 add-ons work in X-Plane 12?
Some simple scenery packages work in both simulators, but aircraft and plugins should be considered incompatible unless their documentation explicitly supports both X-Plane 11 and 12.
- Aircraft: Prefer an XP12-specific release in X-Plane 12. The simulators differ in flight modelling, lighting, materials, weather and other systems on which an aircraft may depend.
- Plugins: Confirm the simulator version, operating system and processor architecture. Apple Silicon users should check whether compiled plugins are native or require X-Plane to run through translation.
- X-Plane 11 graphics: Older plugins, weather tools and visual modifications may support only a particular Vulkan, Metal or OpenGL configuration.
- Scenery: Airports often transfer more readily than base meshes, but lighting, vegetation, water and seasonal effects may differ.
- Product editions: An X-Plane 12 edition does not automatically include X-Plane 11 files, or vice versa, even when the aircraft name is identical.
Do not replace a working package with an archive intended for the wrong simulator merely because its file date is later. Declared compatibility matters more than the timestamp.
Why is an X-Plane add-on not working?
Most add-on failures come from an extra folder level, missing scenery libraries, an obsolete plugin binary, duplicate copies or incorrect scenery priority.
- Read
Log.txtimmediately. Open the copy in the main X-Plane folder after the failed session and search for the add-on name, missing objects, plugin-loading errors and scenery warnings. - Inspect the extraction path. Archives often contain a wrapper folder, leaving the actual aircraft or plugin one level below the location X-Plane expects.
- Remove duplicate versions. Two copies of one plugin can load conflicting binaries, commands or settings.
- Verify every scenery dependency. An airport can appear in
scenery_packs.iniyet show no buildings because its referenced object libraries are absent. - Test by elimination. Move suspect global plugins out of
Resources/pluginsin batches, restart X-Plane and restore them one at a time.
If X-Plane crashes after adding an aircraft, remove that aircraft and any separately installed companion plugin, start with a default Laminar Research aircraft, then inspect Log.txt. Reinstalling the entire simulator should not be the first response to one faulty add-on.
Changing load order cannot fix every conflict. If two plugins assign the same command, control the same dataref or replace the same scenery tile, keep the one that serves your flying and disable the duplicate.
When an add-on works but frame rate falls sharply, complex aircraft systems and traffic plugins usually increase CPU load. Dense airports, high-resolution cockpit textures and orthophotos put more pressure on memory and the GPU. Remove or reduce the responsible category instead of changing every graphics setting at once.
Are weather and graphics add-ons worth installing?
Weather and graphics add-ons make sense only after the unmodified simulator runs smoothly and reliably.
A weather injector changes the conditions supplied to X-Plane, while a cloud or sky package changes their appearance; one product does not necessarily perform both jobs. For X-Plane 11, verify support for X-Plane 11.55 and the Vulkan, Metal or OpenGL mode you use.
Treat older shader replacements cautiously because some support only OpenGL or overwrite core simulator files that the X-Plane installer later restores. Scripts marketed as FPS boosters usually gain performance by reducing object density, visibility or other rendering work already controlled by X-Plane’s own settings.
What is the best add-on setup for each type of flying?
The best setup is the smallest collection that supports your regular aircraft and routes while preserving stable frame timing.
- Airline IFR: Zibo or one detailed paid airliner, AviTab, BetterPushback and custom scenery for airports you use regularly.
- General aviation and VFR: One accurate light aircraft, X-Camera when quick looks are insufficient, regional landmarks and either suitable mesh or orthophotos.
- Bush flying: A taildragger or utility aircraft, improved terrain and a small selection of remote airfields.
- VR or modest hardware: Limit global plugins, dense airports, complex aircraft and large orthophoto regions. Consistent frame timing matters more than another visual layer.
Are paid and study-level X-Plane add-ons worth it?
Paid add-ons offer the best value when they model an aircraft you intend to learn properly or an airport you fly regularly.
“Study level” is not a technical standard. Judge an aircraft by the systems simulated, documentation, supported failures, flight modelling and compatibility rather than the marketing label. Choose the Challenger 650 when detailed system interaction and cockpit preparation are the attraction, ToLiss for repeatable airline operations, or Aerobask and Thranda when hand-flying and shorter preparation matter more.
Before buying, check the required base product, included variants, operating-system support and exact X-Plane edition. Payware does not make an incompatible X-Plane 11 package suitable for X-Plane 12, while many essential utility plugins and scenery libraries remain free.