Configure GSX Pro Quick Edit pushback in MSFS 2024: set the endpoint and heading, save each direction, test the route, and fix common errors.
To configure GSX Pro Quick Edit pushback in Microsoft Flight Simulator 2024, park at the correct stand, open GSX’s airport-position customisation, launch Quick Edit Pushback, place the aircraft at the desired release point and heading, assign the route to a menu choice, save the airport profile, then test it from the stand.
GSX Pro and its Quick Edit tools require the PC edition of MSFS 2024. They cannot be used on the Xbox Series X|S or PlayStation 5 versions.
How to configure a pushback with GSX Quick Edit
Configure Quick Edit at the exact parking position from which the pushback will be requested.
- Load the correct airport scenery. Start at the gate or stand you intend to edit. If both a default and third-party version of the airport are installed, confirm GSX is reading the one shown in the simulator; the MSFS 2024 compatibility and profile-matching checks explain why this matters.
- Check the stand position first. The aircraft should be parked at the proper stop point and aligned with the stand centreline. Quick Edit builds from that configured position, so an incorrect stop point produces an offset pushback. Correct it first using our guide to editing GSX stand positions and profile data.
- Open the GSX airport editor. Open GSX from the simulator toolbar, select Customize Airport Positions, and verify that the displayed stand is the one occupied by your aircraft.
- Start Quick Edit Pushback. Select the QuickEdit Pushback command and choose the route slot or pushback direction that the editor asks you to configure. The precise wording can change between GSX builds, but the process is the same for each route.
- Set the release point. Using the editor or slew controls shown on screen, move the aircraft to where the tug should finish. Put the aircraft on the taxiway centreline, leave enough room behind it for the tug to disconnect, and point the aircraft’s nose in the required departure direction.
- Accept and save the route. Use the editor’s confirmation or save command rather than simply closing it. If custom route labels are available, use an unambiguous description such as Nose east or Face taxiway A.
- Test from the original stand. Return or reload the aircraft at the gate, leave editor or slew mode completely, request a normal GSX pushback and select the route you created. Watch the wings, tail and tug throughout the turn.
The on-screen Quick Edit control legend should take priority over normal flight-control bindings. GSX temporarily uses editor or slew-style movement, and customised keyboard or controller assignments can change how those commands behave.
What does GSX Quick Edit save?
Quick Edit saves a stand-specific custom pushback endpoint and final aircraft heading in the airport profile.
GSX uses those values to construct the tug manoeuvre from the configured parking position. It does not create an airport-wide rule, so editing one gate will not configure adjacent gates with similar names.
The change belongs to the airport profile, not the aircraft profile. User airport profiles are normally stored under %APPDATA%\Virtuali\GSX\MSFS, where they can be backed up before replacing scenery or making extensive edits.
Aircraft size still matters during testing. A route that clears the terminal with a narrow-body may put the tail or wingtip of a wide-body too close to a building, light mast or parked equipment.
How do I create both pushback directions?
Run Quick Edit separately for every direction or route choice you want GSX to display at that stand.
- For the first route, place the aircraft at its release point and set the required final nose heading.
- Save it to the appropriate route slot or direction.
- Reopen Quick Edit, select the other route and repeat the placement process.
- Test both choices from the gate; saving one route does not prove that the opposite turn has enough clearance.
Terms such as left and right can be misread as either the tug’s initial turn or the aircraft’s final direction. A label based on the final nose heading or taxiway is safer where GSX permits custom labels.
Why does the edited pushback go the wrong way?
A reversed heading, incorrect stand profile or endpoint placed too close to the gate causes most faulty Quick Edit pushbacks.
| Symptom | Likely cause and correction |
|---|---|
| The route is missing from the GSX menu | It was not saved to the occupied stand, or GSX loaded a different airport profile. Reopen the editor and check the stand and active scenery. |
| The aircraft finishes facing backwards | The final nose heading was reversed by roughly 180 degrees. Rerun Quick Edit and rotate the whole aircraft to the required departure heading. |
| The tug makes an excessively sharp turn | The release point is too close to the stand. Move it farther along the taxiway centreline so GSX has more distance to complete the turn. |
| The route crosses grass or scenery | The endpoint or stand stop position is offset. Correct the stand first, then recreate the route rather than repeatedly adjusting only the heading. |
| A route breaks after changing airport scenery | The replacement scenery uses different parking references or stand names. Select or rebuild a profile that matches the installed airport. |
| The route appears, but pushback never starts | This is usually a brake, chock, aircraft-state, tug or conflicting-pushback issue rather than a Quick Edit error. Work through our MSFS 2024 pushback troubleshooting checklist. |