Hello everyone,

I took some time to create multiple .vmr files using JukiModelMatcher (Flightsim.to download) to enhance the VATSIM Model Matching experience.
In the past, I saw many generic airliners or blank FSLTL planes taxing around the airports. Therefore, I wrote some custom .vmr files to significantly reduce the amount of mismatches.

Installation/How does it work?

Obviously, the FSLTL base pack is required. You can download it via the FlyByWire Installer.
In the file you will find several files. Extract them and put it in a folder of your choice. Thereafter, add them to your Custom Model matching rules. As V-Pilot checks the .vmr files in order, make sure to put the blank liveries to the bottom.

V-Pilot will use the .vmr to find the best match using the algorithm (Quote):
1. Look for an exact CallsignPrefix or Callsign match, plus an exact TypeCode match, ignoring any rules that don't specify a CallsignPrefix or Callsign.
2. Look for an exact CallsignPrefix or Callsign match, plus a TypeCode match for a similar aircraft type, ignoring any rules that don't specify a CallsignPrefix or Callsign.
3. Look for an exact TypeCode match, ignoring any rules that specify a CallsignPrefix or Callsign.
4. Look for a TypeCode match for a similar aircraft type, ignoring any rules that specify a CallsignPrefix or Callsign.

In the folder you will find the following .vmr files:

FSLTL_standard_no_blanks.vmr

In this file, there are only those FSTL aircraft with the exact Airline and Aircraft ICAO, giving the best result based on rule #1. This should be the primary Model Matching rule.

FSLTL_other_aircraft.vmr
A copy of the file above, but missing models (e.g. MD82) will be shown as a similar Aircraft (e.g. CRJ700) of the same Airline. There are not that much aircraft yet, as I keep improving it whilest flying online and detecting a missing aircraft, but you can do it on your own. Just open the file with a text editor, write yourself a comment on the top to know what you actually replaced (e.g. ).
Execute a search and replace with the following argument: Search: TypeCode="CR7" Replace: TypeCode="MD82". Make sure to use the exact form, not a shorten one, otherwise you will destroy the link to the model aswell!

FSLTL_VAs.vmr

Similar to the other_aircaft.vmr there are flying some fictional airlines on VATSIM, they often do not have publicly available liveries, or you do not want to download them due to disk space. Therefore, they are most likely to be shown as generic airliners. With this file, you can show them as real world airlines instead. E.g. around EDDL we got the MTQ VA by our Subdivision. As I do not have the Liveries, they shall be shown as EWG. Therefore, I commented and replaced: CallsignPrefix="EWG" by: CallsignPrefix="CFG". Note: I don't know that many VAs, therefore there are only a few replaced. You can edit this file on your own, to match VAs you know.

FSLTL_blank_liveries.vmr
This VMR is for the blank FSTL liveries, in case there is e.g. a Nxxxxx B737-800 flying around, and you want them to be shown likewise, instead of a generic A20N.

MSFS_GenericGA_Premium_Deluxe.vmr
A .vmr including all MSFS planes from the premium Deluxe version.

MSFS_GenericGA_Standard
Displaying even Premium Deluxe planes as Standard models, so you can see them as a similar aircraft instead of an A320. Please tell me, if there are bugs in this file, where I missed replacing a model.

EC135_HeliModelMatching.vmr
Helis! EC135 Freeware required

Note/Disclaimer:
Using these .vmr you should get most aircraft shown properly. As I also use other sources (AIG) and other liveries there might be many missing aircraft at the "FSLTL_other_aircraft.vmr", because for me it is shown correctly.  By pressing .aircraft (second Screenshot) in your V-Pilot you can see why a model is shown the way it is and what ruleset has been used. This way you can update those files according to your preferences. Just go to the most fitting file (e.g. missing Aircraft ICAO), edit the .vmr as mantioned above, save it and reload the Model Matching rules at your V-pilot (.aircraft interface). You will not even need to disconnect.

I hope to help you, enhancing your VATSIM experience.
Best wishes,
MasterKill95