MSFS 2020 - Using the MSFS standard GPU and Pushback

[Hanse]

In the newest version I experienced that certain MSFS 2020 function keys e.g. calling the GPU = SHIFT+P or the Jetway = SHIFT+J are not working anymore. Is there a reason for this that I have to use the GSX-menu to call the GPU or to attach a jetway? The way using the MSFS function keys were much faster than to go through the GSX-menu. Sometimes it took a long time for loading or even did not start because COUTL has not started yet. Please make those MSFS functions workable gain!

[Hanse]

I just discovered that the Aerosoft A330 uses / calling the standard MSFS GPU in their EFB. Now it is no longer possible to call the MSFS GPU as well as the Jetway using the EFB functions as well as using SHIFT+P or SHIFT+J. Additionally the MSFS GPU is automatically called when the A330 is loaded and the plane (when the GPU is attached) is powered (EXT PWR = ON). This is not working anymore if GSX is installed. If I deinstall GSX everything is working fine again. Virtuali, please comment on this problem. 

[virtuali]

I can only confirm GSX doesn't make any use of those keys, and doesn't try to reserve them for itself.

[Hanse]

OK, thanks that maybe the case, but the problem is that those keys or functions are "blocked" by the latest versions of GSX in MSFS 2020 and 2024. You can easily try it yourself. If GSX is installed SHIFT+P and SHIFT+J does not work anymore. If you "unlink" GSX in the FSDT-Installer those keys and functions work as previously. The other possibility for us in the EFB (if GSX is installed) is to use GSX commandlines or variables to attach the GSX GPU and Jetway. Is something like this available? Thanks!

[virtuali]

You can easily try it yourself. If GSX is installed SHIFT+P and SHIFT+J does not work anymore.

I tried both sims, and there are no problems in either. However, I think there must something going on here because, you say Shift+P is supposed to call the GPU and Shift+J the Jetway. As far as I know, Shift+P in MSFS 2020 calls the default Pushback, and Alt-P in MSFS 2024 does the same.

I tried both in MSFS 2020 and 2024, and they both works even if GSX is installed, and they call the default Pushback.

I don't think it's even possible to assign a key to the GPU or the Jetway in MSFS 2020 or 2024. Sure, the event exists, so if you trigger a >K:TOGGLE_JETWAY command, it will work, but I don't think you can assign it to an hotkey. Could be you were running some other add-on which has added these features ?

The other possibility for us in the EFB (if GSX is installed) is to use GSX commandlines or variables to attach the GSX GPU and Jetway. Is something like this available? Thanks!

Check the \Addon Manager\couatl\GSX\SDK folder, it has documentation and code sample to do Remote Control: you can command GSX to do anything the user could have done, with the menu closed, and the ability to replicate the GSX menus in an airplane gauge.

[Hanse]

Sorry that I mixed up something in MSFS 2020 regarding jetway and GPU. There are no key commands available and SHIFT+J is already used for a camera position in the cockpit. So the only way to call a GPU and connect a jetway is to use the ATC-Menu. Talking about the jetway first: There is no problem to connect the jetway: For an MSFS  standard plane (A320 NEO) you can connect it via the ATC-Menu and for the FENIX A320 as well as the Aerosoft 330 via the EFB. For all 3 type of planes the function is working.

But for the GPU (FENIX A 320 uses not the MSFS GPU) it is different. In the MSFS A320 NEO using the ATC Menu I get the confirmation that the GPU is on the road - but nothing happens at all. The same is with the Aerosoft A330. But if I unlink GSX and start the MSFS 2020 again: Everything is fine e.g. for both planes the standard MSFS GPU truck arrives and connects.

So please check again if in your MSFS 2020 setup (using the current GSX version) that you can call the standard MSFS GPU via the ATC menu p.e. for the standard A320 NEO. I think this test proves that there are problems with your latest updates regarding using the standard MSFS GPU. Thanks.
 

[Hanse]

unfortunately the issure was not solved with version 3.5.6! Any information when this would be solved?

[virtuali]

unfortunately the issure was not solved with version 3.5.6! Any information when this would be solved?

Which issue, exactly ? the key problem ?

[Hanse]

When GSX 3.5.6 is installed, the MSFS GPU is "blocked" by GSX e.g. you are p.e. not able to call the MSFS GPU via the ATC-menu. The Aerosoft A330 uses the MSFS GPU automatically to start in the Turnaround state with EXT PWR on. Because of the issue, this is not working if GSX is installed. If I "delink" GSX in the FSDT Installer everything is working fine. So please make it possible to use the MSFS GPU even if GSX is installed - like it was in previous GSX versions.

[Hanse]

In the meantime we detected another problem with your latest updates: PUSHBACK! If GSX is installed, the internal Aerosoft A330 EFB Pushback does not work anymore as previously e.g. it stops during the procedure and never recovers. Also during and after using the GSX pushback procedure with the Aerosoft A330 the FPS drop by half and never recover. Additionally the MSFS pushback procedure (called via the ATC menu) does not work. But if GSX is "unlinked" in the FSDT Installer everything works fine e.g. the Aerosoft EFB Pushback procedure as well as the MSFS ATC Pushback work as required. So please revert your latest changes regarding the pushback and the GPU. 

[Hanse]

There seems to be a general problem and not just with the Aerosoft A330. When using a standard MSFS plane like the B787 (and GSX is installed) the functions to call a GPU or make a pushback via the ATC Menu does not work e.g. nothing happens! If GSX is unlinked it works perfect as required. So please change this as fast is possible e.g. blocking those two MSFS standard functions if GSX is installed! Thanks.

[Hanse]

Unfortunately the issure was not solved with version 3.5.8! Any information when this would be solved?

[virtuali]

I cannot replicate the issue of not being able to call the GPU from the default ATC menu with GSX is installed, works here. But I don't have the Aerosoft A330, so I can't say if it's related to this airplane.

I can also call the default Pushback from the ATC, but it works so badly that is not even worth trying it.

[Hanse]

Thanks! Let us concentrate an the GPU because it is most important.

Did you try it using MSFS 2020? I cannot confirm your statement and just tried it again. If GSX 3.5.8 is installed and I use the Standard MSFS A320neo I am not able to attach a GPU (via the ATC menu). I can call it, but nothing happens. But when GSX is "unlinked" it works fine e.g. I can call the GPU (via the ATC menu) and see how it arrives and attaches to the plane. In both cases the Aerosoft 300 is installed, e.g. this is not related to this plane but to GSX. Or do you have any other idea? I already deinstalled and reinstalled GSX completely, but this behaviour did not change. Also this behaviour occured only after updating GSX some weeks ago - previously it worked fine. So there must have been some changes in you latest updates in connection with using the GPU.

[Hanse]

I think the problem is related to a modified parking-/stop-position resp. the GSX Airport ini-file that the possition to connect the MSFS-Standard-GPU cannot be found. If I delete the rsp. GSX Airport ini-file or just the two lines for parking- and stop-position then there is no problem anymore e.g. the GPU can be called, arrives and is connected. This was different a couple of weeks ago e.g. it worked with a modified GSX Airport ini-file without problems. Maybe the files have been updated at least for the postion I used for my tests: A20 in EDDF (Aerosoft)