Connect FlightGear to VATSIM using the approved swift client. Set up the simulator link, voice and model matching, then fix common connection errors.
FlightGear does not connect to VATSIM through its built-in multiplayer system. Use swift, a VATSIM-approved pilot client with FlightGear support, then start FlightGear with swift’s local interface settings, configure your VATSIM login, audio, callsign and aircraft type, and connect only after loading at a parking stand.
FlightGear multiplayer and VATSIM are separate networks. A mistake we see frequently is entering VATSIM details in FlightGear’s multiplayer panel; that panel is only for the simulator’s own network. Our guide to FlightGear’s native online multiplayer explains that alternative system.
What do I need to use FlightGear on VATSIM?
- An activated VATSIM account with any required new-member steps completed.
- A VATSIM-approved release of swift with FlightGear support.
- A working microphone, headphones and a push-to-talk button.
- FlightGear and swift allowed through the operating system’s firewall.
Do not follow old bridge-client instructions simply because they mention FlightGear. VATSIM permits approved pilot clients only, and obsolete clients may no longer authenticate or support the network’s voice system.
How to set up swift with FlightGear
- Install swift and its FlightGear integration. If the installer offers simulator-specific components, include FlightGear support. Run swift’s initial configuration and select FlightGear as the simulator.
- Configure the local simulator interface. swift communicates with FlightGear through local socket connections. Copy the FlightGear startup options generated or documented by your swift installation into the launcher’s additional command-line options field. These options commonly begin with
--generic=socket. - Install the supplied protocol definition if required. Some packages handle this automatically; others provide a setup utility that places the swift protocol data where FlightGear can read it. Use the files supplied with the same swift build rather than copying files from an old tutorial.
- Keep the connection settings matched. The host, incoming port and outgoing port in FlightGear must agree with swift. Copy them exactly instead of substituting port numbers found in another guide.
- Load FlightGear at a parking position. Leave FlightGear’s ordinary multiplayer connection disabled. Starting on an active runway creates an immediate conflict for other VATSIM users.
- Confirm the simulator connection in swift. Do not connect to VATSIM until swift reports that it can see FlightGear. If it remains disconnected, the problem is in the local FlightGear-to-swift link rather than your VATSIM account.
- Enter the network details. Configure your VATSIM authentication, callsign and ICAO aircraft type. Use a type designator such as
C172, not a descriptive aircraft name. - Set up audio and push-to-talk. Select the correct microphone and headphones in swift’s audio settings, then assign a push-to-talk key or controller button. This is a swift command, not FlightGear’s ordinary radio key. Before assigning it, check FlightGear’s existing keyboard assignments to avoid a conflict.
- Connect to VATSIM. Once swift shows FlightGear connected and the aircraft is safely parked, connect the pilot client to the network. Filing a flight plan is separate and is not required merely to establish the simulator link.
How do I know both connections are working?
swift must show both a simulator connection and a VATSIM network connection. These are independent: swift can read your FlightGear aircraft while being offline from VATSIM, or log-in can fail even though the local simulator link works.
- Moving the aircraft or changing a supported radio should update swift.
- The client should display the connected callsign and network status.
- Transmit and receive indicators should react to the configured push-to-talk control and tuned frequency.
- Nearby traffic should appear once model matching is configured and other pilots are within range.
For airport positions and local navigation checks, see how to use FlightGear’s built-in map. The map itself is not proof that VATSIM authentication or voice is working.
Why won’t FlightGear connect to VATSIM?
| Symptom | Likely cause | Fix |
|---|---|---|
| swift says the simulator is disconnected | Missing startup options, missing protocol data, wrong simulator selected or mismatched local ports | Re-run the FlightGear integration setup and compare every local connection setting with the options passed to FlightGear. |
| FlightGear connects to swift, but VATSIM login fails | Account, authentication or approved-client issue | Check the VATSIM account status and credentials, and use an approved swift release rather than an obsolete bridge client. |
| No voice reception or transmission | Wrong audio device, no push-to-talk assignment, incorrect COM frequency or transmit radio not selected | Test the devices in swift, verify its TX/RX indicators and compare the displayed radio frequency with the cockpit. |
| No other aircraft appear | No usable FlightGear model set or incomplete model matching | Run swift’s model scan or mapping setup and point it at the aircraft and model folders actually installed. This display problem does not necessarily mean the network connection failed. |
| Aircraft appear twice | FlightGear multiplayer and VATSIM traffic are both enabled | Disconnect FlightGear’s built-in multiplayer session while using VATSIM. |
| ATC sees the wrong aircraft type | Incorrect ICAO code entered in swift | Correct the aircraft type in the pilot client; changing only the FlightGear aircraft name is insufficient. |
Does every FlightGear aircraft work properly on VATSIM?
Most flyable aircraft can be represented on VATSIM, but radio and transponder synchronisation depends on how the aircraft exposes its systems to FlightGear. A complex add-on may use non-standard properties that swift cannot read correctly.
Watch swift’s displayed COM frequencies and transponder state rather than assuming every cockpit switch has synchronised. If they disagree, test with a standard FlightGear aircraft first. That separates an aircraft-specific property problem from a broken simulator connection.
Can I use FlightGear multiplayer and VATSIM together?
There is normally no reason to run both networks during the same flight. Doing so can mix unrelated traffic, produce duplicate aircraft and make it unclear which network another pilot belongs to. Disable FlightGear’s multiplayer connection and let swift supply the VATSIM traffic while flying on VATSIM.