FSDreamTeam forum

Products Support => GSX Support MSFS => Topic started by: MD-82 on May 12, 2025, 09:29:32 am

Title: GSX Automation re. engine start before push
Post by: MD-82 on May 12, 2025, 09:29:32 am
So, yesterday I tried dispatching a flight without an APU. Since it's an airliner, it will start with the aid of a GPU and Air Starter. So, before anything else, I went and selected the option to start engines before pushback in the airplane config and saved.

Now with ASU and GPU connected, I request pushback. GSX is now on hold, waiting for the GPU to disconnect. In other words, the push sequence does not start. I decide to start the engine on GPU and the request push. GSX says nope. The engine needs to be off for the sequence to start. In the end I had to shut down the engine, fix the APU and push back because I could find a way to use GSX when an APU is inoperative and you want to start on GPU before push.

Did I miss something? Maybe an additional setting that bypasses all these checks?

Thanks,
Title: Re: GSX Automation re. engine start before push
Post by: virtuali on May 12, 2025, 10:23:19 am
So, yesterday I tried dispatching a flight without an APU. Since it's an airliner, it will start with the aid of a GPU and Air Starter. So, before anything else, I went and selected the option to start engines before pushback in the airplane config and saved.

That option is not used to start the airplane with a GPU instead of an APU, it's used ONLY for the very rare cases where the airplane doesn't even have an APU, so it must be started in some other way GSX can't recognize, so it will allow to start Pushback if at least one engine has started. It was basically there to support the Concorde.
Title: Re: GSX Automation re. engine start before push
Post by: MD-82 on May 13, 2025, 08:49:30 am
Correct. And because of GSX's PMDG integration, it is recognising that the GPU is connected and won't allow an engine start. Got it.