Best A320 for X-Plane 11 and 12: compare ToLiss, FlightFactor and JARDesign compatibility, licences, installation and common fixes.
For X-Plane 12, the best A320 add-on is the ToLiss A320neo, with dependable Airbus systems, autoflight and performance. For X-Plane 11, choose the separately sold FlightFactor A320 Ultimate XP11 package for a detailed A320ceo. ToLiss A320neo does not support X-Plane 11; use JARDesign’s XP11 edition if FlightFactor’s is unavailable.
Best A320 for X-Plane 11 and best A320 for X-Plane 12
ToLiss is our first choice on X-Plane 12, while FlightFactor’s dedicated XP11 package is the strongest high-fidelity A320 available for X-Plane 11.
- X-Plane 12: Buy ToLiss A320neo unless recreating an A320ceo is a firm requirement. It combines convincing FMGS and autoflight behaviour with useful situation saving, failures and relatively low setup friction.
- X-Plane 11: Buy only the FlightFactor A320 Ultimate product explicitly labelled for XP11. It remains the better procedural choice than JARDesign for pilots who want an A320ceo.
- X-Plane 11 fallback: JARDesign’s separate XP11 A320neo is the practical alternative if the FlightFactor XP11 product is not available to purchase. Its systems and managed guidance are less consistent than the leading aircraft.
- A320ceo on X-Plane 12: Choose FlightFactor A320 Ultimate XP12 Extended. Do not install the older XP11 package in X-Plane 12.
A common buying mistake is selecting the right aircraft name but the wrong simulator-generation package. The words XP11, XP12 and Extended are product distinctions, not interchangeable download labels.
A320 compatibility, operating systems and licence matrix
The simulator generation named for each package determines where its custom systems and plug-ins are supported.
| Package | Supported simulator and required build | Operating systems | Licence and update entitlement | Separate package needed? |
|---|---|---|---|---|
| ToLiss A320neo | X-Plane 12 only. Use a fully updated 64-bit production build of X-Plane 12. | 64-bit Windows, macOS and supported Linux distributions | The A320neo licence covers its XP12 package and maintenance updates supplied for that product. It provides no XP11 aircraft. | XP11 is unavailable. |
| FlightFactor A320 Ultimate XP11 | X-Plane 11 only. Use X-Plane 11.50 or later, preferably the final 11.55 build. | 64-bit Windows, macOS and supported Linux distributions; X-Plane 11 itself is not native Apple Silicon software | The XP11 licence covers the legacy XP11 package. It does not automatically grant the XP12 Extended aircraft. | Yes. This is distinct from XP12 Extended. |
| FlightFactor A320 Ultimate XP12 Extended | X-Plane 12 only. Use a fully updated 64-bit production build. | 64-bit Windows, macOS and supported Linux distributions | Sold as a new XP12 product or paid extension path for eligible XP11 owners. Entitlement must appear in the purchaser’s account. | Yes. Install the XP12 Extended download, not the XP11 folder. |
| JARDesign A320neo XP11 edition | X-Plane 11 only. Use the final 64-bit X-Plane 11.55 build. | 64-bit Windows, macOS and supported Linux distributions | Licensed and updated as the XP11 product. An XP12 licence is not implied. | Yes. It is separate from the XP12 edition. |
| JARDesign A320neo XP12 edition | X-Plane 12 only. Use a fully updated 64-bit production build. | 64-bit Windows, macOS and supported Linux distributions | Requires the XP12 product or an eligible paid upgrade entitlement shown in the purchaser’s account. | Yes. Do not copy the XP11 package across. |
Operating-system support does not mean every obsolete OS release or Linux distribution is covered. Apple Silicon users must follow the native or Rosetta launch instructions supplied with the relevant aircraft because an aircraft plug-in can have different architecture requirements from X-Plane itself. Our compatibility and dependency checklist for X-Plane add-ons explains what to verify before downloading.
Will an X-Plane 12 A320 work in X-Plane 11?
No. ToLiss A320neo and the XP12 editions of FlightFactor and JARDesign rely on X-Plane 12 flight-model, graphics and plug-in interfaces. An aircraft appearing in X-Plane 11’s selector does not prove that its displays, FMGS or custom systems can run there.
The reverse is also unsafe. Copying an XP11 aircraft into X-Plane 12 can produce apparently normal exterior graphics while its avionics plug-in fails or its flight model behaves incorrectly. Install the package issued for the target simulator and covered by the licence.
FlightFactor A320 vs ToLiss A320: which is better?
ToLiss A320neo is better for most X-Plane 12 pilots; FlightFactor is the better choice when an A320ceo is essential. On X-Plane 11 there is no direct contest because ToLiss A320neo is not compatible, leaving FlightFactor’s XP11 package as the higher-fidelity choice.
| Criterion | ToLiss A320neo | FlightFactor A320 Ultimate |
|---|---|---|
| Aircraft represented | A320neo with new-generation engine behaviour and performance | A320ceo, suited to older fleets and ceo-specific procedures |
| Systems fidelity | Strong normal and abnormal systems logic, flight-envelope protections, failures and aircraft-state handling | Detailed ceo cockpit operation, MCDU work and procedure-led systems management |
| Autoflight | Generally more predictable through managed climb and descent, constraints, route changes and approach transitions | Capable when correctly configured, but less forgiving of installation, route and hardware problems |
| Performance | Usually the lighter and more consistent package, although scenery, weather, traffic and resolution still dominate many systems | Its custom avionics and plug-in stack can demand more CPU time and memory |
| Hardware integration | The ISCS provides aircraft-specific configuration and throttle mapping; custom commands are available for many cockpit functions | The EFB and custom commands support detailed setup, but generic X-Plane bindings do not operate every function correctly |
| Maintenance | Usually easier to keep clean and updated, with situation saving useful for repeat training | More sensitive to incomplete updates, activation, plug-in permissions, modified files and conflicting scripts |
| Best suited to | Pilots prioritising dependable line operations, abnormal practice and an A320neo | Experienced users who specifically want a ceo and are comfortable maintaining a more involved installation |
Neither is a certified training device. The meaningful comparison is not cockpit texture sharpness; it is what happens after a route revision, during an altitude-constrained descent, when changing approach, or when the thrust levers cross an Airbus detent.
Does the A320neo versus A320ceo difference matter?
Yes, especially when using airline operating material, performance figures or a historical fleet plan.
- A320neo: ToLiss and JARDesign represent the new-engine generation, with its associated engine indications, start behaviour and performance profile.
- A320ceo: FlightFactor represents the earlier current-engine-option generation.
- Performance planning: Fuel burn, take-off data, weights and engine parameters must match the model being flown.
- Liveries: A ceo operator’s paint scheme applied to a neo does not change its engines or performance.
- Tutorials: Airbus FCU and MCDU principles transfer, but engine procedures, ECAM indications and aircraft-specific options may not.
Choose the variant before considering liveries. If the airline, era or procedure requires a ceo, FlightFactor is the relevant comparison even when ToLiss is the stronger all-round simulation.
Installing and configuring an A320 add-on
Most failed A320 installations result from using the wrong package, nesting the aircraft folder incorrectly, blocking a plug-in or confusing X-Plane axis calibration with aircraft-specific detent calibration.
- Download the entitled package: Match the product name to the matrix above. Do not rename an XP11 package or merge it with an XP12 download.
- Extract the complete aircraft: Place the resulting aircraft folder below
X-Plane 11/Aircraft/orX-Plane 12/Aircraft/. Do not run it from an archive or bury it under repeated folders such asAircraft/A320/A320/A320/. Our aircraft-folder and plug-in installation instructions cover the correct structure. - Keep local plug-ins with the aircraft: Do not move bundled plug-ins into
Resources/plugins/unless the supplied manual expressly requires that location. - Activate the unmodified base aircraft: Enter the key only in the aircraft’s authorised activation screen, then reload or restart X-Plane when instructed. Test before adding sound packs, cockpit modifications, scripts or third-party liveries.
- Calibrate at simulator level: In X-Plane’s joystick settings, calibrate each axis through its full physical range. Check axis reversal and remove duplicate throttle, tiller, brake, speedbrake and reverse assignments.
- Calibrate at aircraft level: Use ToLiss ISCS, the FlightFactor EFB or JARDesign’s documented setup procedure to define
IDLE,CL,FLX/MCTandTOGA. This second calibration maps the raw X-Plane axis to Airbus detents; it does not replace simulator calibration. - Create a dedicated control profile: Assign it only to that A320. Generic autopilot or throttle commands can conflict with the aircraft’s custom commands.
- Test with consistent navigation data: Build a short route using the same AIRAC cycle as the aircraft. Company-route formats and storage locations are not interchangeable between ToLiss, FlightFactor and JARDesign.
Manuals and official support instructions
Use the documentation supplied with the exact aircraft build: the ToLiss manuals explain ISCS and aircraft functions, FlightFactor’s package documentation and EFB cover its hardware and activation workflow, and JARDesign supplies generation-specific instructions. For activation resets or account problems, use the official support address linked from the manual or purchase account rather than an old third-party guide.
A320 troubleshooting: managed guidance, routes, plug-ins and detents
The Flight Mode Annunciator is the first place to diagnose autoflight behaviour; it shows what the aircraft is actually commanding rather than what the pilot expected it to command.
| Symptom | Likely cause | Actionable checks |
|---|---|---|
| Managed climb or descent will not engage | Incomplete FMGS data, wrong flight phase, a discontinuity or selected mode commanded instead | Check the route has sequenced, required INIT and PERF entries are complete, the cleared altitude is set and the FCU knob was pushed for managed mode. Read the FMA: OP CLB or OP DES is selected guidance, not managed profile guidance. |
| The aircraft ignores an altitude or speed constraint | The constraint is behind the aircraft, not valid for the active phase, or the aeroplane lacks energy to meet it | Inspect the active F-PLN leg and predicted profile, confirm managed mode on the FMA and check for speedbrake or drag prompts. Re-entering the value does not make an impossible descent achievable. |
| The aircraft turns away from the route | Heading mode is selected, the active leg is wrong, or a discontinuity/manual-vector leg has been reached | Check the white active waypoint, ND track and FMA. Use heading for an intentional vector, then a valid DIR TO or cleared intercept before returning to managed navigation. |
| A route file will not load | Wrong company-route format, file location or AIRAC cycle | Enter the route manually to confirm the waypoints exist, then consult that aircraft’s manual for its own route format and folder. Do not reuse a ToLiss route file merely by changing its extension for FlightFactor or JARDesign. |
| A SID, STAR or approach is absent | Navdata cycles, airport data or runway names do not agree | Compare the cycle displayed in the MCDU with the planning source. Check renamed runways and confirm the procedure is published for that runway in the installed cycle. |
| Displays remain blank after electrical power is established | Aircraft plug-in failed to load, activation is incomplete or files are missing | Confirm brightness and power first, then test a clean aircraft folder. Inspect Log.txt for the aircraft and plug-in names, load failures, missing libraries or permission errors. |
| Activation repeats or the key is rejected | Files are not writable, the installation was modified, security software quarantined a component or the activation allowance needs resetting | Use a clean download in a user-writable X-Plane folder, check the system clock and quarantine history, then restart as directed. Use official support for an activation reset; do not keep reinstalling into the same damaged folder. |
Thrust will not remain in CL or autothrust oscillates | Detents are miscalibrated, the axis is reversed, duplicate bindings exist or the potentiometer is noisy | Recalibrate the full axis in X-Plane, remove every duplicate throttle assignment, then repeat the aircraft-specific detent setup. Move the hardware slowly and watch whether the virtual lever and ECAM detent indication jump. |
| Autopilot disconnects without an obvious reason | Control-axis noise, conflicting assignments, excessive manual input or an invalid engagement condition | Centre the controls, widen only the minimum required null zone and unplug duplicate controllers for a test. Watch the FMA and ECAM for the condition that triggered disconnection. |
| The aircraft stutters or frame rate collapses | Combined aircraft, scenery, weather, traffic and plug-in load exceeds CPU, GPU or graphics-memory capacity | Test the same aircraft at a default airport with clear weather and no AI traffic. Disable non-essential global plug-ins one at a time; changing several variables together hides the actual cause. |
Log.txt is in the root X-Plane 11 or X-Plane 12 folder beside the simulator executable. Reproduce the fault, quit X-Plane normally and inspect the newly written file. Search from the bottom for the aircraft name and terms such as failed, not loaded, dlerror, activation and missing; the lines immediately above an error often identify the component or library involved.
Do not treat every warning in the log as the cause. Compare a failed load with a clean test, and remove global scripts or plug-ins one at a time rather than deleting the entire simulator installation.
Is there a good freeware A320 for X-Plane 11 or 12?
No freeware A320 in our library matches ToLiss or FlightFactor for complete FMGS, autoflight, ECAM and system simulation. Free models can still be useful for casual flying, repaints or AI traffic, but some downloads contain no functional virtual cockpit at all.
Before installing an aircraft from our X-Plane freeware library, check whether it is flyable, which simulator generation it targets and whether custom plug-ins are included. A visual A320 model or AI aircraft should not be mistaken for a study-level add-on.