Today I correctly used SimBrief to plan flight (177 passengers, 1,920kg cargo, 13,585kg of fuel).

However GSX only loaded 8,000kg of fuel and didn't load any passengers, despite loading the correct amount of cargo).

All figures were correct on flight plan, on the Fenix EFB and were even showing correctly on EGLL's safe gate system). Therefore everything had been entered correctly, so why did GSX get it so wrong? Very frustrating.

4 minutes ago, BWBriscoe said:

However GSX only loaded 8,000kg of fuel and didn't load any passengers, despite loading the correct amount of cargo).

GSX doesn't load Fuel on non-default aircraft. It only reacts with its animations, with the truck and the crew staying there for as long the airplane refuels itself.

Strangely boarding started AFTER I switched the beacon on...?

1 hour ago, virtuali said:

GSX doesn't load Fuel on non-default aircraft. It only reacts with its animations, with the truck and the crew staying there for as long the airplane refuels itself.

It does on the Fenix. And the PMDG birds as well, because it can enter the correct amount into the FMS on its own.

So why are you saying it doesn't do that, Umberto? You are the developer, you should know best that it very much does so. 😉

27 minutes ago, Farlis said:

It does on the Fenix.

It doesn't on the Fenix. Everything related to loading (fuel, cargo, pax) on the Fenix is handled by the airplane, which then calls GSX to perform various activities, and none of them changes the airplane status, like fuel quantity or payload.

 

Quote

And the PMDG birds as well, because it can enter the correct amount into the FMS on its own.

That's a different matter, and it's because the PMDG integration is done in GSX (while in the Fenix is in the airplane code), but even if GSX can enter the numbers in the PMDG FMC, doesn't mean "GSX is refueling the PMDG", because it's not. It's only typing numbers in the FMS, but the *actual* refueling is performed by the airplane using its own custom systems.

The only planes which are *actually* refueled by GSX, (GSX altering the fuel quantity in the tanks), are those flagged as using a default Fuel system, so the option "Show Fuel/Cargo page" in the GSX airplane profile is Enabled. None of the advanced 3rd party airplanes supported by GSX (Fenix, PMDG) are configured as such.

Edited October 4, 20241 yr by virtuali

I'm having issues with the boarding process, the doors wont open on the A321 during stair boarding procedures. Any hints?

15 minutes ago, rick celik said:

I'm having issues with the boarding process, the doors wont open on the A321 during stair boarding procedures. Any hints?

Most likely because you installed a custom profile for GSX or you edited one, before the V2.x update, where Fenix changed all the doors IDs. They supplied a new default profile with the updated IDs in version 2.x but, if you had a custom profile made with the previous version, since custom profiles always take precedence over the Internal GSX profile and the developer profile (in this order), one with the outdated IDs will prevent door automation from working correctly, so you must remove any custom profiles for the Fenix in %APPDATA%\Virtuali\Airplane, and restart GSX.

4 hours ago, BWBriscoe said:

All figures were correct on flight plan, on the Fenix EFB and were even showing correctly on EGLL's safe gate system). Therefore everything had been entered correctly, so why did GSX get it so wrong? Very frustrating.

Had the same thing happen yesterday on the A-321.  I use the 'GSX Boarding' through the EFB and it loaded fuel and cargo but never any passengers...

Now on my return flight, it's loaded the fuel and cargo properly, but stopped loading passengers at 90 (I should have 179).

In fact, the bus with passengers on it is next to the aircraft but they're not getting off anymore (all doors are open). See this photo...
https://imgur.com/fmHj7WF

6 hours ago, virtuali said:

Most likely because you installed a custom profile for GSX or you edited one, before the V2.x update, where Fenix changed all the doors IDs. They supplied a new default profile with the updated IDs in version 2.x but, if you had a custom profile made with the previous version, since custom profiles always take precedence over the Internal GSX profile and the developer profile (in this order), one with the outdated IDs will prevent door automation from working correctly, so you must remove any custom profiles for the Fenix in %APPDATA%\Virtuali\Airplane, and restart GSX.

I haven’t got any Fenix profiles in that folder and don’t think I ever did download a custom profile for it. But as mentioned below I’ve had that happen also, cargo and fuel but no passengers , or passengers come really late after everything else has completed… and now the doors don’t open automatically. Will wait to hear if anything is found 

Edited October 4, 20241 yr by rick celik

3 hours ago, BWBriscoe said:

Now on my return flight, it's loaded the fuel and cargo properly, but stopped loading passengers at 90 (I should have 179).

When this happens, is because you haven't used the Fenix integration correctly so, for example, you choose one of the Fast Boarding options in the Fenix, and then called GSX Boarding manually. This resulted in the two process not being in sync anymore so, for example, if the Fenix Boarding was already partially undergoing when you called GSX Boarding, since the Fenix constantly updates the number of passengers in GSX during Boarding, it caused GSX starting its own separate Boarding with a different number than the planned one.

This means:

- If you want to use the Fenix integration correctly, you should not call any of the GSX services manually and only start with the "GSX" option in the EFB.

- If you want to use GSX manually, either use the Fenix "Instant" loading or one of the Fast timed options in the EFB, you must *wait* until AFTER the EFB reports the planned pax number to be on board and then call GSX Boarding.

 

1 hour ago, rick celik said:

now the doors don’t open automatically

When the Fenix integration is in use and, it's the integration that is tasked with the door automation.

If the Fenix integration is not used, GSX is not supposed to automate doors, because it doesn't automate doors using custom XML expression UNLESS it has its own integration (like with the PMDG), but since the Fenix does have an internal GSX integration, GSX is not trying to overstep on it, so it doesn't automate doors, because it relies on the aircraft integration to do that.

Edited October 4, 20241 yr by virtuali

24 minutes ago, virtuali said:

When this happens, is because you haven't used the Fenix integration correctly so, for example, you choose one of the Fast Boarding options in the Fenix, and then called GSX Boarding manually. This resulted in the two process not being in sync anymore so, for example, if the Fenix Boarding was already partially undergoing when you called GSX Boarding, since the Fenix constantly updates the number of passengers in GSX during Boarding, it caused GSX starting its own separate Boarding with a different number than the planned one.

This means:

- If you want to use the Fenix integration correctly, you should not call any of the GSX services manually and only start with the "GSX" option in the EFB.

- If you want to use GSX manually, either use the Fenix "Instant" loading or one of the Fast timed options in the EFB, you must *wait* until AFTER the EFB reports the planned pax number to be on board and then call GSX Boarding.

 

Sorry but I was using everything through the Fenix. Called for GSX loading through the EFB (the only thing I'd done manually was connect the jetway / stairs). 

Two flights now and the integration hasn't worked properly (I was using it flawlessly for months prior).

56 minutes ago, virtuali said:

When the Fenix integration is in use and, it's the integration that is tasked with the door automation.

If the Fenix integration is not used, GSX is not supposed to automate doors, because it doesn't automate doors using custom XML expression UNLESS it has its own integration (like with the PMDG), but since the Fenix does have an internal GSX integration, GSX is not trying to overstep on it, so it doesn't automate doors, because it relies on the aircraft integration to do that.

Ok so what do we do to troubleshoot? As others have said, it was working flawlessly prior. It was either prior to the Fenix update that allowed seated passengers on the a321 or it was a GSX update. Can’t put my finger on it.
 

I’ll try unload and re install Fenix liveries and try cycle through the panel states as a troubleshooting step. I’ll leave uninstalling and reinstalling GSX as last resort. 

This doesn't appear to be an isolated incident...