Hello, these updates are cumulative. Same file being updated. When you import, M3 will recognize ones you have already.
Latest aircraft added to the M3 Source Aircraft database:
AS-350
Mitsubishi MU-2
J-20 Mighty Dragon
Bell 407M
Continental SR20
De Havilland DHC-7
X-47B
Alberto Santos-Dumont 14-BIS
Su-27 Flanker
JDT Minimax
Affordaplane (A-Plane)
In M3, use the Source Aircraft Import feature (under Advanced settings) to import.
Is it not possible to select the A310 or B787 as a target? They are not showing up in my list.
Hey TJ. We only included the standard aircraft as target aircraft since everyone has these. If you want to add other target aircraft, you can do so through the add target aircraft option.
M3 Source Aircraft updates are now available at flightsim.to here: Multiplayer Model Matching (M3) Source Aircraft Update File for Microsoft Flight Simulator | MSFS
Many thanks @flyndive for this - it could really improve my multiplayer experience!
I have downloaded it and run the program, but when I try to do pretty much anything on it, an error window pops up with two identical lines: “attempt to write a readonly database” .
So far I haven’t been able to find anything pointing me in the direction of how I can fix that. I’m not sure what I’m doing wrong. Any ideas?
You are only opening the app with the sim closed right?
Hello Cayman. Just a suggestion: Make sure to extract the files within the zip file into an unprotected area on your PC (such as your desktop) before running the exe.
Yes, I opened the app with the sim closed. Good news though: I have found the cure!
On a Discord channel group someone suggested that I need to make sure I hadn’t extracted the Multiplayer Model Matching software into my Program Files folder (or somewhere else which restricts read/write privileges) and suggested I should put it elsewhere in another folder which would not restrict reading or writing to files, such as my Documents folder.
That was the problem!
I moved the MMM_V1_4_2 folder out of my Program Files folder and into my Documents folder, and everything has worked fine since I did that.
Thank you @flyndive
Yes, that was the cure! On a Discord channel group someone suggested that I need to make sure I hadn’t extracted the Multiplayer Model Matching software into my Program Files folder (or somewhere else which restricts read/write privileges) and suggested I should put it elsewhere in another folder which would not restrict reading or writing to files, such as my Documents folder.
That was the problem!
I moved the MMM_V1_4_2 folder out of my Program Files folder and into my Documents folder, and everything has worked fine since I did that.
Glad you got it sorted. That’s good to know.
Would it be possible to alias ICAO codes to other planes? Let me explain.
Planes bought through the market place can not be made target aircraft because the config files are missing. But having matching not enabled for a certain type, say the DC Designs Stearman (Hereafter “plane type X”), this plane type will “natively” show up with my Stearman model. Now if we could tell the program to treat plane type Y as plane type X then theoretically we would be able to load any plane with an installed addon even though we don’t have the config files available.
We have looked at utilizing other plane’s cfgs (or a generic set) for marketplace derived target aircraft, but there are just too many variables for making it bulletproof in preventing CTDs. Models are closely aligned to their cfgs, and a disconnect may cause a sim crash.
Not sure if this is aligned to what you’re asking about, but feel free to elaborate if I missed the mark.
Maybe it was a bit convoluted and I don’t know if that would be possible at all.
Say I have the DC Designs Stearman installed but files are encrypted so I can’t make it a target aircraft.
Now natively when someone with that plane is near me, I would see this plane (the said Stearman) showing up in simulator. But with MMM I could only alias it to say the Jenny. So either I leave matching disabled, so I see “my” Stearman as per default or I tolerate it showing up as a Jenny.
My idea would now be the following:
Somehow the DC Designs Stearman shows up without MMM aliasing (because I have it installed and the sim knows about it). Now I want for example a Staggerwing (which I don’t own) to show up as a Stearman (instead of whatever), thus my question is wether it would be possible for MMM to tell the sim: “ICAO 1 == ICAO 2” and whenever ICAO 1 shows up in the sim, the sim shows ICAO 2 data that already are in the system but just not accessible for MMM.
So basically there are three guys, the Sim itself, then MMM and me. I tell MMM: “tell Mr. Sim that there are no Staggerwings, only Stearmans”
MMM tells the Sim: “Staggerwing == Stearman, so load the Stearman like you do without my configuration files as you always do when the installed but encrypted Stearman shows up”
And the Sim says “ok I see a Staggerwing but MMM tells me I should load up the Stearman instead like I would do if another Stearman was there”. Basically not a distinct package but rather a “re-routing” of MSFS internal model matching logic.
That sounds horribly convoluted again, sorry for that. But I guess that internal interface for model matching in MSFS might not be that open to allow interference without the extra steps of generating definite 1:1 packages anyway.
I saw the note about MSFS 2024 support on flightsim.to. I get your position on this, but if we’re waiting for Asobo to fix this issue I think we’ll be waiting a long time. A ready-for-2024 version of the source and target databases would be ideal.
I will try making my own because going back to sim-default model matching and having to see dozens of DC-6s as A380s on a group flight just pushed me over the edge. I simply do not understand how Asobo is still this bad at this.
Unfortunately, we likely won’t be updating M3 to work with 2024 due to the time/effort required. However, if you disregard the “base” target aircraft in M3 (since they won’t work in 2024), add your own target aircraft from your community folder, then point all the source aircraft to your newly created target aircraft, it should work as expected.
One issue I’ve noted is that community-loaded aircraft in 2024 is hit-or-miss whether you’ll see them as intended or as Bonanza’s due to some other issue(s) within 2024.
And this is why we can’t have nice things, because Asobo just takes them away