MSFS 2024 – Multiplayer: Model Matching, Audio Routing, Performance and Legacy Aircraft Avatar Positioning

Version: All versions

Frequency: Consistently

Severity: High/Blocker

Hi everyone,

I’d like to raise several longstanding multiplayer issues in MSFS 2024 and hopefully get some technical clarification on how these systems operate.

I regularly organise community group flights involving more than 20 aircraft, often with a mixture of default, first-party and third-party products.

Several of these issues date back to MSFS 2020 and have been discussed previously on the community forums. Rather than reopen several older discussions, I’ve consolidated the main problems here, along with the troubleshooting we’ve already carried out.

I’m happy to provide additional testing, configuration details or recordings if useful.

1. Multiplayer Model Matching – Incorrect Aircraft Substitution

Issue: Multiplayer aircraft frequently display as incorrect models, even when the correct aircraft is installed on the receiving user’s system.

This occurs across different aircraft types and products.

Investigation already carried out

We’ve investigated the aircraft identification and fallback configurations extensively, including:

  • Auditing 388 installed aircraft and livery configurations.

  • Correcting 37 aircraft.cfg files affecting 89 configurations.

  • Reviewing ICAO type designators and aircraft metadata.

  • Investigating PlaneTypeICAO.spb and PlaneTypeFallbacks lookup data.

  • Creating an extended ICAO lookup configuration containing 10,168 records.

  • Preparing 175 fallback mappings, including additional ICAO aliases and corrections.

  • Installing modified lookup configurations through the Community folder and verifying that the package was mounted.

Despite these changes, we have not established that the modified lookup files control the final aircraft model selected during multiplayer sessions.

Technical questions

  1. Does multiplayer use the same PlaneTypeICAO and PlaneTypeFallbacks lookup data as AI traffic?

  2. Is multiplayer model selection performed locally, server-side or through a combination of both?

  3. What is the priority order for aircraft selection when the receiving user has the correct model installed?

  4. Are Community-folder overrides of these lookup configurations supported for multiplayer?

  5. Is there a supported mechanism for overriding the model associated with a specific multiplayer ICAO type?

Requested improvement: A documented local multiplayer model-matching override mechanism, allowing users to map an ICAO type to a specific installed aircraft model.

This would also allow third-party developers and community contributors to maintain aircraft-matching configurations without modifying simulator files.

2. Multiplayer Audio – Other Aircraft Volume Control

Issue: Certain multiplayer aircraft sounds do not respond correctly to the in-sim Other Aircraft volume slider.

This is particularly noticeable when multiple aircraft are parked or taxiing close together.

Expected: All audio originating from other multiplayer aircraft should respond consistently to the Other Aircraft volume control.

Observed: Some aircraft sounds remain excessively loud even when the slider is reduced.

This has been encountered across different aircraft products, including default, first-party and third-party aircraft.

Investigation requested

Could the team verify that all multiplayer aircraft audio sources are routed through the appropriate audio bus and correctly respond to the Other Aircraft volume setting?

It would also be useful to know whether third-party sound implementations can bypass this control and, if so, whether this behaviour is expected or requires changes to the simulator or aircraft packages.

3. Multiplayer Performance – FPS Drops and Frame-Time Stuttering

Issue: Significant performance degradation as the number of visible multiplayer aircraft increases.

This includes reduced FPS, inconsistent frame times and stuttering, particularly when numerous aircraft are operating close together.

We regularly fly with more than 20 multiplayer aircraft, so this represents a normal use case for our community rather than an exceptional stress test.

Suggested testing scenarios

Aircraft count Test scenario
2–3 Baseline multiplayer performance
8–10 Medium-sized group
20–25 Typical organised community flight
30–40+ Larger group / stress testing

Testing should include mixed default, first-party and third-party aircraft, both on the ground and in flight.

Areas worth investigating include:

  • Main-thread and rendering performance as visible multiplayer aircraft increase.

  • Aircraft model complexity, LOD selection and animations.

  • Multiplayer position updates and interpolation.

  • Aircraft sound processing.

  • Model loading and asset management.

  • Frame-time spikes when additional multiplayer aircraft enter the visible area.

I appreciate that internal testing may already cover these scenarios, but it would be useful to understand whether larger multiplayer groups are included in performance testing.

We would be happy to help organise a controlled test session with 20–40+ participants if required.

4. Legacy Aircraft – Incorrect Multiplayer Avatar Positioning

Issue: Aircraft originally developed for MSFS 2020 can display incorrectly positioned pilot avatars when used in MSFS 2024 multiplayer.

Examples observed:

  • ATR: Avatar appears on top of the aircraft or sitting on the wings.

  • FlyingIron Spitfire: Avatar appears approximately 20 feet behind the aircraft.

Similar behaviour has been observed with other MSFS 2020 aircraft.

Expected: The multiplayer avatar should appear at the correct pilot position or be hidden where appropriate.

Observed: The avatar can appear significantly displaced from the aircraft model.

Technical questions

  1. How does MSFS 2024 determine avatar attachment points for legacy MSFS 2020 aircraft in multiplayer?

  2. Are these positions derived from aircraft model data, configuration files or a simulator-level fallback?

  3. Is this a known compatibility issue?

  4. Is there a documented configuration change developers can make to correct avatar positioning?

Clarification would help determine whether these issues require simulator-level fixes or updates from individual aircraft developers.

Summary / Requested Follow-Up

The main areas where technical clarification would be particularly valuable are:

  1. Model matching: How multiplayer aircraft substitution works and whether local ICAO/model overrides can be supported.

  2. Audio: Whether all multiplayer aircraft sounds are correctly controlled by the Other Aircraft volume slider.

  3. Performance: Investigation of frame-time degradation with realistic multiplayer group sizes exceeding 20 aircraft.

  4. Avatars: Identification of the cause of incorrect avatar positioning on legacy MSFS 2020 aircraft.

These issues have been observed over several years and across a wide range of aircraft products and user configurations.

I appreciate the complexity involved in multiplayer systems and the work that goes into maintaining compatibility across such a large aircraft ecosystem.

My aim is to provide useful feedback and help narrow down the underlying causes.

I’m happy to supply configuration files, test recordings, performance captures or coordinate larger multiplayer test sessions if these would assist the development team.

Thanks very much for your time and continued work on the simulator.

Cheers,

Murph

In the group I belong to, issues like these are so common that some members—despite having purchased MSFS2024—refuse to switch over from MSFS2020; consequently, we still use MSFS2020 for our group flights.
I hope that model and livery matching will at least be on par with MSFS 2020.

Model matching: It seems the only specific simvar communicated in multiplayer is “TITLE”, i.e. the name of the Livery with no info about the type of aircraft. So if MSFS can’t match TITLE, model matching drops off a cliff . Gliders are routinely replaced with e.g. an ATR turboprop and a ‘mod’ livery on a mutually installed plane will cause MSFS model matching to flip to a completely different aircraft type.

IMHO MSFS needs a new parameter in the aircraft.cfg that specifies a generic plane/vehicle type, communicates that across multiplayer and Asobo can define a sensible set of values for all the stock aircraft which would bootstrap the process.

The stock MSFS avatar: this new feature didn’t include a documented way to turn it OFF and the ‘default’ is to always have the avatar in the multiplayer external view. This would be a bigger problem except many planes are big enough that a badly placed redundant avatar isn’t usually visible outside the model and the avatar draw distance is quite short. If you have a plane with a tight cockpit or planes that fly in close formation (so absolutely fighter jets and gliders), you will see avatars standing/sticking out of cockpits everywhere in multiplayer.

In the screenshot above, the F-16 appears as a Gripen; however, my friend is using the same aircraft (with the SC Designs default F-16 livery)—it is not an add-on livery.

Looking at the Multiplayer Name Labels in MSFS2024, the ICAO type code is displayed correctly, but I occasionally encounter situations like the following in multiplayer:
There are cases where the ICAO type code and the livery name do not match at all.

F/A-18E xxx / F-16 / xxx NM / xxx FT

ah ok - you’re saying MSFS model matching can fail even if two players are flying the exact same installed package. I’ve seen that also, and the nameplates seem to provide a clue (if the nameplate data is related in any way to the ‘traditional’ shared multiplayer data, which might not be the case). I guess these issues split into two underlying catagories - “same package model matching”, which should work but sometimes fails, and the much more common “package fallback model matching” where multiplayer A simply has a plane (or livery) multiplayer B doesn’t have installed which mostly gives an effectively random alternative aircraft.