Set up swift for IVAO in MSFS 2024: connect with SimConnect, configure MTL model matching and audio, and fix missing traffic or login errors.
On a Windows PC, install swift and an MSFS-compatible IVAO traffic model package, select Microsoft Flight Simulator in swift, scan the model folder and activate the resulting model set. Start MSFS 2024, load at a parking stand, connect swift through SimConnect, then log into IVAO and configure audio and push-to-talk.
What do you need before setting up swift?
You need the Windows PC edition of Microsoft Flight Simulator 2024, an IVAO account, a maintained swift build supporting both MSFS and IVAO, and locally installed traffic models. swift cannot run alongside the Xbox or PlayStation editions because it is an external desktop client.
MSFS 2024 communicates with swift through SimConnect. A normal same-PC installation does not require FSUIPC or an extra connector in the Community folder.
How to set up swift for IVAO in MSFS 2024
- Install swift: install a stable Windows build whose release information explicitly includes Microsoft Flight Simulator and IVAO support. Use swiftLauncher to start both swiftCore and swiftGUI; the graphical client cannot function properly without the core process.
- Install IVAO traffic models: add an MSFS-compatible MTL package before building the model set. Our IVAO MTL installation and model-matching walkthrough covers the package side without confusing the MSFS 2020 and MSFS 2024 Community folders.
- Select the simulator: choose the Microsoft Flight Simulator or modern MSFS SimConnect driver in swift. Some builds may retain MSFS 2020 wording for this driver; MSFS 2024 uses the same general SimConnect interface. Do not select an X-Plane, Prepar3D or legacy driver.
- Scan the MTL folder: point swift's model scanner at the Community folder containing the IVAO models. Run the scan, create or update the model set, and make that set active. Scanning a Community folder from MSFS 2020 is a common reason for an empty model list in MSFS 2024.
- Choose fallback aircraft: assign sensible airliner and general-aviation fallback models. They will be shown when swift cannot find an exact airline, type or livery match.
- Prepare MSFS 2024: start the simulator and load fully into an aircraft at a parking stand. Turn off MSFS multiplayer and AI traffic so swift is the only programme injecting online aircraft.
- Connect to the simulator: start the simulator connection in swift and verify that it identifies your aircraft. Simulator connection and IVAO login are separate stages; a green simulator status does not mean you are online.
- Configure IVAO: select IVAO as the network, enter your VID and the network credential IVAO specifies for third-party clients, then provide the callsign and correct aircraft ICAO code. Do not use an email address or display name in place of the VID.
- Set up voice: select the microphone and headset explicitly, assign a push-to-talk button and check the input meter. Avoid binding push-to-talk to a control already used for brakes, trim or the parking brake.
- Connect from the stand: file the flight plan, confirm the callsign and connect while parked rather than on a runway. Our complete MSFS-to-IVAO connection workflow explains the traffic, flight-plan and first-contact stages.
Which MSFS traffic settings should be disabled?
Disable native traffic sources that would draw a second aircraft on top of each IVAO contact. The wording can vary between simulator updates, but the relevant settings are:
- online multiplayer aircraft;
- live or real-time AI traffic;
- offline AI traffic;
- airport ground aircraft, if static models overlap IVAO traffic.
Nameplates are optional and do not create duplicate traffic. Keep them off for realism or enable them while checking that model matching works.
Why is swift connected but no IVAO aircraft appear?
A connected simulator with no visible traffic usually means the model set is empty, inactive or built from the wrong content folder.
| Symptom | Likely cause | Fix |
|---|---|---|
| No simulator connection | Wrong simulator driver, MSFS has not finished loading, or swiftCore is not running | Start core and GUI from swiftLauncher, load into the cockpit, then reconnect using the MSFS SimConnect driver |
| No remote aircraft | MTL models were scanned but no model set was activated | Rebuild the model set, mark it active and restart the simulator connection |
| Models missing after moving MSFS | swift still points to the old Community folder | Remove the stale path, scan the actual MSFS 2024 package location and rebuild the model set |
| Wrong or generic aircraft | No exact type or livery match exists | Update the local MTL package and configure sensible fallback models |
| Duplicate aircraft | MSFS multiplayer or AI traffic remains enabled, or another pilot client is running | Disable native traffic and close the second client |
| Login rejected | Incorrect VID, wrong credential, duplicate session or invalid callsign | Re-enter the IVAO details and ensure the account is not connected elsewhere |
| Traffic causes heavy stuttering | swift is using complex flyable aircraft instead of dedicated traffic models | Restrict the active set to suitable MTL models and reduce the displayed traffic range |
Does IVAO voice always work through swift?
Simulator compatibility does not guarantee voice compatibility. IVAO can change its authentication and voice systems independently of SimConnect, so the installed swift build must explicitly support the IVAO services in use.
If swift connects to MSFS but offers no functioning IVAO voice, do not run IVAO Altitude simultaneously just to supply audio; two pilot clients can create duplicate network sessions and traffic. Use one fully compatible client. For flight plans, frequencies and expected online conduct, see our practical guide to making a first IVAO flight.
Should you use swift or IVAO Altitude?
Choose swift when you specifically want its multi-network interface and detailed model-set controls, and its build supports IVAO login and voice. Choose IVAO Altitude when you want IVAO's own supported client with the least complicated setup. In either case, run only one pilot client during the flight.