FSDreamTeam forum

Products Support => GSX Support MSFS => Topic started by: Dr.Shadow on August 20, 2024, 07:42:09 pm

Title: Fenix A321 and 319 not shown in the FSDT Installer
Post by: Dr.Shadow on August 20, 2024, 07:42:09 pm
Hi all

After installing the expansion (321 and 319) i cant find both busses in the FSDT Installer for doing the fleg on and off for seated passengers. I just have the a320 there.

I did the installation with the fenix installer.

Did i do something wrong?

Cheers Pascal :D
Title: Re: Fenix A321 and 319 not shown in the FSDT Installer
Post by: fabristunt on August 20, 2024, 08:37:44 pm
It just came out, give FSDT the time to add GSX compatibility!
Title: Re: Fenix A321 and 319 not shown in the FSDT Installer
Post by: blakefb21 on August 28, 2024, 09:53:20 am
So both the 319, and 321 are compatible with seated pax? I'm missing the A321 if so. I've got the 319 and 320.

Title: Re: Fenix A321 and 319 not shown in the FSDT Installer
Post by: pete_auau on August 28, 2024, 01:26:31 pm
So both the 319, and 321 are compatible with seated pax? I'm missing the A321 if so. I've got the 319 and 320.
yes both the 320 and  319  have  seated  pax  still  waiting  for  the  321 option in  the  next update  hopefully
Title: Re: Fenix A321 and 319 not shown in the FSDT Installer
Post by: virtuali on August 28, 2024, 02:31:51 pm
So both the 319, and 321 are compatible with seated pax? I'm missing the A321 if so. I've got the 319 and 320.

If you read the release notes, it's said the A321 will come in a future update, because we need an update from Fenix first, to detect the cabin configuration.
Title: Re: Fenix A321 and 319 not shown in the FSDT Installer
Post by: blakefb21 on August 30, 2024, 06:50:15 am
Oh ok perfect! That’s what I thought, but others made it sound like seat pac was available for both variants. Thank you for specifying! Absolutely love GSX and seated pax.
Title: Re: Fenix A321 and 319 not shown in the FSDT Installer
Post by: PistonPilot on September 12, 2024, 01:48:19 pm
So both the 319, and 321 are compatible with seated pax? I'm missing the A321 if so. I've got the 319 and 320.

If you read the release notes, it's said the A321 will come in a future update, because we need an update from Fenix first, to detect the cabin configuration.

Hi Umberto,

with the latest version I've the problem that with the A321 GSX Pro isn't loading passengers. It starts the refueling as it should but then it stucks and didn't load any passengers or luggage. Is this a problem which results of the missing detection of the cabin configuration and the update which needed to be provided by fenix you were talking about? I just want to understand the problem. When this is the problem I know that I should better load the aircraft via Fenix Tablet and use GSX Pro for pushback after I'm done with everything.

Thanks for helping me out.

Best regards,
Marc
Title: Re: Fenix A321 and 319 not shown in the FSDT Installer
Post by: virtuali on September 13, 2024, 11:28:55 am
with the latest version I've the problem that with the A321 GSX Pro isn't loading passengers. It starts the refueling as it should but then it stucks and didn't load any passengers or luggage.

Cannot reproduce it, works fine here.

Of course they won't show Seated, because we still need to wait for an update from Fenix to add a variable we can check to recognize the dual cabin configuration, but they will board normally, without sitting.
Title: Re: Fenix A321 and 319 not shown in the FSDT Installer
Post by: PistonPilot on September 15, 2024, 10:47:54 pm
with the latest version I've the problem that with the A321 GSX Pro isn't loading passengers. It starts the refueling as it should but then it stucks and didn't load any passengers or luggage.

Cannot reproduce it, works fine here.

Of course they won't show Seated, because we still need to wait for an update from Fenix to add a variable we can check to recognize the dual cabin configuration, but they will board normally, without sitting.

Hi Umberto,

thanks for your fast reply. I didn't know exactly what the fault was but it's workeing again. Didn't know what actually happen that it stopped workeing.

Best regards,
Marc