Been using psxt with msfs 2020 and 2024 with no problems until recently. Suddenly, msfs 2020 says "no liveries found" or "too many liveries to create".  Still works fine in msfs 2024.  Read several threads in regard to this issue and cannot find a solution. Any ideas to get this working again in msfs 2020?

If you use Automatic scan but you do not have AIG, FSLTL or JustFlight packages installed (with their default names) you have to switch off Automatic and define lfolder parameters with the full name to the folder with your ai aircraft. See the Manual.

Or maybe you have forgotten to check Automatic?

Btw, PSXT in MSFS 2020 and MSFS 2024 work exactly the same wrt liveries. So what you see looks strange...

Edited April 17, 20251 yr by kiek

I have aig installed. Yep all worked great until a day or 2 ago. Not sure what I’ve done to break 2020. Working good still in 2024.

4 hours ago, SetSpeed said:

I have aig installed. Yep all worked great until a day or 2 ago. Not sure what I’ve done to break 2020. Working good still in 2024.

Well what changed is that in Automatic mode PSXT now only looks for the AI packages AIG, FSLTL and FSTraffic (JustFlight). Before it also looked in the Community folder. I have removed the latter because there may be user-flyable aircraft in the Community folder that should not be picked up by PSXT...

Another difference may be that in MSFS 2020 it is looking for the folder aig-aitraffic-oci-beta while in MSFS2024 it is looking for aig-aitraffic-oci
Pls check that

Edited April 17, 20251 yr by kiek

Hey kiek.

AIG admin here.

I think you have misunderstood something.

MSFS2020 is also "aig-aitraffic-oci" now, and has been for some time. So exactly the same as MSFS2024.

The change was made by the developer in late October / early November 2024, so even before 2024.  It happened when the AIG Manager went out of beta for 2020.

The issue now is that many users of 2020, still uses the version of the folder with "-beta" at the end, but not everyone, and most who uses 2024, have the folder-name without the "-beta".
When a user is either updating from 2020 to 2024 or installs for 2024 from scratch, the folder will be "aig-aitraffic-oci". And it's the same for 2020. If a user installs for 2020, it will be "aig-aitraffic-oci" too now, and not "aig-aitraffic-oci-beta".

Also, is a user moves the "aig-aitraffic-oci-beta" from 2020 to make it compatible with 2025, it is renamed automatically to "aig-aitraffic-oci". And if not, then the user is required to do so manually.

Being a 2020 user myself, I have "aig-aitraffic-oci" and it works perfectly.

So my request would be if you could make it so PSXT, when looking in the 2020 community-folder, it is also looking for "aig-aitraffic-oci" too.

10 hours ago, johanfrc1 said:

So my request would be if you could make it so PSXT, when looking in the 2020 community-folder, it is also looking for "aig-aitraffic-oci" too.

 

Thank you for that information. I will let PSXT look for both versions in 2020, then it will be solved

 No need to add the Community folder.

 

EDIT @johanfrc1

Well, I moved via the official route to MSFS2024, using both sims. The AIG folder in 2020 still is named  with the -beta. Also the AIGTech manager is not complaining about that or changing it to oci only. Can I change that folder manually to the oci version without problems?

 

Edited April 19, 20251 yr by kiek

On 4/19/2025 at 6:59 AM, kiek said:

 

Thank you for that information. I will let PSXT look for both versions in 2020, then it will be solved

 No need to add the Community folder.

 

EDIT @johanfrc1

Well, I moved via the official route to MSFS2024, using both sims. The AIG folder in 2020 still is named  with the -beta. Also the AIGTech manager is not complaining about that or changing it to oci only. Can I change that folder manually to the oci version without problems?

 

Yes. It works fine for me, using no "-beta" in the folder name.