Set up vPilot model matching in MSFS with the right model library and VMR rules, then fix invisible aircraft, wrong liveries and duplicate traffic.
To set up vPilot model matching in Microsoft Flight Simulator, install an MSFS-compatible AI aircraft model library, add a compatible .vmr rule set in vPilot’s Model Matching settings, put specific rules above broad fallbacks, restart the simulator, and disable MSFS-generated traffic so only VATSIM aircraft are injected.
If the client itself is not configured yet, complete our VATSIM and vPilot connection setup first. Model matching cannot correct network, audio, authentication or callsign problems.
What does vPilot model matching require?
vPilot model matching requires two separate components: the visual aircraft models installed in MSFS and rules telling vPilot which model to use. The model library supplies the aircraft and textures; a VMR file maps a remote pilot’s aircraft type and callsign prefix to an exact installed model title.
Installing only the VMR file is a common mistake. It contains no aircraft, so every rule referencing an absent model will fail. Stock MSFS aircraft can provide basic fallbacks, but a dedicated, performance-friendly AI library gives much better type and airline coverage; our guide can help you choose a suitable MSFS AI model package.
For example, FSLTL users need the Base Models package for model matching. Its separate traffic injector is not required while using vPilot and should not run at the same time, because vPilot is already injecting the VATSIM traffic.
How do I configure vPilot model matching?
The reliable setup order is models first, matching rules second, and traffic settings last.
- Close MSFS and install the model library. Choose a package compatible with your edition of MSFS. Confirm that it went into the active Packages location used by that installation; a Community package should have files such as
manifest.jsonandlayout.jsonat its package root, not inside an accidental extra folder level. - Obtain the matching VMR rule set. Use a VMR intended for the installed model library and, where applicable, the same package release. A stale VMR can reference titles that have been renamed or removed.
- Store the VMR somewhere permanent. The
.vmrfile does not need to be placed in the Community folder. Keep it in a stable folder and do not move or rename it after adding it to vPilot. - Add it in vPilot. Open vPilot’s settings, select the Model Matching section and add the file as a custom rule set. Confirm that the rule set remains listed and enabled after saving the settings.
- Prioritise the rules. Put airline-and-aircraft-specific rules above type-only or generic fallback sets. Avoid loading duplicate VMR files that target the same model library.
- Disable competing MSFS traffic. Turn off live, AI or offline traffic and MSFS multiplayer aircraft, then set the simulator’s parked or ground-aircraft density to zero. The exact labels differ between MSFS 2020 and MSFS 2024.
- Restart and test. Restart MSFS after installing models and restart vPilot after changing rule files. Load at a parking stand, wait for vPilot to report that the simulator is connected, and then connect to VATSIM.
Which model matching rules should come first?
Put the narrowest rules first and broad fallback rules last, because an earlier valid match can prevent a more appropriate livery from being selected.
| Rule type | What it matches | Recommended position |
|---|---|---|
| Callsign prefix and aircraft type | A particular airline and ICAO type, such as a specific operator’s B738 | First |
| Aircraft type only | Any operator using that ICAO type | After airline-specific rules |
| Generic or family fallback | Traffic for which no exact model exists | Last |
A single well-maintained VMR is usually safer than several overlapping files. More rules do not automatically mean better coverage: two packages may define different models for the same airline and type, leaving priority rather than accuracy to decide the result.
Can I create my own VMR rule?
You can create a custom VMR when an installed livery or aircraft is missing from the supplied rules. A basic entry looks like <ModelMatchRule CallsignPrefix="ABC" TypeCode="B738" ModelName="exact aircraft.cfg title" /> inside a <ModelMatchRuleSet> root element.
ModelName must match the model’s title= entry exactly; the folder name or livery name shown in the aircraft selector may be different. Save the file as genuine XML with a .vmr extension, not the easily missed .vmr.txt, and keep custom rules outside the add-on folder so an update does not overwrite them.
Why are VATSIM aircraft invisible or showing the wrong model?
Most vPilot model matching failures come from a missing model, an obsolete VMR reference or another traffic injector running alongside vPilot.
| Symptom | Likely cause and fix |
|---|---|
| No VATSIM aircraft appear | First confirm that other pilots are actually within range and that vPilot reports both simulator and network connections. If the simulator connection is missing, follow our steps to repair the MSFS SimConnect link. |
| A model-not-found or aircraft-creation error appears | The VMR’s ModelName is not available to MSFS. Check the active Community folder, package structure and VMR version, then restart the simulator. |
| A generic aircraft appears | No exact rule or installed model matched the remote pilot’s ICAO type. This is a working fallback, not necessarily a fault; remote pilots can also supply missing or non-standard type codes. |
| The type is right but the airline is wrong | A type-only rule may be taking priority, the callsign prefix may not represent the painted operator, or the correct livery is absent. Reorder overlapping rule sets and verify that the referenced model exists. |
| Aircraft appear twice | MSFS live traffic, multiplayer traffic or another injector is still active. Disable those sources and let vPilot inject VATSIM traffic by itself. |
| Aircraft are pink, textureless or partly invisible | This normally indicates missing textures or another model-library dependency rather than a bad matching rule. Repair or reinstall the affected model package. |
| Frame rate drops heavily at busy airports | Use AI-optimised models rather than complex flyable aircraft and reduce the number of remote aircraft vPilot is allowed to inject. |
How can I tell whether model matching is working?
Model matching is working when remote VATSIM aircraft appear without creation errors and show a plausible type or fallback model. Test near active traffic rather than at an empty airport, and remember that model matching controls other pilots’ aircraft, not your own.
An exact airline livery is not guaranteed. The library may lack that operator, a callsign may represent a charter or codeshare, or the remote pilot may have supplied an incorrect aircraft designator. A sensible generic model is preferable to an invisible aircraft.
Does vPilot model matching work in MSFS 2024?
Yes, the same vPilot and VMR principle works with MSFS 2020 and MSFS 2024 on Windows PC, but the model package must support the installed simulator and be placed in its active Packages location. Do not assume that every MSFS 2020 traffic model will work correctly in MSFS 2024.
vPilot model matching is a PC setup. The Xbox and PlayStation editions cannot run the Windows vPilot client or load PC Community-folder model packages.