Seated passengers textures

[AndyCYXU]

you need to make sure that the livery in the community folder follows the fenix standards. Named as follows fnx-aircraft-320-xxxx. If you have a livery folder named like FNX_320_IAE_VLGMVN as I had gsx does not recognise it as a livery. I changed the folders name to fnx-aircraft-320-VLGMVN and voila.
If you do not see the created by gsx file inside the model folder it just means that gsx has created nothing. But it will work anyways.
If you do not have a model folder GSX will write an entry in the aircraft.cfg and create that model folder.
So 1 : make sure to have the airline icao entry in the aircraft.cfg
and 2. that the folder name in the community folder follows the fenix standards

I just think that this is something that the developers should explain clearly. It took me 2 hours to figure out the GSX logic on this.

Thanks for that it seems to work well for the most part..

I use addon-linker and renamed all my livery folders to fnx-aircraft-320-xxxx run the installer check uncheck seated plane and out of 19 liveries i have 15 worked great and I saw GSX created model.XXX and some files in there.. all the liveries had to be activated of course so that there are links in community folder.

so 4 did not work not sure why tried finding what was special about these 4.. idk just these did not work

thanks for the tip ! 

[20NailsPilot]

you need to make sure that the livery in the community folder follows the fenix standards. Named as follows fnx-aircraft-320-xxxx. If you have a livery folder named like FNX_320_IAE_VLGMVN as I had gsx does not recognise it as a livery. I changed the folders name to fnx-aircraft-320-VLGMVN and voila.
If you do not see the created by gsx file inside the model folder it just means that gsx has created nothing. But it will work anyways.
If you do not have a model folder GSX will write an entry in the aircraft.cfg and create that model folder.
So 1 : make sure to have the airline icao entry in the aircraft.cfg
and 2. that the folder name in the community folder follows the fenix standards

I just think that this is something that the developers should explain clearly. It took me 2 hours to figure out the GSX logic on this.

I'm just about to give up... Have a 3d party livery. As it's a 3d party livery, is installed directly into the comunity folder (no addon linker). Just renamed the folder to fnx-aircraft-320-IAEFENIX (Fenix is the VA name). Also checked the aircraft.cfg contains the icao_airline line as shown below:
[VERSION]
major = 1
minor = 0

[VARIATION]
base_container = "..\FNX_320_IAE"

[FLTSIM.0]
title = "FNX_320_IAE_FENIX_2024"
texture = "FENIX"
model = ""
ui_variation = "FENIX"
atc_id = "EC-FNX"
atc_airline = "FENIX"
icao_airline = "FNX"

fnx_selcal_code = FNX
fnx_wifi_antenna_type = 0

// rest of the file omitted for lengh reasons //
Just went to GSX - Options and unchecked and checked the Seated Passengers option, but the model folder is not being created.

Is there anything I'm missing??

[virtuali]

// rest of the file omitted for lengh reasons //

And that's what you should never do, because the aircraft.cfg might have a problem in other parts you don't think are important, that's why you should never post a file copied in a post but, instead, using the forum ATTACH function to add the actual file, so I could look at the whole file, unchanged.

[eu204]

Hi all. I discovered another problem. When you turn on the passenger checkbox on the Phoenix 320, all visual effects disappear (warm air from the engines, APU and contrail). Only a complete reinstallation of Phoenix will help. Then, as soon as you check the box, the effects disappear again. Has anyone encountered such a problem? Thanks in advance

[Art69]

Hi all. I discovered another problem. When you turn on the passenger checkbox on the Phoenix 320, all visual effects disappear (warm air from the engines, APU and contrail). Only a complete reinstallation of Phoenix will help. Then, as soon as you check the box, the effects disappear again. Has anyone encountered such a problem? Thanks in advance

Sorry... what aircraft is Phoenix 320?    Never heard of it.

[karank]

Adding the steps I took to make it work:

Note (1): If you haven't used the Fenix Livery Manager before, you can create the necessary folder structure by downloading any livery from the manager. This will create a folder called "fnx-aircraft-320-liveries" in your MSFS Community folder.

Note(2): I use MSFS Addon Linker and store my liveries on a different drive. GSX doesn't recognise this location even though it's active in the Addon Linker so for the moment, I've moved all my flightsim.to liveries from the custom directory to the default MSFS Community folder.

1. Download the livery you like from flightsim.to.
2. In the downloaded zip file, browse until you reach the folder called 'FNX_320_IAE_xxx'. In my case, it was 'FNX_320_IAE_VTTTM'. Copy this folder to the following directory: Community\fnx-aircraft-320-liveries\SimObjects\Airplanes.
3. Run FSDT Universal Installer and click on 'Config' for GSX.
4. Enable 'Fenix A320 B2'.
5. You should see that GSX recognises the livery and adds a 'model' folder into this particular livery directory.
6. If this occurs, congratulations, everything should work as intended and you can now close the FSDT Universal Installer.

IF GSX did not create a 'model' folder in the livery folder, chances are the ICAO airline in the 'aircraft.cfg' of the livery isn't recognised by GSX. In my case, this happened.

To resolve it, I changed the ICAO airline from 'VTI' to a more common airline such as 'AIC' in the 'aircraft.cfg' file and re-launched FSDT Universal Installer. This time GSX recognised the livery and added the 'model' folder.

So, it appears that if the ICAO airline in the 'aircraft.cfg' isn't known to GSX, it doesn't recognise that particular livery folder at all.

Hope this helps. 

[virtuali]

So, it appears that if the ICAO airline in the 'aircraft.cfg' isn't known to GSX, it doesn't recognise that particular livery folder at all.

That's normal, although GSX tries to recognize the airline even from the atc_airline or even the Title itself, but this heuristic is not as reliable as a proper airline ICAO code, because there's only so many way we can deal with all the creative ways airplanes or their airline are named.

So yes, best to have the icao_airline line present with the correct code, otherwise the Crew uniform will be generic.

[karank]

So, it appears that if the ICAO airline in the 'aircraft.cfg' isn't known to GSX, it doesn't recognise that particular livery folder at all.

That's normal, although GSX tries to recognize the airline even from the atc_airline or even the Title itself, but this heuristic is not as reliable as a proper airline ICAO code, because there's only so many way we can deal with all the creative ways airplanes or their airline are named.

So yes, best to have the icao_airline line present with the correct code, otherwise the Crew uniform will be generic.

Thanks, the code for the airline was correct in the livery aircraft.cfg. 'VTI' (Vistara) is an Indian Carrier but GSX does not recognise 'VTI' so it never created the adequate folder with its modified files. When changing it to 'AIC' (Air India) which is in GSX airline database, GSX immediately recognised the livery but of course the crew weren't in VTI uniform.

I also didn't find any generic textures GSX falls back to, if the airline isn't recognised, the model is not modified and I get pink textures. For the moment, I've modified the aircraft.cfg of liveries that GSX does not recognise to more known carriers. That resolves the pink texture issue (albeit with wrong crew uniforms) until the GSX airline database is updated or a generic texture is available.