Feature Request: Pilot-Centric Automated Pushback System (GSX-style Implementation)

  • Dear IPACS Development Team,

    First, I would like to express my appreciation for the incredible work you have done with the physically simulated pushback system in Aerofly FS. The realism of the tug’s physics and the immersion of the driver camera are outstanding features that set this simulator apart.

    However, I would like to propose a "quality of life" evolution for this system to better reflect real-world cockpit operations. Currently, the manual control of the tug (using throttle and rudder inputs) requires the pilot to act as both the flight crew and the ground equipment operator simultaneously.

    The Proposal: Automated Ground Crew Assistance
    I am suggesting an optional, more automated pushback solution similar to the one found in GSX (Ground Services X). Instead of the pilot steering and powering the tug, the system would allow us to:

    1. Select a pre-defined path: Choosing "Nose Left" or "Nose Right" toward the nearest taxiway.
    2. Delegate the maneuver: The ground crew handles the steering and power automatically based on the selected exit.
    3. Focus on the Cockpit: This allows the pilot to dedicate their attention to what they do best: performing engine starts and completing pre-flight checklists without the risk of mishaps or "forcing" the throttle while looking outside.



    In the real world, the pushback is a coordinated effort where the pilot remains "in the loop" but is not physically steering the tug. An automated option would bridge the gap between Aerofly's high-fidelity physics and a more natural operational workflow.

    I have attached a screenshot of how this is implemented in GSX to illustrate the simplicity of the selection menu.

    Thank you for your time and for your continuous dedication to making Aerofly FS a top-tier simulation experience. I look forward to hearing the community's and the team's thoughts on this!

    Kind Regards,

    AeRodri

    Specs: 16-inch MacBook Pro 2019, 2.3 GHz 8-Core Intel Core i9 Processor, 16 GB 2667 MHz DDR4 RAM,
    AMD Radeon Pro 5500M 4 GB, 1TB Apple SSD, currently on MacOS Sequoia 15.7.3 + 2x Alienware AW3225DM.
    On the latest version of AeroFly FS 4 from Steam. Visit my dedicated AeroFly Instagram: https://www.instagram.com/realflightops/
    Visit my newly created AeroFly YouTube channel: https://www.youtube.com/@RealFlightOps

  • I like this idea as an extension to the pushback.

    From my point of view, the current pushback in the FS 4 is a "pushback light", because in principle the aircraft drives backwards and pulls a pushback tractor behind it (therefore there are, for example, the restrictions on the angle and the exclusive reverse driving of the aircraft).

    I have activated the FS 4 pusback tractor so that it can also drive independently - also in the pushback function. I now call this variant "pushback normal", because the pushback tractor is actually driven here and collisions can occur very quickly if used incorrectly.

    The third variant would then be from my point of view the proposed "pushback automatic".

    For the implementation of "pushback automatic" I suggest offering this only at selected positions, because otherwise it can quickly come to a lot of problems. By this I mean that at these positions every aircraft that can be positioned in the position can also be automatically pushed back cleanly along the existing taxi lines without colliding with any objects (buildings, aircraft, vehicles, ...). From my creation of over a thousand airports, I know that this is not trivial.

    And I suggest expanding the pushback icon. Marked with a black "A", the pushback icon could indicate that an automatic pushback is possible. And then, as with the gliders, the user could choose which type of pushback should be carried out.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • The issue is not controlling the pushback automatically, we designed the system to eventually be fully automatic. The issue is that the lines at the airports are currently just dummy lines without any logic so there is no "centerline" we can just taxi to, it's just visual, living on the graphics card. A major redesign of all airports is due which would mean the lines actually have function and are connected by nodes and are not just visual objects. But that's a major obstacle we have to overcome first and automatic pushback will fall right out as a byproduct.

    Regards,

    Jan

  • The issue is not controlling the pushback automatically, we designed the system to eventually be fully automatic. The issue is that the lines at the airports are currently just dummy lines without any logic so there is no "centerline" we can just taxi to, it's just visual, living on the graphics card. A major redesign of all airports is due which would mean the lines actually have function and are connected by nodes and are not just visual objects. But that's a major obstacle we have to overcome first and automatic pushback will fall right out as a byproduct.

    So does this mean that additional ground services will be added like cargo, catering, passengers etc?