Fix FlyByWire A380X not working in MSFS: check PC compatibility, installer paths, duplicate packages, black screens, conflicts and crashes.
The FlyByWire A380X usually stops working in Microsoft Flight Simulator because it was installed into the wrong Community folder, an old manual copy conflicts with the Installer version, the selected build does not match the simulator, or another add-on is interfering. On consoles, it cannot be installed at all.
What should I check first?
Confirm the platform and installation before changing graphics, controls or aircraft systems.
- Confirm that you are using a PC. The FlyByWire A380X is a PC Community add-on and cannot be installed on Xbox Series X|S, PlayStation 5 or PS5 Pro. Our A380X platform and simulator compatibility overview explains why its free availability does not make it a console aircraft.
- Select the correct simulator in the FlyByWire Installer. MSFS 2020 and MSFS 2024 can have separate package locations. Install the build offered for the simulator you actually launch; do not force a package intended for the other version into its Community folder.
- Remove duplicate A380X installations. Keep one Installer-managed copy only. An older manual installation, another release branch or a linked copy in a second add-on folder can cause missing aircraft, duplicate entries, failed loading or broken avionics.
- Restart MSFS after installation. Adding or updating the aircraft while the simulator is open will not reliably reload its package.
Why does the A380X not appear in the aircraft list?
An A380X that is completely absent from the aircraft selector is normally installed in an inactive folder or has the wrong folder structure.
Check the Community path shown by the Installer against the path used by MSFS. This matters when both simulator generations are installed, when the packages location was moved to another drive, or when separate Microsoft Store and Steam installations have existed on the same PC. Follow our active Community-folder checks if other external add-ons are also missing.
At the aircraft package root, manifest.json and layout.json should not be buried inside an extra wrapper folder. A source-code archive, Installer download or livery package is not itself a flyable aircraft. The correct add-on aircraft folder structure shows how to recognise nested or incomplete installations.
MSFS Safe Mode deliberately disables Community add-ons, so the A380X being absent there is expected. Its absence from Marketplace-owned content is not evidence of a failed installation either.
What does each A380X problem usually mean?
| Symptom | Likely cause | Next check |
|---|---|---|
| A380X is not listed | Wrong Community folder, nested files or incompatible simulator target | Verify the active path and reinstall through the Installer |
| Two A380X entries appear | Duplicate manual and Installer-managed packages | Remove every old copy, then install one branch |
| Pink, white or missing textures | Incomplete package or incompatible livery | Reinstall the aircraft and test without liveries |
| Loading stalls or MSFS closes | Add-on conflict, damaged package or resource pressure | Test the A380X alone at a default airport |
| Cockpit screens remain black | Cold-and-dark state or avionics package failed to initialise | Check aircraft power, then test a clean installation |
| Only hardware controls fail | Incorrect or duplicated control bindings | Test cockpit controls with the mouse and inspect the active profile |
Why are the A380X cockpit screens black?
Black screens at a parking stand can be normal until electrical power is established, but an already powered runway start should not remain completely dark.
For a cold-and-dark start, switch on the aircraft batteries and connect available external power or start the APU using the aircraft's normal procedure. Give the systems time to initialise after loading. If every display and the EFB remain dead despite confirmed power, return to the main menu and test a freshly installed A380X without liveries or other aircraft modifications.
A switch that does nothing does not always indicate a broken installation. The A380X is developed in stages, and some controls or systems in a particular build may be intentionally inoperative. If the aircraft loads, displays work and it can be flown, one inactive control is more likely an implementation limitation than package corruption.
How do I isolate an add-on conflict or crash?
The quickest conflict test is to run the A380X with no unrelated Community packages loaded.
- Close MSFS and the Installer. Move other Community add-ons to a temporary folder outside the active packages directory, leaving only the Installer-managed A380X and any dependency it installed.
- Remove A380X liveries and modifications. Older liveries are common causes of missing textures and loading failures after the base aircraft changes.
- Repair the aircraft through the Installer. If repair is unavailable or fails, uninstall the A380X, remove its leftover package folder and install one clean copy.
- Use a simple test flight. Load at a default airport without third-party scenery. If that works but a highly detailed airport crashes, the scenery combination or available memory is the stronger suspect.
- Restore add-ons in small groups. When the failure returns, the last group contains the conflict; test those packages individually.
Clearing the rolling cache does not fix an aircraft installed in the wrong folder, and reinstalling all of Microsoft Flight Simulator is rarely justified when default aircraft still work. Check paths, duplicate packages and conflicts first.
What if the aircraft loads but my controls do not work?
If the virtual cockpit responds to the mouse but the yoke, sidestick, pedals or throttle do not, the A380X installation is probably sound.
Select the intended device profile and remove duplicate axis assignments, especially where one physical axis is bound to several throttle or flight-control commands. Assistance settings and bindings left over from another aircraft can also interfere. Our MSFS controller and binding diagnosis covers the device checks without requiring another A380X reinstall.