I am having difficulty seeing liveries downloaded from Flightsimto to appear in MSFS.  I think I know what the problem is but I don't know how to fix it.

In the Community folder, the livery directory of a livery installed using the Fenix Livery Manager contains 4 items- subdirectory MODEL.xxxx, subdirectory TEXTURE.xxxx and the files AIRCRAFT. CFG and LIVERYDATA.JSON.  These work fine.

The livery directory extracted from the *.ZIP downloaded from Flightsimto to be copied to the Community folder has 3 of the 4 items from above; it's missing the LIVERYDATA.JSON file.  This is true for multiple *.ZIP files so I don't think the problem is with the ZIP files.

I would appreciate some direction.

Can you link the exact file?

You just unzip the whole folder into the community folder 

12 hours ago, rick celik said:

You just unzip the whole folder into the community folder 

No, this does not work and I didn't think it would because the naming convention of the unzipped folder does not match the naming convention of liveries installed by the Fenix Livery Manager.  The downloaded zip file is fnx-aircraft-321-JBPRISM-IAE_hD_dU.zip.

12 hours ago, Tuskin38 said:

Can you link the exact file?

I don't understand what you are asking.

Fenix do things differently, don't use them as a model.

Just unzip the whole folder from the download into community, preserving the folder from the zip.

3 hours ago, zachlog said:

No, this does not work and I didn't think it would because the naming convention of the unzipped folder does not match the naming convention of liveries installed by the Fenix Livery Manager.  The downloaded zip file is fnx-aircraft-321-JBPRISM-IAE_hD_dU.zip.

As mentioned above, unzip and preserve whole folder. So in the community folder there should be a folder called fnx-aircraft-321-JBPRISM-IAE_hD_dU

It's not like every livery you download on Flightsim.to comes with an instruction how to install it...

1 hour ago, rick celik said:

As mentioned above, unzip and preserve whole folder. So in the community folder there should be a folder called fnx-aircraft-321-JBPRISM-IAE_hD_dU

This is what I did earlier today and it worked for this one and two others.  The problem was that I was trying to fit the installation of a 3rd party livery into the Fenix Livery Manager directory structure until I saw Keith's post above that Fenix does things differently and that's when the light bulb went on.

Many thanks.

4 hours ago, keithb77 said:

Fenix do things differently, don't use them as a model.

Just unzip the whole folder from the download into community, preserving the folder from the zip.

Letting me know that Fenix does things differently fixed it for me.....thanks !

8 hours ago, zachlog said:

No, this does not work and I didn't think it would because the naming convention of the unzipped folder does not match the naming convention of liveries installed by the Fenix Livery Manager

Liveries installed by the Fenix livery installer are different than those that you download and add manually and the folder naming WILL be different. 

 I just downloaded that same file, and dropped the fnx-aircraft-321-JBPRISM-IAE folder within the zip into my community folder and it works fine.