GSX Services disappear when beacon is turned off - Fenix

[Pirateinparadise]

I'm having a problem with de-boarding in the Fenix. When I pull up to the gate and shut down the engines, I wait until the N2% drops below 5% and then I turn off the seat belt signs, no smoking signs, and then the beacon. GSX announces "De-boarding requested", and then all of the GSX vehicles and marshaller disappear. From here, I have to restart Couatl, and manually request de-boardig again. The service vehicles reappear (after I make all of the menu selections) and then everything works properly except the passengers are staying seated even thought the jetway is connected and the door is open. I've also tried selecting deboard on the Fenix tablet and I get the same results.

The odd thing is that the other day, for one flight, it de-boarded properly without a Couatl restart. The next 3 flights did not work.

I haven't seen any other reports of this, so I'm guessing I have something going on with my installation.     

[lexussteve]

I have the exact same issue using the same process as you….the passengers just continue to sit in their seats.

[Pirateinparadise]

I had a slight variation to this last night. Landed at FB KSFO and pulled into gate a15 using the marshaller. I tried not waiting so long for the engines to spool down. At about 10%, I flipped all of the switches and got the deboarding requested announcement. Poof! All GSX vehicles and personnel vanished. I restarted Couatl, went through the menus, and this time the pax actually deboarded. The EFB did not show the pax count decreasing, or seats emptying on the seating chart, though.

I'm at a loss. I don't see anything in the log.

[virtuali]

That looks like a crash so, as any other crash, it can be identified by providing a diagnostic log, if you have logging Enabled when it happens. Note that, for the log to be meaningful, you should ZIP it and Attach it here before you restart the Couatl engine, because restarting will create a new log, overwriting the previous one.

[Pirateinparadise]

Log attached

[Pirateinparadise]

I flew the same flight again, but this time I removed the .ini file for KTPA. New log attached.

EDIT: Also flew the flight in reverse, from KTPA to (FSDT) KCLT. I had the same issue. Attached 'Couatl - KCLT.zip' log for this flight.

EDIT 2: Just flew KPDX to KSFO (both Flightbeam) and had no problems with de-boarding.  The Mass and Balance screen also updated properly as well. Attached 'Couatl - worked fine kpdx-ksfo.zip' log for this flight.

[Pirateinparadise]

Did a flight to Boston earlier today, and the same problem happened again.

[virtuali]

Your shows the real cause of the problem:

Error: exception JETWAY_DATA in call RequestJetwayData param #99 'KTPA'

The error #99 is a panic code from Simconnect Navdata API, indicating something is wrong in the airport, like a faulty or missing jetway, and that will surely break all operations.

[Pirateinparadise]

Thank you for the response.

Will you be correcting this in KCLT since it also has the error #99?

Bad Jetway data at KCLT - Concourse D|Gate 5
Error: exception JETWAY_DATA in call RequestJetwayData param #99 'KCLT'
{'Airport': 'KCLT', 'Requested assistance services at': 'Gate F 80', 'Requested parking services to': 'Gate F 80', 'User Pos': (35.20199897440113, -81.06724781013075, 2818.16 m, 2623.47 m, 355.0647369011257, -0.029166441625976522, 0.001745329238474369, 0.0006527372341260218, 3.18211187210083, 0.0)}

[virtuali]

Will you be correcting this in KCLT since it also has the error #99?

If you mean FSDT KCLT, we don't have any error in the airport, I can't see that error logged with FSDT KCLT installed and jetway at D5 works fine.

Your error log line suggests you had this problem when you were at Gate F 80. However, this gate doesn't exists in FSDT KCLT and it doesn't exists in the default MSFS scenery either so, it seems you must have some conflict caused by extra data which added a non-existing parking spot flagged to have a jetway but not really having it.

Also, I checked the coordinates in your error log, and it shows you were still flying when you selected the (non existing) Gate F 80 at KCLT. There's a limitation in the Navdata API that it won't return any data about Jetways until after jetways have been actually loaded by the sim, but from your location I think you were too far, usually they load much later, however they shouldn't return that error so, I think it's a combination of issues.

[moxiejeff]

I too am having lots of issues w/ latest update and Fenix. Passengers aren't showing (even though boarding is happening) - and yes, I unchecked/checked the A321 during GSX update in options before starting. Nothing seems to be automating in GSX for some reason in fenix.

[virtuali]

I too am having lots of issues w/ latest update and Fenix. Passengers aren't showing (even though boarding is happening) - and yes, I unchecked/checked the A321 during GSX update in options before starting. Nothing seems to be automating in GSX for some reason in fenix.

Fenix automation works normally, passengers shows up, but be sure you run the latest update again, because we had a couple of fixes after the update:

https://www.fsdreamteam.com/forum/index.php/topic,32308.0.html

[Pirateinparadise]

Will you be correcting this in KCLT since it also has the error #99?

If you mean FSDT KCLT, we don't have any error in the airport, I can't see that error logged with FSDT KCLT installed and jetway at D5 works fine.

Your error log line suggests you had this problem when you were at Gate F 80. However, this gate doesn't exists in FSDT KCLT and it doesn't exists in the default MSFS scenery either so, it seems you must have some conflict caused by extra data which added a non-existing parking spot flagged to have a jetway but not really having it.

Also, I checked the coordinates in your error log, and it shows you were still flying when you selected the (non existing) Gate F 80 at KCLT. There's a limitation in the Navdata API that it won't return any data about Jetways until after jetways have been actually loaded by the sim, but from your location I think you were too far, usually they load much later, however they shouldn't return that error so, I think it's a combination of issues.

But the log shows that I selected Gate D5 at KCLT (I was on approach, below 10,000' and slower than 250kts when I selected Concourse D|Gate 5, Then, the log refers to Gate F80 which was the gate at KPTA that I departed from an hour earlier. It seems like GSX took my request for KCLT D5 and then immediately used the info from my departure instead of my arrival gate.

Loading airport KCLT
Using airport customization from GSX.airports.kclt_fsdt_msfs
Loading user customizations from C:\Users\Captain\AppData\Roaming\Virtuali/GSX/MSFS\kclt-fsdt.ini
MSFS always use CheckIcingConditionsSimple() + surface condition
Icing test =  0 9.73718261719 False
emulateMenu_MSFS
emulateMenu_MSFS CHOICE 3
channel.balance =  -1
emulateMenu_MSFS
emulateMenu_MSFS CHOICE 4
channel.balance =  -1
FSDT_GSX_SetGate 15 5 0
Assistance Auto mode set externally to False
Bad Jetway data at KCLT - Concourse D|Gate 5
Error: exception JETWAY_DATA in call RequestJetwayData param #99 'KCLT'
{'Airport': 'KCLT', 'Requested assistance services at': 'Gate F 80', 'Requested parking services to': 'Gate F 80', 'User Pos': (35.20199897440113, -81.06724781013075, 2818.16 m, 2623.47 m, 355.0647369011257, -0.029166441625976522, 0.001745329238474369, 0.0006527372341260218, 3.18211187210083, 0.0)}
Error: exception UNRECOGNIZED_ID in call AddClientEventToNotificationGroup param #2 '-1716569168'
{'Airport': 'KCLT', 'Requested assistance services at': 'Gate F 80', 'Requested parking services to': 'Gate F 80', 'User Pos': (35.20199897440113, -81.06724781013075, 2818.16 m, 2623.47 m, 355.0647369011257, -0.029166441625976522, 0.001745329238474369, 0.0006527372341260218, 3.18211187210083, 0.0)}
emulateMenu_MSFS
emulateMenu_MSFS CHOICE 0
channel.balance =  -1
Error: exception UNRECOGNIZED_ID in call RemoveClientEvent param #2 '-1716569168'
{'Airport': 'KCLT', 'Requested assistance services at': 'Gate F 80', 'Requested parking services to': 'Gate F 80', 'User Pos': (35.20465229462634, -81.0674818868967, 2810.37 m, 2628.26 m, 355.07503545635706, -0.029752148447255086, 0.001745329238474369, -0.00019618439453051242, 3.18211187210083, 0.0)}
Requested parking services to Concourse D|Gate 5
Marshaller distance readout disabled by user preferences
emulateText_MSFS [GSX] Handling by American Airlines 2.0
emulateText_MSFS [GSX] Safedock© system activated at the requested parking 6

[Pirateinparadise]

Well, I can now confirm that this is related to selecting the destination gate while in the air (below 10,000' and <250 kts). If I wait until I am on the ground to select the gate, everything works fine. If I select the gate before landing, all GSX services disappear when I turn the beacon off.