If GSX can't detect your aircraft type, fix profile mismatches, stale Couatl data, livery conflicts and unsupported aircraft variants.
GSX usually cannot detect an aircraft type because the loaded variant does not match its aircraft profile, the profile is missing or stale, or the Couatl engine has not refreshed after an aircraft change. Confirm the exact model and livery, remove conflicting profiles, then restart Couatl and reload the flight.
This is a general GSX issue covering GSX Pro in Microsoft Flight Simulator and the earlier GSX editions for FSX and Prepar3D. GSX Pro relies on external PC components, including Couatl, so it cannot operate on console-only installations of MSFS.
For MSFS 2024 on PC, use a GSX build and aircraft profile intended for that simulator generation. Our MSFS 2024 GSX compatibility checks cover the additional version and profile considerations.
What does GSX use to identify an aircraft?
GSX identifies the loaded user aircraft from data supplied by the simulator and then applies a matching aircraft configuration. It does not rely solely on the aircraft name, airline livery or ICAO code shown in the aircraft-selection screen.
In MSFS, the base package, model variant and GSX profile must correspond. FSX and Prepar3D add-ons also depend on valid aircraft configuration entries, including a unique title= value in each [fltsim.x] section. A malformed or duplicated entry can make two variants appear identical to external add-ons.
| Symptom | Most likely meaning |
|---|---|
| GSX still shows the previous aircraft | Couatl has retained stale aircraft data after a change |
| Only one variant or livery fails | The model identity or profile does not match that package |
| Every aircraft is unrecognised | Couatl, SimConnect or the GSX installation is not communicating correctly |
| The aircraft is named correctly but doors are misplaced | Detection works, but the geometry profile is wrong |
| The problem occurs at only one airport | The aircraft type is probably not the issue; check the airport or stand profile |
How do I fix GSX aircraft detection?
The quickest fix is to establish whether GSX fails with one aircraft or with every aircraft, then work through the matching branch below.
- Reload the flight completely. After changing aircraft in an active session, return to the main flight setup, load the intended aircraft again and allow the cockpit to initialise before opening GSX.
- Restart Couatl. Use the GSX restart command and wait for it to reconnect. If the GSX menu is unavailable or every aircraft fails, close the simulator, confirm that Couatl is not being blocked or quarantined by security software, and restart the PC installation.
- Test another known aircraft. If that aircraft is recognised, the installation and simulator connection are working. Concentrate on the original aircraft package rather than reinstalling GSX immediately.
- Try the aircraft's supplied livery. A normal texture-only repaint should not change detection, but some liveries are packaged as separate models or aliases. If the supplied livery works, the repaint package is exposing a different or incomplete aircraft identity.
- Temporarily disable competing user profiles. An old community or self-made profile can override the configuration that GSX would otherwise select. Move it outside the active profile location, restart Couatl and test again. Follow our process for installing and validating an MSFS GSX profile when adding the corrected file.
- Match the precise variant. Profiles for passenger, freighter, long-range and engine variants are not automatically interchangeable. The painted name may look the same while the underlying model folder and door layout differ. Fenix and PMDG users should also check the variant-specific GSX fixes for those aircraft.
- Update both components. Run the GSX installer or updater, then update the aircraft through its normal management tool. Aircraft package changes can make an old profile's matching information obsolete.
- Check editable aircraft metadata last. In FSX or Prepar3D, inspect
aircraft.cfgfor duplicatedtitle=values, incomplete[fltsim.x]sections or an invalidsim=reference. In MSFS, restore or reinstall a damaged aircraft package rather than editing protected or encrypted files.
Does the GSX profile have to match the exact variant?
Yes, the profile should match the actual installed model, not merely the aircraft family. A passenger 737, freighter conversion and business-jet derivative can have different exits, cargo doors and service positions even when their cockpits and external shapes look similar.
A profile from another variant may be rejected, attached to the wrong aircraft or loaded with visibly incorrect door positions. Confirm the developer, model, sub-variant and base package before installing it.
Can an aircraft livery stop GSX detecting the type?
A texture-only livery normally cannot, but a livery distributed as a complete aircraft package can change the identity GSX receives. This is especially common with packages that include their own model files, aliases or legacy aircraft.cfg entries.
Test the same aircraft in its original supplied livery. If that works, repair or replace the repaint rather than changing the otherwise correct GSX profile.
Can GSX work with an unsupported aircraft?
GSX can usually service an unsupported aircraft once a custom configuration defines its exits and vehicle positions. Use the GSX aircraft editor to create a profile, save it against the exact variant and restart Couatl before testing.
A custom profile cannot repair a broken simulator connection, missing aircraft metadata or unavailable door animations. If GSX identifies the aircraft but places stairs, loaders or catering vehicles incorrectly, detection has already succeeded; correct the aircraft profile geometry instead of rebuilding the airport database.