Improve the variety, accuracy and realism of VATSIM traffic in Microsoft Flight Simulator 2024 with a cleaned and validated set of custom vPilot Model Matching Rules (VMR).

Yebbert Model Matching was created by combining, reviewing and cleaning a large number of aircraft and airline matching rules with one main goal:

Show the correct aircraft type and airline/operator livery as often as possible, while avoiding unrealistic or broken fallback matches.

The project has been tested in MSFS 2024 and is built around real-world plausibility.

If a real airline/operator and aircraft combination does not exist, Yebbert aims to avoid forcing a completely different aircraft type simply to preserve an airline livery.

What's New in V4.7?

V4.7 further improves aircraft-type accuracy, historical fleet coverage and realistic airline representation across the supported model libraries.

• Expanded Boeing 757-200/300 matching, with additional verified historical, legacy and niche aircraft coverage.
• Refined airline and AOC matching, including SAS, Norwegian, Icelandair and KLM/KLM Cityhopper.
• Corrected aircraft variants and unrealistic fallbacks for selected operators.
• Additional model-reference checks and rule cleanup across AIG, FS Traffic and IVAO MTL.

For the full list of changes, see the V1.6 / V4.7 changelog in the Version History.

Included Versions

Choose ONE main VMR

Five main VMR versions are included.

Do not load multiple main Yebbert VMR files at the same time.

Choose the version that matches the model libraries installed on your system.

Important for AIG users

Before using an AIG-based VMR, check the AIG Model Library section below. Our validated reference installation combines v1.5 and v1.6; v1.6 alone should not be assumed to contain every model.

1. AIG + FS Traffic + IVAO MTL

Use:

Yebbert_ModelMatching_AIG_FSTraffic_MTL

For users with:

• AIG AI models
• Just Flight FS Traffic
• IVAO MTL

This is the broadest-coverage edition and can use models from all three libraries.

Recommended for users looking for the widest possible aircraft and livery coverage, including additional legacy, niche and historical aircraft types.

2. AIG + FS Traffic

Use:

Yebbert_ModelMatching_AIG_FSTraffic

For users with:

• AIG AI models
• Just Flight FS Traffic

No IVAO MTL models are referenced.

This version combines both libraries to increase available airline and aircraft coverage.

3. AIG + IVAO MTL

Use:

Yebbert_ModelMatching_AIG_MTL

For users with:

• AIG AI models
• IVAO MTL

No FS Traffic models are referenced.

This edition is particularly useful for additional legacy and niche aircraft coverage that may not currently be available through AIG alone.

4. FS Traffic Only

Use:

Yebbert_ModelMatching_FSTraffic_Only

For users who only want to use:

• Just Flight FS Traffic

No AIG or IVAO MTL models are referenced.

5. AIG Only

Use:

Yebbert_ModelMatching_AIG_Only

For users who only use:

• AIG AI models

No FS Traffic or IVAO MTL models are referenced.

This remains the simplest choice if you use AIG without any additional model library.

Optional GA & Business Expansion

Use:

Yebbert_GA_Business_Expansion_AIG

This optional additional VMR expands matching for:

• General Aviation / VFR
• Business jets
• Business and utility turboprops
• Bush and utility aircraft

Business aviation coverage includes aircraft from families such as:

Gulfstream, Citation, Challenger, Global, Falcon, Learjet, Embraer Legacy / Phenom, King Air, PC-12 and more.

The expansion contains 731 additional rules and uses AIG models only.

Important

The GA & Business Expansion should only be used when AIG is installed.

It should be loaded above your chosen main Yebbert VMR.

Why Include IVAO MTL Editions?

AIG and FS Traffic provide very broad airline coverage, but no single model library covers every aircraft type, historical operator or niche aircraft.

The optional IVAO MTL editions provide additional model-title coverage where available, particularly for some:

• Legacy aircraft
• Historical aircraft
• Less common aircraft types
• Niche operators

Important IVAO MTL Notice

No IVAO aircraft models, liveries, installers or model files are included or redistributed with Yebbert Model Matching.

The MTL editions only contain vPilot model-matching rules referencing model titles expected to already exist on the user's own system.

Users are responsible for having any required model libraries installed separately.

Installation

Open vPilot and go to:

Settings → Model Matching (MSFS 2024) → Custom Rules

Recommended order

For AIG users:

1. Yebbert_GA_Business_Expansion_AIG (optional)
2. ONE chosen Yebbert_ModelMatching VMR

Do not load multiple main Yebbert VMR files together.

Choose the main version that matches the libraries installed on your system.

Updating from V4.6?

The main Yebbert VMR filenames are unchanged.

Back up your existing VMR, then overwrite it with the matching V4.7 file in the same location.

If the filename and path remain unchanged, you do not need to remove and re-add the VMR in vPilot. Restart vPilot to ensure the updated rules are loaded.

If you are switching to a different main edition, select the new file in Custom Rules and remove the old main edition. Do not load two main Yebbert VMR files together.

AIG Model Library

Important: V4.7 was validated against a merged AIG v1.5 + v1.6 installation.

Our development scans used v1.5 base models together with v1.6 updates/additions in one installation. A standalone v1.6 update should therefore not be assumed to contain every model that Yebbert references.

Make sure your installed model library is complete and follow the installation instructions supplied with your AIG download. Missing or incorrectly combined model files can cause vPilot model creation errors even when the matching rule is valid.

AIG package information and downloads:

https://github.com/Samueleonard/AIG-ModelMatching-For-MSFS2024/releases

Make sure the relevant AIG components are installed correctly, including:

• OCI / SimObjects aircraft models and liveries
• ModelBehavior
• Effects

Yebbert does not include or redistribute AIG aircraft models or textures.

Matching Philosophy

Yebbert Model Matching deliberately prioritizes realistic aircraft/operator combinations.

The general approach is:

• Real-world operator + correct aircraft type → preferred
• Legitimate historical combinations → allowed when verified
• Legitimate wet-lease / operated-by combinations → allowed when verified
• Sensible same-family fallbacks → used conservatively
• Unrealistic cross-family combinations → avoided

For example, Yebbert is designed to avoid selecting an unrelated aircraft simply because it carries the correct airline colours.

Correct aircraft type and real-world plausibility are more important than forcing a livery onto the wrong airframe.

What Has Been Improved?

The original source data contained many useful matches, but also generated, outdated or overly aggressive fallback rules.

Yebbert Model Matching has therefore been cleaned and refined to:

• Prioritize correct airline/operator and aircraft combinations
• Add verified real-world operator/type matches
• Include selected legitimate historical combinations
• Include verified wet-lease / operated-by relationships
• Retain sensible same-family fallbacks where useful
• Avoid unrealistic cross-family substitutions
• Remove duplicate and empty rules
• Provide separate builds for different installed model libraries
• Combine AIG, FS Traffic and IVAO MTL coverage where appropriate
• Add optional legacy and niche-aircraft coverage through IVAO MTL
• Significantly expand business aviation matching
• Provide optional GA & Business Aviation coverage
• Add dedicated British Airways SHT / “Shuttle” matching for UK domestic services using BA mainline short-haul aircraft
• Improve AOC-specific matching and reduce cross-operator model bleed across easyJet, Ryanair, Wizz Air, TUI and Corendon groups
• Improve AOC, fleet and wet-lease accuracy across AirAsia, Volaris, Jetstar and Smartwings using the verified AIG model inventory
• Refresh selected current wet-lease and operated-by relationships
• Remove or replace outdated AIG model references no longer present in the current model set
• Further reduce outdated, overly broad and unrealistic fallback combinations
• Expand Boeing 757-200 and 757-300 matching, particularly through verified legacy and IVAO MTL models
• Refine SAS, Norwegian, Icelandair and KLM/KLM Cityhopper fleet and AOC combinations

The AIG + FS Traffic + IVAO MTL V4.7 edition contains 9,477 matching rules.

The optional GA & Business Expansion contains 731 additional rules.

A Note About Model Matching

Model matching can never be 100% watertight.

vPilot may have multiple valid models available for a matching rule and can choose between those models.

A VMR rule containing multiple models should therefore not be interpreted as a strict first-choice → second-choice → third-choice priority chain.

Yebbert controls which models are considered valid candidates for a match, but vPilot ultimately handles the final model selection.

Different users may also have different:

• Model-library versions
• Liveries
• Installed subsets
• Missing or outdated packages
• Incorrectly installed model libraries

Because of this, an occasional unexpected aircraft, livery or model-loading error can still occur even when the VMR rule itself is valid.

A ModelErrors entry does not automatically mean the VMR itself is incorrect.

It can also indicate that a specific model or livery is:

• Missing
• Outdated
• Incomplete
• Incorrectly installed

The goal of this project is therefore not to promise perfect matching, but to provide a cleaner, broader and more realistic starting point for MSFS 2024 VATSIM traffic.

Feedback & Error Reports

Feedback is very welcome.

If you encounter:

• An incorrect aircraft type
• An obviously incorrect airline/operator livery
• A missing model
• Strange fallback behaviour
• A vPilot model creation error

Please include, when possible:

• Callsign
• Aircraft TypeCode
• Exact Yebbert VMR filename/version
• Which model libraries you have installed
• Relevant ModelErrors.txt entries from vPilot
• A screenshot of your vPilot Custom Rules order, if relevant

Please also make sure the selected Yebbert edition matches the model libraries actually installed on your system.

Real-world testing and community feedback will continue to be used to improve future releases where possible.

Important

Yebbert is a model-matching project only.

It does not install aircraft models and does not inject AI or static traffic.

The required aircraft models must be installed separately through the supported model libraries.

FSLTL models are not referenced by the V4.7 editions; FSLTL integration is planned separately for V4.8.

Enjoy the traffic!

– Yebbert