GSX GPU

[XCLTM3]

I have tested this several times with the same outcome.

When calling up for the GPU to be delivered the process is fine.

However, when calling up to remove the GPU, the vehicle is driverless, and, once the GPU is removed, the electrical cable is still attached to the aircraft. The cable eventually disappears a short time later.

[birkenmoped]

I can confirm this insofar as, on my flight yesterday from EDDM to ESSA with the CRJ v2, an empty tractor (without a driver) picked up the GPU and the GPU connection was still shown as connected in the cockpit. In the EFB, the GPU was still shown as “managed by GSX” or something similar, which is actually only displayed there if the connection was established via GSX!

[virtuali]

the electrical cable is still attached to the aircraft. The cable eventually disappears a short time later.

Please clarify "the aircraft"

[XCLTM3]

the electrical cable is still attached to the aircraft. The cable eventually disappears a short time later.

Please clarify "the aircraft"

iFly737 Max 8 (MSFS2020)

[virtuali]

iFly737 Max 8 (MSFS2020)

I checked the internal profile for the iFly 737 Max, and I can confirm GSX is not handling the GPU of the airplane so, whatever is happening, is happening in the airplane code itself, maybe part of some GSX integration.

[XCLTM3]

Thats interesting. I don't use the internal iFly EFB for operations, rather, I use GSX via the GSX Menu. Menu item 8, then 1 (GPU) for both delivery and retrieval. So are you saying that despite the fact I'm using GSX for this operation, that somehow iFly is overwriting that and using it's own internal based GPU operation? The more details I can get from you, I can then pass this onto the devs at iFly.

[virtuali]

I don't know exactly how the iFly integration works so, using the EFB or not, might not matter, it might still be doing something in reaction to GSX events and variables.