I was wondering if there is a way to improve the model matching.

I have multiple AIG airlines packages installed as well as the FSTL base models and use them with the inbuilt Live-Traffic feature. There are a few airlines that MSFS has trouble assigning either correct models or liveries for.

For example CLH (Cityline Lufthansa). The models being used are correct, yet the liveries are all over the place. They were CRJ's alright but I saw a Kenya Airways, SAS, Nordica. It was all over the place. The only thing I didn't see was an actual Lufthansa livery.

Or an Uzbekistan Airlines 787 that showed up in a Air Canada livery

Edited October 3, 20223 yr by Farlis

Very good question. According to their discord, they are working on improvements of the injector on behalf of fallback solutions. And they might add the one or the other option to configure it. 

Basically I see the same: although I have installed everything from AIG, especially in Asia a lot of planes are white. I guess, the fallback works kinda ok for models missing (but according to your report with some issues regarding the selection of the repaint), but does not really work (at all) for missing repaints. 

Then, this tool was released only some days ago, clearly it needs to mature a little bit 😉 

It's not about the FSTL injector though. It's about the model matching that MSFS does when you use the Live-Traffic option that comes with the sim togehter with fitting models installed from both AIG and FSTL. Currently I prefer to use that, as no injector other than the insanely pricey PSXT will make the AI fly proper procedures.

That matching was already wonky with only the AIG packages installed. I had hoped that giving the sim more options to look for matching models would improve the assignements.

But some Airlines remain illusive.

 

(That Usbekistan Airlines was my fault though. Hadn't installed the corresponding AIG package yet).

Edited October 3, 20223 yr by Farlis

49 minutes ago, Farlis said:

It's not about the FSTL injector though. It's about the model matching that MSFS does when you use the Live-Traffic option that comes with the sim togehter with fitting models installed from both AIG and FSTL. Currently I prefer to use that, as no injector other than the insanely pricey PSXT will make the AI fly proper procedures.

That matching was already wonky with only the AIG packages installed. I had hoped that giving the sim more options to look for matching models would improve the assignements.

But some Airlines remain illusive.

 

(That Usbekistan Airlines was my fault though. Hadn't installed the corresponding AIG package yet).

Agree, I have been doing the same and have seen the same issues with some wrong assigned models or liveries and was wondering wether MSFS has a modelmatching file like other AI tools has...

Ok..I found this tool but I don't use VATSIM not familiar with the vpilot setup but I will give it a try this afternoon just to see if it will improve MSFS AI modelmatching for the sim.

https://flightsim.to/file/23534/aig-traffic-model-matching-for-msfs-2020

16 minutes ago, adino said:

I found this tool

 

I believe this tool is meant only for users of vPilot, the VATSIM pilot client. It almost certainly does nothing for model matching internally for MSFS AI.

 

25 minutes ago, jrw4 said:

 

I believe this tool is meant only for users of vPilot, the VATSIM pilot client. It almost certainly does nothing for model matching internally for MSFS AI.

 

ok, thnx for the headsup.

7 hours ago, Farlis said:

For example CLH (Cityline Lufthansa). The models being used are correct, yet the liveries are all over the place. They were CRJ's alright but I saw a Kenya Airways, SAS, Nordica. It was all over the place. The only thing I didn't see was an actual Lufthansa livery.

I found the cause, Lufthansa Cityline's ICAO Airline code in the aircraft.cfg file is 'DLHX' instead of 'CLH'. I've asked about it on the AIG Discord.

Edit: Can't be helped, CLH is included under the Lufthansa regional package, and they can't separate the icao codes of the ones only operated by CLH. The entire thing is automated.

You could manually edit the CLH aircraft's aircraft.cfg file with a text editor and change any livery that is opb CLH ones to use CLH instead of DLHX. But any time the flight plan is updated or you run a OCI Verify, you'd have to edit them all back.

Edited October 3, 20223 yr by Tuskin38

 What I have done was copy some of those folders out of the OCI folder and into my own AI AIrcraft folder where I can edit them to what they should be and it doesn't interfere with my OCI install. Similar to in the US where ASAX, UALX, AALX, DALX would be their actual icao code of QXE, SKW, EDV, ENY etc. This issue though and that is entirely why AIG did it the way they did is this introduces not knowing the difference between flights operated by SKW for Alaska, Delta, American, or United.
 Another win for PSXT as it doesn't have this issue.😉

Edited October 3, 20223 yr by Dave_YVR

8 hours ago, Farlis said:

Currently I prefer to use that, as no injector other than the insanely pricey PSXT will make the AI fly proper procedures..

Yes flying the proper procedures, with the right livery, in real time comes with a cost. However, I would not call 3 beers a month or once to the movies a month, "insanely priced"  😉

And don't forget that you get  my part of the system  PSXT, for free.

 

 

Edited October 3, 20223 yr by kiek

2 hours ago, kiek said:

However, I would not call 3 beers a month or once to the movies a month, "insanely priced" 

I would call 180€ per year extremely pricey.

3 minutes ago, Farlis said:

I would call 180€ per year extremely pricey.

Worth every dime!

4 minutes ago, Adrian123 said:

Worth every dime!

Not unless the only way to make this work is to completely take over every positional information of the AI models. I would prefer if one could have the inbuilt ATC learn how to read this and transfer it into commands to the AI instead of having no radio chatter at all, without tuning into the real world stations. Especially since those are unavailable to the public in most countries in the EU.

 

But back to my question: So the problem is that the AI packages come with the wrong airlinecodes in their packages. That's unfortunate and I hope that @Kaiii3 and people at AIG find a way to change that in the future.

Edited October 3, 20223 yr by Farlis

13 minutes ago, Farlis said:

So the problem is that the AI packages come with the wrong airlinecodes in their packages.

Only for the regional airlines that operate for multiple things.

Even if they did, there's really no way to make it match properly. for example Republic Airways, all their flights no matter what airline they're operating for (Delta, United or American), all use the airline code RPA. So you could end up seeing a Delta Connection livery on a United Express flight.

1 hour ago, Farlis said:

I would call 180€ per year extremely pricey.

 $90/year, you don't have to get the Professional Edition. Even just to try it for a month and see. Real spacing on final and take off, traffic exiting the runway at the actual place and speed that they do irl. You won't see go arounds unless they ACTUALLY went around in real life!