See page 99 manual:" Depending on the airplane used, 3rd party liveries might be distributed in package names different than the ones used by the official liveries. Some airplanes like PMDG, encourage distribution through a special archive (.PTP) which usually prevents the problem of having liveries spread across multiple packages, but not all airplanes work like this, so you might find liveries in packages named in many ways.
This might be a problem for the FSDT Installer, because it doesn’t scan all folders in your Community, parsing all aircraft.cfg trying to recognize a supported airplane, it would be very slow. Instead, if will only look inside a few folders that are known to be used to contain add-on liveries for the supported airplanes.
For example, Fenix A320 liveries are searched in all packages with a name starting with “fnx-aircraft-320” or “fnx_320_”, Maddog X liveries are only searched in packages with a name starting with “lsh-maddogx-aircraft” or “lsh-maddogx-livery”, iniBuilds A300 liveries are searched in packages with a name starting with “inibuilds-aircraft-a300-600“, “inibuilds aircraft-a306r-pw “ or “inibuilds-a300”and so on.If you have an unofficial livery that comes in a package named not according
to these standards, it won’t be detected, resulting in Pink texture, because the airplane is referencing the default exterior model (which has been patched to add Seated Passengers), but the texture Fallbacks hasn’t been added to the TEXTURE.CFG of that livery, because its package was ignored because of its name. The solution in this case is to rename the package in the Community as expected.
I modified it as indicated in the manual, but it didn't work. In fact, the configuration no longer reads or modifies the aircraft's tetxtuer.cfg file. I'd like to know what else I need to modify.
