GSX adds ice (!) to the 777 and 737

[Fiorentoni]

Now that might sound hilarious - but it's not a joke.

Context: MSFS 2024, in the 777 and 737 FMC -> Payload menu, there's a field call "icing". It shows the current "icing" value of the aircraft in percent.
I've noticed that very often after the pre flight departure I end up having an icing value in there between 15 and 30% - and that is with outside temperatures of e.g. 25 degrees Celsius.

I've started looking for a reason and also contacted the PMDG support. Now I think I have finally found out - it seems like this is caused by GSX doing inputs on the FMC (or directly on the aircraft variables, not sure).

To reproduce:
Prepare a flight normally, then request boarding via GSX. Now GSX starts navigating and entering something into the FMC pages (payload), and since I don't want that (already distributed all weights as I want it), I quickly change the page back in the FMC to where I want it (usually the ground services overview page). The same happens when I request departure / pushback.
Now it's either the request boarding or the request pushback that causes an icing value to appear afterwards on the payload page. So it seems like the inputs GSX does into the FMC/aircraft do add icing accidentally when I touch the FMC in the meantime. (Theory: it's the boarding request, because the icing percentage 15-30% correlates with typical passenger numbers on the 737 and 777).

Another important info: The actual things GSX tries to do (entering payload, or even fuel before that when requesting a fuel truck) does NOT work at all. Nothing changes on the fuel page or the payload page, even when I leave it alone. So I think PMDG changed / disabled the "API", because they don't want GSX to mess with their FMC.

What I want from GSX: Disable the complete FMC-intervention stuff in the PMDG aircraft, or at least give a setting to disable it.

I attached a log of a flight where it did add about 10-15% of icing (can't remember the exact value anymore) after I requested boarding.

[virtuali]

Prepare a flight normally, then request boarding via GSX. Now GSX starts navigating and entering something into the FMC pages (payload), and since I don't want that (already distributed all weights as I want it), I quickly change the page back in the FMC to where I want it (usually the ground services overview page).

Well, that's what really caused it. The commands sent to the FMC can't be stopped like that: they use a queue, so we are sure they are executed in the same order as they were inserted, but if you change the page ( no matter of quickly ), the queued commands will still execute, but on the wrong page.

It IS already possible to selectively disable various automation features, as explained in the manual at Page 117, the chapter named "Enabling or Disabling GSX own Automation", but it requires access to any utility/script that allows you set LVars (Mobiflight, Spad Next, AxesAndOhs, FSUIPC.), because we added this feature so that airplane developers can disable parts of GSX own automation to replace them with their own.

[Fiorentoni]

Thanks, yes I've read this in the manual and I think I will set it with mobiflight as I already use that for my MCP.

[Fiorentoni]

Quick follow up question regarding those:

"New LVars added to help 3rd party integration: FSDT_GSX_LOADER_EXIT_0, FSDT_GSX_LOADER_EXIT_1, FSDT_GSX_LOADER_EXIT_2. These LVars will be set to 1 if there's a GSX loader at Cargo1, Cargo2 and MainCargo doors. "

I'd like to disable the door automation for the 737F and 77F, but only for the main cargo door - I want to open that door myself (it's quite immersive doing this at the panel). How would I go about setting those in a mobiflight profile? Is the FSDT_GSX_LOAD_EXIT_2 always the one for the main cargo door? And do I have to set it to 0 or to 1 to DISable the door management by GSX?

[virtuali]

"New LVars added to help 3rd party integration: FSDT_GSX_LOADER_EXIT_0, FSDT_GSX_LOADER_EXIT_1, FSDT_GSX_LOADER_EXIT_2. These LVars will be set to 1 if there's a GSX loader at Cargo1, Cargo2 and MainCargo doors. "

Pay attention to the start of the Developers chapter ( Page 86 ):

If a variable is shown on a table with a RED background, it’s supposed to be readonly, if it’s on a GREEN background, it’s a variable add-ons can write to control GSX. Please don’t write values to read-only variables, because it will surely confuse GSX.

These variables are in red, meaning they can be used to read something GSX is doing, opposite to the ones about disabling the automation, which are green, so you are supposed to write to them and control some GSX behavior.

It's not possible to selectively disable door automation for *some* doors. It's either all of them or nothing.