Set up voice control with GSX Pro in MSFS using speech-to-key macros, reliable menu commands, push-to-talk and fixes for common failures.
GSX Pro does not include general built-in speech recognition. To use voice control with GSX Pro in Microsoft Flight Simulator, run a PC voice-macro tool that converts spoken phrases into your GSX menu shortcut and number-key selections. Use push-to-talk and follow the visible menu, because service numbers can change with aircraft state.
Does GSX Pro have built-in voice recognition?
GSX Pro's standard interface does not interpret arbitrary microphone speech by itself. Selecting a microphone in MSFS, Windows or a voice-enabled ATC program therefore does not make GSX respond to commands such as start boarding.
You need either a speech utility that sends keyboard inputs or a third-party voice system with explicit GSX integration. This is a PC workflow for GSX Pro in MSFS 2020 or MSFS 2024; it is not available on console editions.
How do I set up GSX Pro voice commands?
- Test GSX manually first. Open its toolbar menu and request a service with the mouse or keyboard. Our guide to the normal GSX Pro service workflow covers the prerequisites. Voice automation cannot repair a GSX menu, aircraft profile or service-state problem.
- Confirm a stable GSX menu shortcut. Choose a key combination that opens the menu and does not conflict with an aircraft, camera or simulator command. Use your configured shortcut rather than copying a supposed default from another installation.
- Configure the microphone. In the voice-macro utility, select the correct input device and use push-to-talk where possible. Set the utility to send keystrokes to Microsoft Flight Simulator.
- Create a menu command. Map a phrase such as
GSX menuto the GSX shortcut. Keep the simulator window active while testing it. - Create selection commands. Map
one,twoand the other required numbers to the corresponding keys accepted by your GSX menu. A separatecancelcommand can send the key you normally use to close or back out of the menu. - Add a short pause between actions. If one phrase opens the menu and chooses an item, the macro must wait until the GSX panel is ready before sending the number. Otherwise, MSFS receives the number too early.
- Test at a parked aircraft. Begin with a simple service request and watch every menu change. Only build longer commands after each individual input works reliably.
Which voice-control method works best?
| Method | Choose it when | Main limitation |
|---|---|---|
| Spoken menu and number commands | You want the most dependable setup and do not mind reading the visible GSX menu | Requires more than one spoken command |
| One-shot keyboard macro | The menu always starts on the same page and the required option stays in the same position | Can request the wrong service when GSX changes the menu order |
| GSX-aware voice integration | Your voice software explicitly supports the installed GSX Pro and MSFS versions | Compatibility depends on that integration being maintained |
For most setups, we recommend separate menu and number commands. A mistake we see constantly is assigning start boarding to a blind sequence such as open menu, press a fixed number and confirm. GSX changes available options according to location, service progress and aircraft state, so the same number may later mean something else.
Why is my GSX voice command recognised but nothing happens?
If the speech utility recognises the phrase but GSX does nothing, input delivery rather than speech recognition is usually at fault.
- Wrong window: MSFS must have keyboard focus. A browser, text field or another toolbar panel may be receiving the keys.
- Windows permission mismatch: The simulator and voice utility should run at compatible privilege levels; automated input can be blocked when one is elevated and the other is not.
- Shortcut conflict: Remove any duplicate MSFS or aircraft binding that uses the GSX menu combination.
- Wrong number keys: Test the top-row digits and numeric keypad manually. Send whichever set your installation accepts.
- Macro runs too quickly: Insert a pause after opening the toolbar panel and after each submenu change.
- Incorrect service starts: Replace the fixed sequence with separate spoken number commands, then select from the menu shown on screen.
- GSX refuses the service: Read its displayed reason and correct the aircraft or stand state. If the same request fails when clicked manually, the voice setup is not the cause.
Can one microphone control both ATC and GSX?
One microphone can serve both systems, but ATC software does not automatically pass ground-service commands to GSX. Use separate push-to-talk buttons or clearly distinct command phrases so an ATC transmission does not trigger a GSX macro.
For microphone calibration, recognition thresholds and push-to-talk configuration, use our voice ATC setup and troubleshooting advice. Test the ATC and GSX profiles separately before enabling both together.
Can voice commands control GSX pushback?
Voice commands can request pushback and select an existing GSX option, but they do not calculate a safe route or interpret an ATC clearance. Configure the route first, then use voice control to choose it from the displayed menu.
Pre-planned routes are safer than blindly sending left, right or straight-ahead selections. Our instructions for editing GSX Pro pushback routes and controls explain that stage. Wait for GSX to acknowledge each request before speaking the next command.