Learn how MSFS 2020 multiplayer model matching chooses aircraft and liveries, why generic planes appear, and how to fix incorrect models.
In Microsoft Flight Simulator 2020, each player's computer renders nearby traffic from aircraft identity data sent across multiplayer, using models and liveries available on that computer. If the exact content is missing, or generic multiplayer models are enabled, the simulator shows a substitute. It does not transfer the other player's add-on.
What does MSFS 2020 model matching check?
MSFS 2020 tries to associate the transmitted aircraft identity and variant information with locally installed content. The complete fallback hierarchy is not exposed to users, and results depend partly on how accurately each aircraft developer has configured the add-on's identity metadata.
- The remote player selects an aircraft and livery. Multiplayer sends identifying information and the aircraft's position, attitude and movement, not its 3D model or texture files.
- Your simulator checks its local content. It looks for a suitable installed aircraft and, where possible, the corresponding livery.
- The multiplayer generic-model setting is applied. When generic multiplayer aircraft are enabled, MSFS can deliberately use an optimised generic representation instead of loading the detailed model.
- A fallback is displayed when no match is available. This may be a generic airliner, a generic light aircraft or another broad substitute rather than the aircraft the other player is actually flying.
Each client performs this process independently. Two people watching the same player can therefore see different aircraft. Our broader explanation of how MSFS transmits and displays multiplayer traffic covers the underlying online system.
Why does another player appear as the wrong aircraft?
| Situation | Likely result on your screen |
|---|---|
| The same aircraft and livery are installed, with generic models disabled | The intended aircraft and paint scheme should be shown, subject to add-on metadata and simulator limitations |
| The aircraft is installed but the livery is missing | The correct aircraft may appear with a default or substitute paint scheme |
| The aircraft add-on is not installed | MSFS uses a generic or approximate replacement |
| Use Generic Plane Models (Multiplayer) is enabled | An optimised generic model may be shown even when more detailed content is available |
| The add-on has ambiguous, duplicated or incomplete identity data | Matching can be inconsistent or select an unexpected model |
A filename or similar-looking folder name does not make two aircraft equivalent. MSFS relies on the identity information defined by the aircraft and livery packages.
Model substitution also affects apparent size and geometry. A generic twin may have a different wingspan, height or cockpit position from the aircraft being flown, which makes close spacing misleading. This matters particularly when following our practical advice for multiplayer formation flying.
Do both players need the same aircraft add-on?
Both players do not need the same add-on to join a multiplayer session, but every observer needs a compatible local copy to see the intended model. For an exact paint scheme, the observer normally needs that livery as well.
If only one person owns or has installed a payware aircraft, that person can still fly it; everyone without the required content will see a substitute. Each user needs their own legitimate installation where the product's licence requires it.
On Xbox, PC Community-folder aircraft and liveries cannot simply be copied to the console. Cross-platform groups may therefore be unable to reproduce an exact custom livery unless equivalent content is available through supported in-simulator channels.
How can I improve multiplayer aircraft matching?
- Disable generic multiplayer models. Open General Options > Traffic and turn off Use Generic Plane Models (Multiplayer). Do not confuse it with the separate option for AI traffic.
- Install the same aircraft and livery on each viewing system. The base aircraft must be present before a livery made for that aircraft can work.
- Match package versions. Remove obsolete duplicate copies and confirm that the aircraft and livery are enabled. Older and newer packages can identify variants differently.
- Reload the session after changing content. If an aircraft has already spawned as a substitute, leave and rejoin the flight or restart it so the traffic model is created again.
- Use generic models when performance matters more than accuracy. Detailed multiplayer aircraft can increase memory use and rendering load at busy airports. The generic option is a sensible compromise on lower-specification systems.
If a friend is completely absent rather than represented by the wrong model, the problem is probably not model matching. Check multiplayer availability, server region, group membership and visibility settings using our guide to joining and troubleshooting multiplayer flights.
Is MSFS multiplayer matching the same as VATSIM model matching?
No. Built-in MSFS 2020 multiplayer uses the simulator's internal matching and substitution system; it does not read user-created VMR rules for ordinary player traffic.
VATSIM traffic displayed through vPilot uses a separate, rule-based process that matches network callsigns and aircraft type codes to installed models and liveries. That system offers more control but requires suitable model packages and configuration, as explained in our guide to installing VATSIM model-matching liveries.