Install VATSIM model-matching liveries in MSFS 2020 correctly, with Community folder placement, vPilot VMR setup and common fixes.
To install VATSIM model-matching liveries in Microsoft Flight Simulator 2020 on PC, extract the aircraft model packages into the active Community folder, then add their supplied .vmr rule files in vPilot under Model Matching. Restart MSFS and vPilot, confirm the rules load without errors, and disable only duplicate or conflicting rule sets.
What files are required for VATSIM model matching?
Working model matching requires both the aircraft models and rules telling vPilot when to display them.
| Component | Location | Purpose |
|---|---|---|
| Aircraft models and liveries | Active MSFS 2020 Community folder | Provides the aircraft shapes, textures and simulator model titles. |
.vmr rule file | Any permanent folder outside the Community folder | Maps aircraft type codes and airline callsigns to installed model titles. |
vPilot does not download liveries from VATSIM. It reads the aircraft type and operator information received from the network, checks the loaded VMR rules, and asks MSFS 2020 to display the selected installed model. A download containing only VMR files is therefore not a complete model pack.
How do I install the models and VMR files?
Install the simulator packages first and load the matching rules into vPilot afterwards.
- Close MSFS and vPilot. Adding models while the simulator is running can leave them unavailable until the next restart.
- Find the active Community folder. Its location varies between Microsoft Store, Steam and custom installations. If there is any doubt, follow our MSFS 2020 Community-folder and package-root instructions rather than copying files into a guessed location.
- Extract the model package. Do not leave it inside a ZIP or RAR archive. The actual package root should contain files such as
manifest.jsonandlayout.json. Some downloads contain several separate package folders; copy each required folder without merging their contents. - Use the supplied installer when required. If the package has its own installer, select MSFS 2020 and confirm that it targets the active packages location. Do not then install a second manual copy.
- Store the VMR files somewhere permanent. A folder under Documents is suitable. VMR files do not need to be in the Community folder, but moving or renaming them later can break vPilot's saved paths.
- Add the rules to vPilot. Open vPilot Settings, select Model Matching, use the Custom Rules or Add control, and choose every required
.vmrfile. Keep multiple files in the order supplied with the package. - Check rule priority. Put specialised rules ahead of broad fallback rules when one must take precedence. Remove or disable old copies of the same rule set, but retain complementary files required by the model pack.
- Restart and check the message log. Start MSFS 2020, load into an airport, open vPilot and confirm that no missing-model or invalid-rule messages appear. Turn off simulator-generated AI, live and multiplayer aircraft to prevent duplicate traffic; our full vPilot and VATSIM connection setup covers the remaining client and traffic settings.
Can ordinary MSFS liveries be used for VATSIM model matching?
Ordinary flyable-aircraft liveries can sometimes be referenced by a VMR file, but installing them alone does not make vPilot use them automatically.
The rule must call the exact simulator model title registered by that livery, not its folder name or visible aircraft-selector name. Flyable aircraft can also use considerably more resources than purpose-built traffic models, particularly at a busy airport. Use our standard MSFS livery installation procedure if the paint is intended mainly for your own aircraft rather than network traffic.
Why are VATSIM aircraft white or showing the wrong airline?
White, generic or incorrect aircraft usually indicate a missing dependency, an unmatched callsign or type code, or a VMR file that references models not installed on the computer.
- Every aircraft uses a generic model: check that the custom VMR files are enabled and not being overridden by a broad fallback rule.
- vPilot reports missing models: the VMR and model package may be from different releases, or an optional base package has not been installed.
- Textures are blank or show a missing-texture pattern: reinstall the complete package and its required base models. Copying only a repaint folder often omits shared texture files.
- The aircraft type is correct but the airline is wrong: the remote pilot may have filed an incomplete type code, used an unrecognised callsign, or selected an airline absent from your pack. That is not necessarily an installation fault.
- The models do not appear in the MSFS aircraft selector: dedicated traffic models may intentionally be non-flyable. Their absence from the hangar does not prove that installation failed.
- Performance drops at busy airports: remove overlapping packs and avoid matching large numbers of high-detail flyable aircraft. Dedicated traffic models are the better choice for dense VATSIM traffic.
How should a model-matching pack be updated?
Keep the aircraft packages and VMR rules from the same release, because renamed model titles can make older rules fail.
Use the package's documented update method rather than blindly merging every old and new folder. Afterwards, replace obsolete VMR files, check for duplicate entries in vPilot, and restart both applications before testing.
Can VATSIM model-matching liveries be installed on Xbox?
No. This workflow is for MSFS 2020 on Windows PC because it requires vPilot, access to user-installed packages and manually loaded VMR files. Although MSFS 2020 runs on Xbox Series X|S, the console version cannot run the required external VATSIM pilot client.