Set up the FlyByWire A32NX for VATSIM in MSFS 2020 or 2024, including the pilot client, model matching, flight plan, radios and transponder.
To set up the FlyByWire A32NX for VATSIM, use Microsoft Flight Simulator 2020 or 2024 on Windows PC, install a compatible A32NX build and pilot client, disable non-VATSIM traffic, configure audio and model matching, file and load the same route, then connect from a vacant parking stand with COM1 and the transponder correctly set.
Does the FlyByWire A32NX work with VATSIM in MSFS 2020 and MSFS 2024?
VATSIM works with both Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024 on PC, provided the FlyByWire A32NX build and pilot client support the simulator being used. The A32NX is FlyByWire's modified Airbus A320neo; it is the aircraft, not the software that connects you to the network.
For MSFS 2020, use our clean A32NX installation and duplicate-removal procedure if the aircraft is absent or its systems fail to load. For MSFS 2024, use only an A32NX package explicitly identified as compatible with that simulator. Do not assume every MSFS 2020 Community package will work unchanged.
We recommend the Stable branch for a first online flight. Use a Development build when its release information addresses a compatibility problem or feature you need, and never leave Stable, Development and an old manually installed copy together in the Community folder.
Can you install VATSIM on MSFS 2024?
Yes, but only on PC: install a supported external pilot client, such as vPilot, in Windows and connect it to MSFS 2024 while a flight is loaded. There is no VATSIM option to install from inside the simulator.
This setup is not available on Xbox Series X|S, PlayStation 5 or PS5 Pro because those platforms cannot run the required Windows pilot client. Our full pilot-client, audio and traffic connection checklist covers the wider account and client configuration.
FlyByWire A32NX VATSIM setup step by step
The reliable order is to prepare the simulator and pilot client first, load the aircraft at a parking position, then connect after checking the radios, identity and transponder.
- Install one compatible A32NX build. Confirm that you are selecting the FlyByWire A32NX rather than the stock A320neo. Remove obsolete or duplicate installations before troubleshooting blank displays, missing cockpit systems or loading failures.
- Install and configure the pilot client. Enter your VATSIM credentials, allow the program through the Windows firewall when prompted and verify that it detects the running simulator. Select the microphone and headphones inside the client rather than relying solely on the Windows default devices.
- Bind push-to-talk. Use a momentary button that is easy to hold while flying but is not assigned to an MSFS ATC command, view control or flight control. Test the microphone level in the client before connecting.
- Configure model matching. Install an aircraft model library compatible with your version of MSFS and enable its matching rules in the pilot client. Model matching is optional for connecting, but without it other pilots may appear as generic aircraft.
- Disable competing traffic. Turn off MSFS multiplayer aircraft, AI traffic and real-time online traffic. Set static or ground aircraft density to zero or low so simulator-generated models do not duplicate VATSIM traffic or occupy gates.
- Load at a vacant stand. Start at a gate, ramp or parking position with the parking brake set. Never connect on a runway or taxiway; if another online pilot already occupies your stand, relocate while disconnected.
- Enter the correct identity. The connection callsign must match the filed callsign. Airline flights normally use the three-letter ICAO operator designator, such as
BAW123, rather than a two-letter ticketing code. The ICAO aircraft type for the A320neo isA20N. - File and load the flight plan. File the intended departure, destination, route and requested cruise level, then enter the same plan in the A32NX FMGC. Do not claim equipment or navigation capabilities that you cannot operate.
- Prepare COM1 and the transponder. Tune the required frequency on VHF1, select VHF1 for transmission and reception, enter the assigned squawk and set the A32NX transponder to AUTO. Confirm that the client shows COM1 and altitude reporting in the expected state.
- Connect while stationary. Listen before transmitting and remain parked until cleared to push or taxi. If you discover an overlapping aircraft after connecting, disconnect before changing position rather than slewing across the airport online.
Which MSFS traffic and assistance settings should you use?
VATSIM traffic should be the only moving aircraft source, while automated radio features must not retune the A32NX or transmit on your behalf.
| MSFS option | Recommended setting | Why |
|---|---|---|
| Multiplayer aircraft | Off | Prevents pilots from appearing once through MSFS multiplayer and again through the VATSIM client. |
| AI and real-time online traffic | Off | The pilot client injects network aircraft instead. |
| Static or ground aircraft | Zero or low | Reduces blocked stands and aircraft parked inside online traffic. |
| AI radio communications and assisted ATC | Off | Stops the simulator changing frequencies or making automated calls. |
| Weather | Live Weather is usually practical | VATSIM does not inject weather. Check the controller's ATIS because simulator winds, pressure and runway selection can still differ. |
Switch off the individual traffic sources rather than disabling every online function in MSFS, especially if you want to retain Live Weather.
How do I set up VATSIM model matching in MSFS 2024?
MSFS 2024 model matching requires both compatible aircraft models and a pilot-client rule set that points to those installed models. A rule file alone cannot supply the aircraft it references.
- Choose models built or confirmed for MSFS 2024. A library that works in MSFS 2020 may contain model definitions that MSFS 2024 cannot inject correctly. A flyable aircraft in the selection menu is also not automatically suitable as an efficient traffic model.
- Install the models in the correct simulator. Use the library's supported installer or its documented
Community-folder method. Check that an old MSFS 2020 copy has not been linked into MSFS 2024 alongside a newer package. - Add the matching rules. Import or enable the supplied VMR rule set in the pilot client. Remove duplicate or conflicting rule sets; broad fallback rules can otherwise replace a more accurate airline and aircraft match.
- Refresh the client after changes. Restart or rerun its model scan so it can see newly installed aircraft titles. Test at a moderately busy airport before joining a large event.
If the client reports that no model was found, the rule set probably lacks an exact match and should fall back to a generic aircraft. A message about failing to create an aircraft points instead to a missing, incompatible or damaged model referenced by the rules.
Model matching is local. It controls what you see; other pilots use their own model libraries and rules to display your A20N. Installing an A32NX livery therefore does not guarantee that everyone else will see that exact livery, and a poor match does not change how ATC identifies your callsign.
What route and cruise level should you file?
File the route and requested cruise level you intend to fly, but treat both as requests until ATC issues the clearance.
| Item | How it should be used |
|---|---|
| Callsign | Must match the callsign entered in the pilot client. |
| Aircraft type | Use A20N for the FlyByWire A320neo. |
| Route | File the intended route and load it into the FMGC; amend it when ATC changes the clearance. |
| Cruise level | Enter the requested level in the flight plan and MCDU, but set the FCU to the altitude actually cleared by ATC. |
| SID, STAR and runway | The controller's clearance takes precedence over a planning tool or imported plan. |
A mistake we see often is treating the filed VATSIM plan, the planning-service plan and the route inside the MCDU as one synchronised record. They are separate. Importing a plan does not automatically file it with VATSIM, and filing it does not programme the aircraft.
If you use SimBrief, you can import the plan and prepare fuel and payload through the A32NX flyPad. For manual entry and clearance amendments, follow our explanation of entering and checking an Airbus route in the MCDU.
Do CruiseLevel or RouteTune set up VATSIM for you?
No. CruiseLevel and RouteTune can be treated as optional route-planning sources, but neither replaces the Windows pilot client, files every required field automatically or programmes the A32NX FMGC by itself. Check any suggested route against the navigation data available in the aircraft and be ready for ATC to amend it.
Directional level rules, airway restrictions and available procedures vary by airspace. Do not choose a cruise level solely because it is odd or even; use the route's applicable planning rules and an altitude the loaded aircraft can reach safely.
If the MCDU displays NOT IN DATABASE or shows different procedures, the planner and aircraft may be using different navigation-data cycles. Select a procedure available in the aircraft, correct the route and tell ATC promptly if you cannot accept the cleared procedure.
How should the A32NX radios and transponder be set?
The active VHF1 frequency, A32NX audio-panel selection and pilot-client COM1 state must agree before voice communication will work correctly.
Place the controller's frequency in the active VHF1 position and select VHF1 for both transmission and reception on the audio control panel. The pilot client's COM1 display should follow the cockpit radio. If it does not, confirm that the client is connected to the simulator and that an assistance feature is not retuning the radio.
Enter the assigned four-digit squawk on the A32NX ATC panel and use AUTO during normal operations. Check the pilot client for Mode C or altitude-reporting status because that status is what the network receives. Use IDENT only when ATC asks for it.
TCAS traffic mode and transponder altitude reporting are related but separate. Selecting TA/RA does not correct a pilot client that remains in standby, and changing the client to Mode C does not by itself configure the cockpit TCAS display.
Why can ATC see the A32NX but not hear me?
Position reporting and network voice are separate, so ATC can see your callsign even when the selected audio device, COM radio or push-to-talk binding is wrong.
| Symptom | Likely cause and fix |
|---|---|
| You hear nobody | Confirm the controller frequency is active on COM1, enable VHF1 reception on the audio panel, raise its volume and verify the playback device selected in the pilot client. |
| ATC cannot hear you | Select the correct microphone in the client, check its input level and confirm that push-to-talk is bound there rather than only in MSFS. |
| The radio changes by itself | Disable AI radio communications and assisted ATC, then retune VHF1. |
| ATC cannot see your altitude | Check the assigned squawk, set the A32NX transponder to AUTO and verify that the client indicates Mode C or altitude reporting. |
| Aircraft appear twice | MSFS multiplayer, AI traffic or real-time online traffic is still active. Disable it and let the pilot client inject traffic. |
| Other aircraft have generic or incorrect liveries | The installed model library lacks an exact match, the associated rule is missing, or another VMR rule is taking priority. This is visual and does not prevent ATC communication. |