Install and set up vPilot for FSX or Steam Edition, including SimConnect, VATSIM login, audio, push-to-talk, model matching and common fixes.
Install vPilot on the same Windows PC as FSX or FSX: Steam Edition, then enter your VATSIM credentials, select audio devices and a push-to-talk key, add compatible AI models and model-matching rules, load FSX at a parking stand, and connect with the correct callsign and aircraft type.
vPilot requirements for FSX
vPilot requires a patched copy of FSX, a VATSIM account, working SimConnect components and a microphone or headset. Boxed FSX should have Service Pack 2 or Acceleration installed; FSX: Steam Edition already includes the relevant simulator updates.
- VATSIM account: Have your VATSIM ID and the sign-in credentials requested by vPilot ready.
- SimConnect: This lets vPilot exchange aircraft, radio and traffic data with FSX.
- Audio: A headset is preferable because speakers can feed controller audio back into your microphone.
- AI aircraft models: These are needed to display other pilots with appropriate aircraft and liveries.
vPilot connects FSX to VATSIM; it does not use the simulator's normal multiplayer lobby. Our comparison of FSX multiplayer and third-party online networks explains the distinction.
Install vPilot step by step
- Obtain the official installer. Use the genuine current vPilot installer rather than a repackaged copy from an add-on bundle.
- Close FSX and run the installer. Accept the normal installation location; vPilot does not need to be placed inside the FSX programme folder.
- Allow network access. If Windows Firewall displays a prompt, permit vPilot to communicate. It needs internet access for the VATSIM network and voice service.
- Launch vPilot once. Open its settings before connecting and complete the account, audio, push-to-talk and model-matching sections.
- Run both programmes normally. Avoid setting only one of them to “Run as administrator”. Different Windows privilege levels can prevent applications from communicating correctly.
There is normally no IP address or port to configure when vPilot and FSX run on the same computer. SimConnect should detect the simulator automatically after a flight has loaded.
Essential audio and model-matching setup
- Enter your network details. Supply your VATSIM ID and complete the password or sign-in process presented by your vPilot release.
- Select audio devices. Choose the actual microphone and headset outputs rather than leaving an unwanted webcam microphone or monitor speakers selected.
- Assign push-to-talk. Pick a joystick button or keyboard key that is not already assigned to an FSX control. Test the microphone level without speaking so loudly that it clips.
- Install FSX-compatible AI models. Follow the model package's installation method, then use vPilot's model scan or reload function.
- Load the matching rules. Add any supplied vPilot model-matching rule files and check that they reference models actually installed on the computer.
A mistake we see constantly is installing only a model-matching rules file. The rules tell vPilot which model to select, but they contain no aircraft themselves. vPilot also does not supply a complete set of airline models and liveries.
Set FSX's own airline and general aviation traffic sliders to zero if you want only live network traffic. This avoids mixing computer-generated aircraft with the aircraft injected by vPilot.
How do I connect FSX to vPilot?
Load FSX at a gate or parking stand first, then start vPilot and wait for its simulator connection indication before joining VATSIM.
- Choose the aircraft and departure airport in FSX, then place the aircraft away from runways and taxiways.
- Start vPilot and confirm that it reports a simulator connection.
- Enter the same callsign used on your flight plan.
- Enter the aircraft's ICAO type code, such as
C172orB738, rather than its full marketing name. - Connect, tune the appropriate frequency in the FSX radio panel and use the assigned push-to-talk control.
Do not connect while positioned on a runway or where another pilot is already parked. For flight plans, radio use, transponders and normal network procedure, follow our complete FSX-to-VATSIM connection procedure.
Why does vPilot say the simulator is not connected?
“Simulator not connected” usually means FSX has not finished loading, SimConnect is missing or damaged, or FSX and vPilot are running at different Windows privilege levels.
| Symptom | Likely cause | Fix |
|---|---|---|
| vPilot remains disconnected from the simulator | FSX is still at its opening screen or SimConnect is unavailable | Load into an aircraft first, restart vPilot, then repair the appropriate SimConnect runtime if necessary. |
| Connection works only when both programmes use administrator mode | Windows privilege mismatch | Remove unnecessary administrator settings and run both programmes at the same level. |
| Network login fails | Incorrect credentials, callsign or account status | Re-enter the requested VATSIM credentials and check the callsign before retrying. |
| No controller audio | Wrong output device, untuned radio or avionics power off | Select the headset in vPilot and verify the active COM frequency and aircraft avionics. |
If the simulator connection still fails, use our FSX SimConnect repair checklist rather than repeatedly reinstalling vPilot.
Why can't I see other VATSIM aircraft?
Missing or generic aircraft usually indicate absent AI models, incorrect matching rules, a failed model scan or SimConnect communication problems.
Check vPilot's messages for missing model names and confirm that the referenced aircraft appear in FSX's recognised SimObjects locations. If traffic remains invisible, our guide to diagnosing missing VATSIM traffic and model matching covers the focused checks without repeating the installation process.