I'm seeing generic liveries. How do I fix it?

SayIntentions.AI has full model and livery matching, and will automatically utilize any livery packages installed (FSLTL, AIG, FSTraffic, IVAO MTL, etc.)

In all cases, where a "match" can be identified by the SayIntentions AI, we'll use any available livery that we find installed. 

If you're seeing generic liveries instead of the ones from your installed libraries, you should check the following:

1) Make sure the airplane ICAO and airline combo really does have a "match" installed

If you're seeing mostly "correct" liveries, but a handful of generics, it often means your model library is missing the livery needed for that specific Aircraft ICAO + Airline combination. Sometimes adding an additional model library will solve the problem.

2) Make sure the injected traffic was really injected by SayIntentions.AI

In the SayIntentions.AI windows application, click the "Live Map" tab. All of the injected traffic should appear on the map. Confirm there are no red planes.

If you see red airplanes on the traffic map, you have another injector running, and those airplanes may appear as generics, but more importantly, they're not under the control of the SI ATC system. (Note that the injected airplanes might even be coming from the built-in MSFS injector, which should be disabled using these instructions).

3) Re-install your livery libraries

Yes, they do get corrupted, and yes, this really does fix this problem on a regular basis.

4) Add AntiVirus exclusions for your MSFS community folder.

While MSFS might be able to scan your community folder, it's possible your A/V is preventing the SI application itself from scanning that folder, which can cause failures.

By default, the community-folder locations are as follows (though it should be noted that these can be customized and may or may not apply if you have moved them).

• For MSFS 2020 "Microsoft Store Version": C:\Users[YourUsername]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community.
• For MSFS 2020 "Steam Version": C:\Users[YourUsername]\AppData\Roaming\Microsoft Flight Simulator\Packages\Community.
• For MSFS 2024 "Microsoft Store Version": C:\Users[YourUsername]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community.
• For MSFS 2024 "Steam Version": C:\Users[YourUsername]\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community.

5) Confirm you are not using a custom community-folder location

While this shouldn't normally be a problem, we have seen many situations where the SI app is unable to find them if your community folder has been moved to a custom location on your PC.

6) Confirm the model libraries are in the correct community folder

Double-check you've installed the model libraries for the simulator you're using. Often we find people who installed the libraries into the community folder for one sim (e.g. 2020), and then forget that they need to install them into the community folder for the other sim as well.

7) If you've tried all 5 of the above steps....

Open a support ticket on our Discord and the dev team can take a closer look at your issue.