Description

Disclaimer: This software is designed to work with traffic packages for Microsoft Flight Simulator by indexing installed models and generating configuration files.
Users are solely responsible for ensuring that their use of third-party content complies with the respective terms of use.
Any misuse of the tool, including modifications intended to enable such violations, falls entirely under the user's responsibility.
The developer does not endorse or encourage any use that breaches third-party conditions.

Update 2: The basic mechanics are unchanged in MSFS2024, so I'm expecting it to work as intended in the new simulator. Compatibility issues may arise with traffic packages themselves, but I haven't encountered particular problems so far (FSLTL & AIG in particular) except missing landing gears and skidding tires. Please report any inconvenience.

Update: Extended internal database with complete set of ICAO types (2,737) and special designators.

Perfect Model Matching is a VMR generator for vPilot and VATSIM, evolution of the original Model Matching Magic by mccarl1978.

Model matching - unfortunately - can't really be perfect. The idea of this project, however, is to offer the most plug-and-play solution possible, providing satisfying results with minimal interaction.

Key Features:

A fully customizable internal database with over 2700 aircraft types for a broader range of accurate matches.
Smart recognition of airline callsigns and aircraft models, with the ability to add custom search keywords.
Support for alternative airline callsigns, reducing errors when matching with other pilots.
Preferences for model selection.
User manual.

Compatibility:
Perfect Model Matching works best with traffic packages and is specifically designed to fill the gap for general aviation and classic aircraft models. It has been tested with:

Alpha India Group (AIG)
FSLTL – FS Live Traffic Liveries
GAmod
FS Traffic

Installation & Use:
Extract the .zip folder and run the executable.
Once ready, generate the matching rules, which will be saved as PerfectModelMatching.vmr in the same folder.
Move the .vmr file to your desired location and add it in vPilot by navigating to: Settings > Model Matching (MSFS) > Custom Rules > Add Custom Rule Set(s)...

Comments(109)

AnderK

6 days ago

Hello!

Thanks a lot for the project.
I am using full installations of FSLTL and AIG with it.

I have a concern though, is it recommended to enable "Generics Priority" before generating the VMR file?
I only play on VATSIM so don't know what is the best option, I cross around some aircraft like Wizz and TAP Air Portugal with white liveries, what would be the issue with it? there's also in some cases where a different aircraft popped up, like it was originally supposed to be a KLM MD-11 and it was an A300 instead.
Also, do you just recommend to simply install it as: Scan Community > Generate VMR, OR, do I need to edit something else?

Ema8_88Author

5 days ago

The thing with 'Generics Priority' works this way: do you prefer the right model (or the most similar) over the right airline colors? (ex: someones flies an A320 with ryanair. do you want to see a blank A320 or a ryanair B738?). If you want the right aircraft, go with priority checked. If you prefer the airline colors, leave it unchecked.

You could, and should, check what you're loading in your vmr before generating it. Have a look on what models your scand finds, edit in the spreadsheet any mistakes or missing ICAO/airline callsign and MOST IMPORTANTLY, remove all the non FSLTL/AIG/other traffic package models (i.e., the addons liveries) that will affect your simulator performances.

AnderK

3 days ago

Ok Thanks for the clarification!
I been using it without "Generics Priority" checked and I still see white liveries on Simple Airlines, came across to another TAP, BAW and AFR A320s with blank liveries.

Is it a way to just show the default Paint from the Airline instead of showing white?

Ema8_88Author

3 days ago

Do me a favour:

- make sure you have just PMM vmr in vpilot or at least no other rules before it
- open your current vmr file with a text editor and look for these entries:

ModelMatchRule CallsignPrefix="TAP" TypeCode="A320" ModelName="
ModelMatchRule CallsignPrefix="BAW" TypeCode="A320" ModelName="
ModelMatchRule CallsignPrefix="AFR" TypeCode="A320" ModelName="

AnderK

3 days ago

Hello,
Yes I'm using one single VMR for all my model matching using your Generator. all those text entries exist, I just checked them.

I don't care seeing a a special livery or anything fancy from the current airplane, I just want to see the correct airline colors and avoid blank liveries or different aircraft

Ema8_88Author

2 days ago

I got it: I don't want you to check if those entries are there, but what are the models assigned to each of those keys.

AnderK

2 days ago

This shows for the A320:

Ema8_88Author

2 days ago

you have to remove the brackets to paste the keys, these messages are sanitized of markup language

AnderK

2 days ago

OK sorry, this is for TAP A320:

ModelMatchRule CallsignPrefix="TAP" TypeCode="A320" ModelName="AIGAIM_TAP Air Portugal Airbus A320-200//AIGAIM_TAP Air Portugal Airbus A320-200 - IC//AIGAIM_TAP Air Portugal Airbus A320-200 - White opb Airhub//AIGAIM_TAP Air Portugal Airbus A320-200SL//AIGAIM_TAP Air Portugal Airbus A320-200SL - IC//AIGAIM_TAP Air Portugal Airbus A320-200SL - IC old webtitles//FSLTL A320 TAP Air Portugal"/>
ModelMatchRule CallsignPrefix="TAP" TypeCode="A20N" ModelName="AIGAIM_TAP Air Portugal Airbus A320-200neo//AIGAIM_TAP Air Portugal Airbus A320-200neo - IC//AIGAIM_TAP Air Portugal Airbus A320-200neo - Star Alliance//FSLTL A20N TAP Portugal"/

AnderK

2 days ago

Also another thing, I have AIG and FSLTL, what model matching do you recommend me for Helicopters?

Ema8_88Author

2 days ago

The issue, as you can see from your entries, is not the matching, is the fact that you have a white livery for TAP! If you don't want to see it, disable it from the PMM interface and regenerate the VMR.

My suggestion is to use both AIG and FSLTL, a bit overkill but you get a great coverage.

As per the helicopters, GAmod (2020) could have a couple helicopters in their traffic package. otherwise, you should check for yourself if any traffic package available online have them.

AnderK

1 day ago

Ahh I see it now! so its not a bug. is it a way to disable white liveries at all?,
Also, when I scanned my community based on FSLTL and AIG, theres some models that were excluded, were couple airliners 737s from FSLTL and some turbo props from AIG, should I leave them like that or I can enable them on the VMR file? I only have exluded all the twin and quad engine models from asobo, theyre like 9 of them.

Ema8_88Author

1 day ago

Unfortunately, you have to remove riveries you don't like by hand, as there's no way to know how do they look by their data for the tool.

Models are excluded by default when PMM wasn't able to assign them an ICAO code (ex: B738), because that wasn't configured and wan't deductible by its title. If you want, you can assign the ICAO code manually and untick the exclusion. Edits will be saved for future sessions.

AnderK

about 5 hours ago

Ok perfect! I’ll do that.
One more thing, I got me a Helicopter model matching, in some helicopters it actually shows models and in some other ones it shows a GA airplane. I tested it alone with one single PMM VMR and with no VMR at all (which shows the Heli model without it). Looks like PMM is limiting from displaying the model

Ema8_88Author

about 1 hour ago

It could be different things.

- have you checked your heli models are both not excluded and have icao codes assigned for an helicopter?
- what is the icao code of the vatsim pilot that doesn't get recognized? is it in the database (it should) and marked as helicopter?
- is there a matching key for said icao code in your vmr (it should if the above are ok)?
- lastly, you can always type in vPilot ".aircraft" and see what has been matched for each aircraft in sight, with the matching vmr it used.

Feel free to dm me and send evidence if you need further help.

McOatmeal

18 days ago

I shouldn't have to modify this program to use IVAO models. It doesn't scan the community 2024 folder and hasn't been updated. I have experienced substantial CTD's when trying to exclude stuff from having such a large community folder while using this program lately. Mine is over 1tb. It isn't your job to change your code to make your program worse because IVAO doesn't like Vatsim. Stand up to bullies, update the program to scan the 2024 folder and make it generally more reliable. then absolutely you will have 5/5.

Ema8_88Author

10 days ago

You're really confused about the software functionalities. It does scan whatever you select. If you experienced CTDs it is unrelated to the use with MSFS2020 or 2024, you might have too long folder paths.

I'd also like to point out that this is not my job. You can't dictate how I should manage my relations with anyone. Appreciate my volounteer work with respect.

MSFS 2020MSFS 2024