Use GSX Pro Profile Manager in MSFS to match profiles to the correct airport scenery, prevent conflicts and fix profiles that will not load.
Open the GSX Pro Profile Manager from the FSDT Installer or its Windows shortcut, scan your Microsoft Flight Simulator packages, then select the exact airport scenery installed and import or enable its matching profile. Apply the change, restart Couatl, and keep only one applicable profile enabled for that scenery variant.
What does GSX Pro Profile Manager do?
GSX Pro Profile Manager installs, associates and organises airport profiles without changing the airport scenery itself. A profile supplies GSX-specific data such as vehicle positions, stopping points, walking routes, service providers and customised pushback instructions.
The match is based on more than the ICAO code. A profile made for a default airport may not fit a third-party version of the same airport because its stands, parking indexes and compiled airport data differ. The manager is a Windows utility, so this workflow applies to PC installations rather than console editions of Microsoft Flight Simulator.
| GSX tool | Use it for |
|---|---|
| Profile Manager | Importing, enabling, disabling and matching airport profiles |
| Airport customisation editor | Changing an individual stand, stop position or service arrangement |
| GSX Pro Config | Controlling GSX jetway replacement and related installation settings |
How do I assign a GSX profile to an MSFS airport?
The safe method is to match the profile to the airport package and simulator version for which it was created, not merely to an airport with the same ICAO.
- Close MSFS and Couatl. This prevents an active GSX session from retaining an older profile while files are being changed.
- Launch Profile Manager. Open it through the GSX Pro entry in the FSDT Installer or its installed Windows shortcut; exact button wording can vary between installer builds.
- Scan the correct simulator installation. If both Microsoft Flight Simulator 2020 and 2024 are installed, confirm that the manager is reading the package libraries for the version you intend to use. Rescan after moving a Community folder or changing a package-library location.
- Find the airport and scenery variant. Check the ICAO, package name and scenery edition. Select the third-party package if that is what appears in the simulator, rather than assigning a profile made for the default airport.
- Import or add the profile. Choose the supplied profile file or archive using the manager's import function. Do not select the airport scenery package itself. If an archive is not accepted or the download contains loose files, our guide to installing GSX airport profiles manually explains the expected file location and matching process.
- Review the detected association. Confirm that the profile targets the installed airport package or airport-data file. Do not force a profile onto unrelated scenery simply because both use the same ICAO.
- Resolve competing profiles. Disable or remove obsolete profiles for the same installed scenery, but back up any version containing your own edits first. A manually copied profile can remain in
%APPDATA%\Virtuali\GSX\MSFSafter a managed profile is installed. - Apply and reload GSX. Save the manager's changes, launch Microsoft Flight Simulator and restart Couatl if it was already running.
How can I tell whether GSX loaded the right profile?
The profile is working when GSX's stand layout and services reflect the installed airport rather than generic positioning.
- Open GSX at a parking stand, not from a runway start.
- Check that the selected gate corresponds to the stand displayed in the scenery.
- Verify that marshallers, service vehicles and stopping positions are not inside buildings or other static objects.
- Inspect the available pushback directions; named or customised routes should match the profile documentation.
- If your GSX build displays an active profile or airport-data path in the customisation screen, confirm that it references the intended scenery package.
A profile can load successfully yet still contain inaccurate positions after the airport scenery has been updated. For the operational sequence after loading a flight, see our explanation of using GSX services at the gate.
Why does the GSX airport profile not appear?
A missing profile is usually caused by a scenery mismatch, duplicate file, stale Couatl session or scan of the wrong MSFS package library.
| Symptom | Likely cause and correction |
|---|---|
| GSX uses generic stand positions | The profile targets another edition of the airport. Install a profile made for the exact scenery package. |
| The manager shows the profile, but GSX ignores it | Restart Couatl and check for an older manually installed .ini profile that takes precedence or conflicts. |
| The airport is absent from the manager | Rescan the correct MSFS installation and verify that the airport package is enabled. |
| The profile worked before a scenery update | The airport developer may have changed parking records or package data. Update the profile or re-save the affected stands. |
| Files were copied but nothing changed | The profile may be nested inside an extra folder or placed directly in Community instead of the GSX user-profile location. |
For Couatl errors, package-link problems and wider installation faults, follow our GSX Pro troubleshooting checks for MSFS 2024.
Can I edit an imported profile?
Yes, imported profiles can be customised through GSX's airport editor, but save a backup before replacing or updating the original profile.
Use the in-simulator airport customisation controls for stand-specific changes. Pushback geometry can be adjusted and saved with Quick Edit; our Quick Edit pushback procedure covers the route, naming and save process without duplicating the entire profile.
Reimporting a newer copy may overwrite local changes. Choose the updated profile when the airport layout itself has changed; retain your edited copy when it still matches the scenery and contains stand or pushback work you need.