Set up vPilot for VATSIM in MSFS 2020 with correct audio, push-to-talk, model matching and traffic settings, plus practical connection fixes.
Install vPilot as a Windows desktop application—not in the MSFS 2020 Community folder—then enter your VATSIM credentials, choose and test your headset and microphone, bind a push-to-talk button, and add model-matching rules. Start MSFS, load at a parking stand, open vPilot, and connect using your filed callsign.
How to install vPilot for MSFS 2020
vPilot runs alongside the PC version of Microsoft Flight Simulator 2020 and communicates with it through SimConnect. It does not need your MSFS installation path, and a separate Community-folder SimConnect add-on is not normally required.
- Confirm that you are using MSFS 2020 on PC. vPilot is a Windows program and cannot be installed on an Xbox console.
- Download the official vPilot installer. Use the client download approved by VATSIM rather than a mirrored or repackaged copy.
- Run the Windows installer. Accept its normal application location; do not extract or copy vPilot into the MSFS
Communityfolder. - Allow vPilot through Windows security prompts. It needs network access for VATSIM and local access to MSFS through SimConnect.
- Start MSFS and load an aircraft. Once the cockpit has loaded, open vPilot and check that it reports a simulator connection.
The simplest arrangement is to run MSFS and vPilot on the same PC under the same Windows account. Multi-PC operation is possible, but it adds networking and host-client configuration that is unnecessary for a first setup.
What should I configure in vPilot?
Configure your account, audio hardware, push-to-talk control and model matching before making your first network connection. Exact tab names can vary slightly between vPilot builds, but the required settings remain the same.
| Setting | Recommended choice | Common mistake |
|---|---|---|
| VATSIM account | Your numeric VATSIM CID and account password | Entering an email address, forum name or IVAO account |
| Network server | Automatic or the default recommended option | Forcing a specific server without a support reason |
| Microphone | The exact Windows input device you intend to use | Leaving it on Default and having Windows switch devices |
| Headset/output | Your named headset or communications device | Selecting monitor speakers and then missing ATC calls |
| Push-to-talk | A dedicated keyboard, yoke, joystick or HOTAS button | Using a control already assigned to brakes, trim or another function |
| Model matching | Rules matching the traffic models installed in MSFS | Loading a VMR file whose referenced aircraft models are not installed |
How should I set up vPilot audio and push-to-talk?
Select specific input and output devices rather than generic Windows defaults, then use vPilot's microphone level or test facility if the installed build provides one. Speak normally: the signal should be clear without remaining extremely low or clipping at maximum level.
Bind push-to-talk inside vPilot. A control assigned only in MSFS will not necessarily transmit on VATSIM. Windows must also permit desktop applications to access the microphone.
Once in the aircraft, power the radios, tune the correct frequency and select the intended COM radio for transmission and reception. If vPilot shows the frequency but ATC remains silent, the aircraft's audio panel or active/standby frequency selection is often the real cause. FlyByWire users can follow our A32NX-specific radio, transponder and VATSIM configuration.
Do I need model matching to connect?
Custom model matching is not required merely to log in, but it is needed for believable and reliable display of other pilots. Without suitable models and rules, vPilot may substitute generic aircraft or report that it could not create an aircraft.
The traffic models must be installed where MSFS can load them, while the associated VMR rule file is selected inside vPilot. A VMR file alone contains rules, not the aircraft models themselves. Our MSFS 2020 model-matching and VMR setup explains the package installation, rule ordering and missing-model fixes.
Which MSFS traffic settings should I disable?
Disable MSFS multiplayer aircraft and Live or AI air traffic when flying on VATSIM, because vPilot injects the network traffic. Set ground-aircraft density to zero if static aircraft are occupying stands or appearing on top of VATSIM traffic.
You can leave Bing data, photogrammetry and other scenery services enabled. Turning off all online functionality is unnecessary; the aim is to remove competing aircraft sources, not online scenery.
How do I connect vPilot to VATSIM for the first time?
Connect only after MSFS has loaded your aircraft at a parking stand and vPilot confirms that it can see the simulator.
- Prepare the flight. Start at a suitable stand rather than on a runway, and file the intended flight plan when required.
- Check the callsign. Enter the same callsign used on the flight plan, normally without spaces or punctuation.
- Enter the ICAO aircraft type. Use the actual type code for the aircraft being flown, such as
C172orA20N, rather than its marketing name. - Leave observer mode off. Use it only when you intend to observe rather than operate an aircraft on the network.
- Connect and verify the radios. Check that your callsign appears in vPilot, tune the relevant controller or advisory frequency, and perform a brief radio check only when needed.
The next challenge is usually procedure rather than software. Our full MSFS 2020 VATSIM flight sequence covers filing, clearance, taxi, hand-offs, arrival and disconnection without repeating the client setup.
Why won't vPilot connect to MSFS or VATSIM?
Most connection failures come from starting vPilot before the cockpit has loaded, incorrect credentials, Windows audio permissions or inconsistent security settings.
- vPilot cannot see the simulator: load fully into an aircraft, restart vPilot and keep both programs under the same Windows user and privilege level. Running one as administrator and the other normally can cause avoidable problems.
- Authentication fails: enter the numeric VATSIM CID and VATSIM password, not an email address. vPilot connects to VATSIM only.
- The microphone meter does not move: check Windows microphone privacy permission, confirm the selected input device and reconnect a USB headset before reopening vPilot.
- ATC cannot hear you: verify the vPilot push-to-talk assignment, active COM frequency, radio power and transmit selection on the aircraft audio panel.
- You cannot hear ATC: confirm vPilot's output device and volume, then check that the correct COM radio is selected for reception.
- Aircraft are duplicated: disable MSFS multiplayer, Live Traffic and AI traffic. Static ground aircraft may also need to be set to zero.
- Model creation errors appear: remove invalid rules or install the models referenced by the VMR file, then restart MSFS so it can index them.
- The callsign is already in use: make sure another vPilot instance is not connected. After an abnormal disconnection, allow the previous session time to clear before reconnecting.
Can vPilot be used with MSFS 2020 on Xbox?
vPilot cannot run on Xbox, so the Xbox version of MSFS 2020 cannot connect directly to VATSIM through it. Use the Windows PC version of Microsoft Flight Simulator for a supported vPilot setup.