Use GSX Pro with SayIntentions.AI in MSFS 2024: follow the correct gate-to-pushback sequence, avoid duplicate commands and fix common conflicts.
Use GSX Pro for physical ground handling and SayIntentions.AI for spoken ATC in Microsoft Flight Simulator 2024. Start both PC clients before the flight, complete GSX boarding and servicing at the stand, obtain the required ATC clearances through SayIntentions.AI, then let GSX alone perform pushback. The two tools complement rather than replace each other.
What does each add-on control?
GSX controls the visible ground operation, while SayIntentions.AI handles radio communication and ATC instructions. Keeping those responsibilities separate prevents duplicate pushback commands and conflicting gate procedures.
| Task | Use GSX Pro | Use SayIntentions.AI |
|---|---|---|
| Boarding, catering and baggage | Yes | No, except supported announcements or event awareness |
| IFR clearance and radio calls | No | Yes |
| Pushback tug and route | Yes | No |
| Pushback or start approval | No | Yes, where the airport procedure requires it |
| Taxi instructions | No | Yes |
For the broader strengths and limitations of the AI controller, see our comparison of MSFS 2024 ATC add-ons.
How do I set up GSX and SayIntentions.AI together?
Set both applications up separately, then connect them to the same running MSFS 2024 flight.
- Verify the GSX installation. In the FSDT installer, confirm that the MSFS 2024 package is installed or linked to the active
Communityfolder and that Couatl starts correctly. Our MSFS 2024 GSX installation and compatibility checks cover the package-location details. - Load at a parking stand. Start at a gate or ramp position rather than on the runway. Set the parking brake and use a stand large enough for the aircraft; an unsuitable stand can cause poor vehicle placement before SayIntentions.AI is involved.
- Connect SayIntentions.AI. Confirm that its client sees the simulator, then check the microphone, push-to-talk input, callsign and flight plan. The filed route should agree with the route in the aircraft's FMS or EFB.
- Run the GSX turnaround. Request deboarding, catering, refuelling, baggage and boarding as needed. Follow GSX door prompts and keep the parking brake set. The full GSX gate-service sequence explains the normal order without duplicating it here.
- Obtain the appropriate clearances. Use SayIntentions.AI for delivery, ground or ramp communication. IFR clearance can usually be handled while GSX is still servicing the aircraft.
- Prepare one pushback method. Select or pre-plan a GSX pushback route that matches the controller's instruction. Do not activate the simulator's built-in tug or an aircraft EFB pushback system as well.
- Push and taxi. Once approval has been received where required, start pushback through GSX and obey its brake prompts. After the tug is disconnected and the aircraft is ready, call SayIntentions.AI for taxi.
Does SayIntentions.AI control GSX automatically?
SayIntentions.AI does not replace the GSX menu or directly drive its vehicles in the core workflow. The practical integration is that ATC provides the clearance while GSX performs the physical operation.
If the installed SayIntentions.AI client presents a setting labelled for GSX integration, enable it only after both clients are connected. Such options can use supported GSX states to trigger cabin or turnaround events, but service requests and tug movement still belong in GSX. If that setting is absent from a particular client feature set, the manual sequence above remains valid.
How should I coordinate pushback clearance with GSX?
Treat ATC approval and tug control as two separate actions: obtain or confirm the applicable clearance through SayIntentions.AI, then perform the movement once through GSX.
At some airports, pushback is controlled by ground or ramp personnel. At others—especially where the stand is in a non-movement area—the controller may say that pushback is at the pilot's discretion. That response is not an integration failure. It means GSX can perform the push while the pilot remains responsible for clearance from nearby aircraft and obstacles.
If ATC specifies a direction, choose the GSX route that leaves the aircraft facing that direction. Profile names such as left, right or a taxiway identifier can be ambiguous, so inspect the planned path rather than guessing from the label.
Why do GSX and SayIntentions.AI sometimes appear to conflict?
Most apparent conflicts come from duplicate controls, mismatched flight information or microphone audio rather than direct interference between the applications.
- The aircraft moves before GSX is ready: another pushback system is active. Cancel the built-in tug or EFB pushback, set the parking brake and use only GSX.
- ATC gives an unexpected route or runway: check that the departure, callsign and flight plan in SayIntentions.AI match the aircraft's active route.
- The assigned parking position differs from GSX: taxi to the stand given by ATC, park there, then request GSX arrival services for that actual stand.
- Cabin or ground audio triggers speech recognition: use push-to-talk and prevent speaker output from feeding back into the microphone.
- The GSX menu or vehicles disappear: troubleshoot Couatl, the MSFS package link and airport profiles independently. Our GSX connection and Couatl troubleshooting steps cover those failures.
Can I use this combination on Xbox or PlayStation 5?
No. Although MSFS 2024 is available on PC, Xbox Series X|S and PlayStation 5, GSX Pro depends on external Windows software and is therefore a PC-only add-on. The combined GSX Pro and SayIntentions.AI workflow cannot be reproduced on the console editions.