Skip to content

Support Guide

Microsoft Flight Simulator 2020 is still a rather young flight simulator and many issues still need to be addressed.

The FlyByWire A32NX tries to address many of these issues but it is of course also likely to have issues and bugs itself now and then.

This guide shall help you how to identify and solve these issues by guiding you through a systematic troubleshooting process. There are several sources of information you can check if you experience an issue with the FBW A32NX add-on. We will describe each of them in more detail below.

Index

  1. Learn how to fly the A32NX
  2. How to Troubleshoot
  3. Research Known Issues
  4. Report Issue on Discord
  5. Report Issue on the A32NX Github
  6. Collecting Support Information

1. Learn How to Fly the A32NX

IMPORTANT

The FBW A32NX aims to become a realistic simulation of a real Airbus A320neo. Accordingly as with real pilots some reading and learning is required to gain the knowledge to competently fly this aircraft even in a simulator. Our support channels are not meant to and cannot replace this learning process for you.

A good place to start learning to fly and operate the FlyByWire A32NX is our Beginner Guide.

Further help can be found on our - Discord Link in the channel #flight-school .

Please make sure you have acquired the knowledge to distinguish a software issue within the A32NX from lack of knowledge on your part. You will help keep our support channel effective for other users reporting actual issues.

2. How to Troubleshoot

Before reporting an issue on the FlyByWire Discord or on GitHub please follow this troubleshoot steps first.

Please follow the steps below. If you can't reproduce the issue until the last item in the list then it is most likely NOT a FlyByWire A32NX issue.

  1. Read 3. Research Known Issues
  2. Make sure the issue is reproducible!
    Issues which happen only once can have many causes. These can usually not be investigated or fixed as they can't be reproduced by the FlyByWire team. To do so restart the sim and try to create the same situation again (e.g. same airports, route, livery, time of day, weather, etc.).
  3. If the issue is reproducible do a test in a different situation (different airports, route, weather, etc.).
  4. If the issue is still reproducible please do a test with another aircraft (preferably a default Microsoft Flight Simulator aircraft). If the issue is reproducible with other aircraft it is most likely not a FlyByWire A32NX issue. If it is not reproducible with other aircraft follow the next steps.
  5. To make sure the issue you are experiencing is not caused by a conflict with other add-ons or liveries *remove everything (really everything!) from your Community Folder and perform a clean reinstall of the A32NX with the FlyByWire Installer.
  6. Also ensure no other 3rd party software such as FSUIPC, SPAD.neXt, YourControls, FS2Crew, etc. is running while you are troubleshooting.
  7. If the issue is not already known and is reproducible please take screenshots or a video clearly showing your issue and continue with chapter 4. Report Issue on Discord.

Please really do this as >90% of all reported issues are caused by conflicts with other mods and liveries, etc. Unfortunately Microsoft Flight Simulator 2020 is very sensitive to conflicts between mods and liveries.

3. Research Known Issues

Read the Reported Issues section - most issues users encounter are already on this list.

If you have a github account please also see Issues there. Please also use the search for your particular issue.

Join our Discord server - Discord Link in channel #support and do the following:

  • Read the Pinned Messages for commonly reported issues

    Pinned-Messages

  • Read the Sticky Messages which is automatically posted after each message.

    Sticky-Message

  • Search in the #support channel for similar issues other users have reported.

    Search-support

Please do this research before you post any questions or report any issues.

4. Report Issue on Discord

If you can't solve or find your issue with the above steps, you can use our - Discord #support channel to get further help.

Please prepare the following before reporting any issues:

With this information at hand go to our Discord - Discord #support channel and describe your issue and respond to the questions our support team might have.

Please do some research (see above ) before you post any questions or report any issues.

5. Report Issue on the A32NX GitHub

- Issues / Feature Requests

Follow the issue template as best as you can. The more information you provide the easier it is for our team to understand and reproduce your issue.

Provide at least the following so that our team can reproduce the issue:

  • MSFS Version
  • A32NX Version
  • Clearly describe the issue in a way a third person can fully understand and reproduce it!
  • Include references like screenshots or videos

Be aware that issues that do not follow the template or provide insufficient information might get ignored or closed without any response.

Collecting Support Information

MSFS Version

The version of Microsoft Flight Simulator 2020 you are using can be found via several ways:

  • In the MSFS main menu you can click on your username in the upper right corner. This will display your version.

    MSFS Version

  • Using Alt+Tab to see all open windows.

    MSFS Version via Alt+Tab

  • Using the MS Store Update dialog.

    MSFS-Version-MSStore

A32NX Version

Stable or Development

You can determine which version of the FBW A32NX you use by looking at:

  • the FlyByWire Installer

    Installer

  • the Microsoft Flight Simulator Content Manager

    Content-Manager

Build Info

To get the actual build number of your installed A32NX go into your Community folder and open this A32NX file with Notepad:

\flybywire-aircraft-a320-neo\build_info.json

This should contain something like this: 

{
  "built": "2021-08-11T07:29:20+00:00",
  "ref": "master",
  "sha": "1c5335ec13ec6b7d29319db3371299da5e4fb880",
  "actor": "developername",
  "event_name": "manual"
}

Community Folder Content

Make sure that before reporting any issues that your Community Folder is completely empty with the exception of the FlyByWire add-on (folder name flybywire-aircraft-a320-neo).

Make a screenshot of the Community Folder if requested by our support team.

Screenshot of Cockpit

Quite often when issues during flight are reported a screenshot of the Cockpit will be request by our support team. A good screenshot should contain all screens and the FCU in a sufficient resolution to help the support team to recognize details on the PFD, ND or ECAMs.

Example

Cockpit screenshot for Support

How to Take a Good Screenshot

Position yourself in the cockpit using arrow keys (default key mapping) to look straight at the front instrument panel as in the example above and then use the Windows Snipping Tool (Instructions Here) to take a screenshot of all screens and the FCU.

Last update: October 28, 2021
Back to top