MSFS 2020 - Using the MSFS standard GPU and Pushback

[hwmertens]

Hi,
I can confirm a problem with In-Game ATC services when GSX Pro is loaded in MSFS 2020.
No A330 here but I checked with the Fly-By-Wire Mod for the Asobo A320neo.
My result: GSX has "stolen" the In-Game pushback vehicle, so ATC is rejecting pushback requests.
In-Game GPU works and pushback via Shift+P is also ok.
Regards
Hans

[virtuali]

GSX will remove the default pushback only after you call GSX, which of course is normal. However, I can't see how GSX can possibly disable the default pushback by "just" being installed. In MSFS 2020, you can disable all AirportServices, try to do that.

[Hanse]

Hi Umberto,

I hope, if some other develloper has "broken" something in GSX with one of his update, that he would be as cooperative as you are in this case! You do not seem to understand (and did not read my last messages) that we are just lately talking about the standard MSFS GPU only, which cannot be used anymore via the ATC menu after your last updates. This is related to two entries in the GSX airport ini-file: "parkingsystem_stopposition =" as well as "this_parking_pos =".  If I remove those two lines from the file everything is working fine again e.g. the standard MSFS GPU can be called again via the ATC menu. 

Regards,

[virtuali]

If I remove those two lines from the file everything is working fine again e.g. the standard MSFS GPU can be called again via the ATC menu. 

That seems to indicate the GSX customized STOP position in the airport profile is so different from the one that MSFS calculates with its own methods, that MSFS itself is considering the airplane to be either outside the parking spot, or maybe too far away to be serviced by the GPU (or the Pushback).

It might be enough to adjust both the GSX Parking center and the STOP position, but if to obtain a good result in GSX you would cause MSFS to stop generating its own ground services, an adjustment of the airport .BGL itself might be required.

[Hanse]

Thanks and your explanations seem reasonable. But unfortunately it is something different: If I use for the two mentioned lines in the ini-file the same data like in the airport BGL-file then the plane parks exactly at the same position like without ini-file, but still the MSFS GPU cannot be attached ! Only if I remove the two lines in the ini-file the MSFS GPU connects. This behaviour clearly states that the problem are not the position but the lines itself. some weeks ago it worked fine with those two lines but suddenly the behaviour changed. So again, GSX must have changed something in connection with the parking- and stop-position or it is related to the newest MSFS beta version.

[virtuali]

Only if I remove the two lines in the ini-file the MSFS GPU connects. This behaviour clearly states that the problem are not the position but the lines itself.

The parking position in GSX would affect the center of the parking radius around which all default ground vehicles will be removed by GSX. Of course, this will happen only AFTER you call the GSX menu, but it seemed you said the GPU didn't work "just" because GSX is installed, which I just can't see how's possible.

GSX always removed all default ground vehicles around your airplane after you call GSX, which not only is normal and to be expected, but it has always been like this in years. Clearly, if you want to use default ground vehicles, just don't call GSX, on the other hand, if you want to use GSX (calling its menu), the default GSX must be removed, otherwise they'll interfere with GSX.

None of this changed in GSX and it would affect only vehicles removed after using the GSX menu.

[Hanse]

You are writing that all default ground vehicles (like the GPU and Pushback truck ) will be removed only AFTER the GSX menu is called. Sorry, this is not the case in connection with the GPU and the PB truck. Even when the GSX-icon on the menu bar is "black" it is already not available. This might be the case (removed when opning the GSX menu) for other MSFS ground vehicles, which you see disappearing when opening the GSX menu and selecting a service. But in case of the MSFS GPU you can avoid this behaviour only if GSX is "unlinked" in the FSDT Installer.

I selected a standard MSFS airport (like EDDS Gate 72 - with no airport ini-file) and in the attached document you can see the differences between GSX installed (linked) and unlinked after loading a plane. Especially you can see that the PB truck is already removed BEFORE the GSX menu is opened. This proves that already in connection with the GSX installation (not with opening the GSX menu) something happens to the ground vehicles. And this gets more weird if there is an aiport ini-file with the two lines in the ini-file: "parkingsystem_stopposition =" as well as "this_parking_pos =".

You should really look in depth into your program to sort this out and not making just some statements which can easily be checked and found wrong. After making many attempts to find the root cause I can clearly state that the ini-file entry "parkingsystem_stopposition =" is the reason for removing at least the MSFS GPU. If there is an entry (even at the original BGL-parking position) the GPU is removed. If I remove this entry from the ini-file then everything is OK e.g. the MSFS GPU is not removed and available.     

[virtuali]

I can replicate the problem of the missing default Pushback and I think I found the cause, but the GPU works fine and can be called.

Note that, with "default Pushback" and "default GPU", I mean the default services that are called from the ATC menu. However, with GSX installed, they will LOOK like GSX vehicles, even if they are still default ground vehicles.

When you open the GSX menu, they will be removed to be replaced by GSX-proper vehicles, which in many cases might look identical, but are GSX vehicles controlled by GSX.