Had a couple of happy flights this morning in the CFM Fenix and then swapped to the IAE for a quick hop to Santorini. Put the beacon on and waited for pushback at FlyTampa LGAV but nothing happened. Everything is ready to go, chocks are off, APU is running but the pushback guy just stands there looking at me. 
 

Eventually restarted Couatl and the aircraft jumped a tiny bit in the air and then came up with ‘use man pitch trim’ so I suspect it thinks it’s airborne. No way to get out of this state without restarting the sim. 

Is it an IAE thing with SU15?

Quote

Is it an IAE thing with SU15?

I don't think so - I've done a couple of IAE Fenix flights in SU15 and I've not had any issues with GSX so far. 

Did you turn the APU bleed on? I missed that once or twice...

Maybe you need to check if gsx is active in the tablet setting because you change the plane 

I had an awful start to a flight the other week with GSX and the Fenix - when passengers started boarding the gate reversed back to its original position and the passengers began walking through the air to the plane. I also got stuck at pushback as the whole plane vibrated with the sound of the engines spooling up and the wheels rolling but the plane wasn't moving an inch, very weird.

I found out it was a conflict with the Jetway at the airport I had downloaded and the fact that I had forgot to disable it in the Universal Installer. Did that, reloaded the flight and all was good again. Might be worth checking if you haven't already.

My issue is i dont seem to get a prompt asking which direction the pushback needs to be. How is this specified.  So beacon goes on, tug connects, man walks to the side, but pretty much stuck there.

1 hour ago, ErichB said:

My issue is i dont seem to get a prompt asking which direction the pushback needs to be. How is this specified.  So beacon goes on, tug connects, man walks to the side, but pretty much stuck there.

The most common cause for this, is closing the GSX Toolbar Menu with the mouse, instead of following the suggested workflow in the manual:

Quote

This is now your normal workflow should be:

• Open the GSX menu from the Toolbar icon when first starting Ground services.

• Don’t close it from the Toolbar while Ground services are performed, always use the Hot-key or the X icon to close the menu.

• Close the menu using the Toolbar icon when you are done with Ground services, usually before take-off.

In brief, the Toolbar Icon should always be left Active while Ground services are required.

The manual explains why is this in detail, no use repeating it here but, the worse side effect of having closed the GSX menu from the Toolbar in the middle of using it, is that GSX won't be able to display a pop-up menu, with the most important one being the one asking for a direction during Pushback. Because Pushback is important, we added a specific handling for this case, which is the "Continue Pushback" option that will appear if you re-open the menu from the Toolbar again.

I've had an issue a couple of times lately where it will say gsx can not be called while the engines are running.  However the engines were not running.  It's tough to get past that because the option to restart couatl cannot be pressed as the menu automatically passes that and says I can't call gsx with the engines on.  

You can always restart Coatl by rightclicking on its systemtray icon.

Edited June 18, 20242 yr by Farlis

2 hours ago, micstatic said:

I've had an issue a couple of times lately where it will say gsx can not be called while the engines are running.  However the engines were not running.  It's tough to get past that because the option to restart couatl cannot be pressed as the menu automatically passes that and says I can't call gsx with the engines on.  

Fenix? It's an issue with the Fenix load-in state. You need to reselect a panel state in the EFB after loading in.

2 hours ago, Fiorentoni said:

Fenix? It's an issue with the Fenix load-in state. You need to reselect a panel state in the EFB after loading in.

I always load with cold and dark.  but thanks for the tip.  will keep in mind

6 hours ago, micstatic said:

I've had an issue a couple of times lately where it will say gsx can not be called while the engines are running.  However the engines were not running. 

Yes, it's a confirmed bug of recalling a Cold & Dark save state in the Fenix. While the airplane own systems are off, there's a mismatch between the internal engine simulation, and the standard A: variables which represents the engines in the sim, (the only thing GSX can read), reports one engine running.

We reported it to Fenix and they promised a fix. I guess they are fairly busy doing new things, that's why a few minor issues like this (another is the airplane resetting the GSX passengers number to 0 on restarting GSX, for which we had to do a workaround) hasn't been solved yet.

Edited June 18, 20242 yr by virtuali