We need a full explination as to why add on aircraft continues to show up as generic planes. Several people mentioned that you need to buy the same aircraft in order to see it.
That is nonsense. All settings are correct in the game controls as well. What I did find today is the official SDK showing that it should be working based on ICAO codes.
Upon checking the aircraft.cfg files, the correct codes are there. Microsoft Flight Simulator we need answers regarding this attached SDK.
Why is this not working???
Hi @DJJerseytwin ,
Thank you for this report. We’ve moved your topic into the User Support Hub.
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
1 Like
All well and good but this is an issue often near my local airport I have atrs flying in that are coming in as an a380 you know the biggest passenger plane not a regional turpoprop that alone isn’t great and the ICAO code attached to the nameplate tells me the plane it should be
Or have the same add-ons as the other player yet I get an a320 doing hovers rolls and loops and over mach 1 because it’s meant to be a F35B this is why on PC they have made 3rd party apps to sort this fix this issue
On Xbox we can’t get those said add-ons so please fix it and get model matching somewhat better
Can you try get an answer for us about this and communicate back to the community, you guys need to be a bit more active talking back to us in the forums it will go along way to fix attitudes only say this as often when I’ve joined a forum for anything else you generally get responses from mod teams or development within 3 days here I’m seeing no communication from the community managers or care for community please do better
1 Like
@WaggazM Correct, this to all of us is a clear bug. @DementedCorn327 can you please move this back to know bugs?
2 Likes
Exactly the fact they say to us on Xbox you will see the same if you have it and every bloody time it’s a a320 it’s an issue something fundamentally not working as it should to what the developers have said it’s an issue/bug that needs attention
So far crickets from the mod. This needs to be considered as a bug and fixed asap.
1 Like
Exactly what I was talking about with communication with your community
The mods are volunteers, not Microsoft staff like the community managers. It’s not fair to expect them to respond immediately.
There have been problems with model matching in the sim since 2020 launched and it has never been fixed, so expecting it to be fixed just right now is not realistic. It’s not like Asobo doesn’t know there are problems, and there have been plenty of threads about this. It’s clearly either not a simple fix or it’s not considered important enough to spend time on.
Now with that said, model matching in 2024 in particular is terrible. Worse than 2020, if that were possible. The problem likely lies with the algorithm for matching to a ‘suitable generic aircraft’. For the F35s appearing as A320s, the sim has picked something which is a) a jet, b) has two engines, and c) is present on everyone’s machine. If you ignore the fact that the F35 is a fighter jet, it almost makes sense. The problem is that the aircraft.cfg doesn’t include any kind of ‘category’ information that would tell you that. It would obviously make more sense to match the F35 with the F/A18, for example.
The other thing I suspect happens in 2024 is that it doesn’t want to model match to an aircraft you don’t have in your streamed data folders, so it’ll prefer something you already have downloaded vs something it would have to download. But even when it’s a default aircraft, I still sometimes see other players as Bonanzas when they have something we all have, so something’s broken.
The real clincher (for PC pilots) is that the M3 people have said they won’t be updating it to work with 2024, and since Asobo has changed the structure of the default aircraft the existing tool will now only work using aircraft in your community folder as targets.
A simple way of overriding the default and configuring your own 1:1 model matches is badly needed, and there is a wishlist item for that somewhere, but it will never get enough votes.
If this is the case, then why did the mod just move it from bugs and went silent? Even if this is a know issue since 2020, then why publish an sdk showing that it works, when clearly it doesn’t? The aircraft.cfg produces the ICAO code for aircraft, which clearly shows that it should match and be accepted. The ICAO codes listed in the cfg is accurate and correct. It’s just unacceptable.
Yea that’s fair about a mod I didnt read his title properly but community managers definitely need to do some more communication with the community
Yes understand we are talking about addons as well here but for addon to be sold in the marketplace it has to fit Microsofts criteria I’m on Xbox so everything’s gone through marketplace so approved add-ons as you would say as I can’t get any free ones
and all my add-ons are being streamed for 2024 so that’s not the issue of is it downloaded they need to look into more tags for it to give us more options or go through and physically choose the generic aircraft per type (hell wouldn’t care seeing a bunch of f18s if they were meant to be 16s etc) but right type of plane vs generic a320
2 Likes
For a bug report you are supposed to use the bug reporting template. You didn’t, and you didn’t give anywhere near enough detail for this to be reproducible by the team as a bug. The mods are charged with tidying up the forum and one of the things they do is moderate bug reports to make sure they are using the right format and have enough information to be submitted as a bug to the triaging team. If they don’t, the post gets put into the user support hub, as this one was, along with the standard reply you got.
The intent is for you to use the template to provide steps to reproduce your issue. You didn’t, for example, say which aircraft it was you were expecting to see or what you saw instead. Also, I’m sure there are bug reports about incorrect model matching already and again, the mods are charged with closing or merging duplicate bug reports.
That SDK doc has been there since 2020 (and that looks like the 2020 SDK in your screenshot anyway, whereas you’re reporting this for 2024) and it has never worked as described. Unless the ‘appropriate’ generic aircraft just means ‘has the same number of engines’. That’s one for the SDK team to address.
Don’t get me wrong, I’m as frustrated with the terrible multiplayer experience as everyone else. But it’s one thing among hundreds of other things that people want fixing, and the way to get the devs attention on something is to follow the bug reporting process so they can reproduce it and add it to the bug-logged list.
1 Like
Thats fair to say and I agree with you. Even if I referenced the SDK from 2020, you would think it would carry over and that it would be fixed in 2024. I guess not. Now when you really think of it, is it really a bug if it never worked? Either way, this is visible and regardless of not documenting it as a bug, they are clearly aware of this and are not even addressing it. Why produce facts that suggests it works, when it doesnt? This is regardless again of it it’s 2020 vs 2024 SDK documentation. I nor anyone else should even have to report this as a bug.
Yea model matching is a lower thing for on the wish it was fixed things (like I said would be happy if they used some more generic options to diverse the skies around)
I understand the frustration when a bug report is moved out of the Bug Reporting Hub category. But part of our role is to keep the forum organized and in the case of the Bug category we need to ensure that new reports comply with certain rules, among them:
-
Filling in the provided template so that devs have quality and enough information to replicate the issue and other users can also contribute with their test/findings
-
Issue is happening with the base sim and 1st party content, without any 3rd party addons installed
Issues related to the SDK and 3rd partly developers that need to report issues must use the main SDK forums located at https://devsupport.flightsimulator.com/
You can contribute to the main thread related to model matching: Multiplayer: display other players actual aircraft 3D models and liveries around you
Hope the information provided clarifies the move of category.
1 Like
Thank you very good clarification there
1 Like
Appreciate the follow up and clarification.
1 Like
I’m one of the developers for M3 (Multiplayer Model Matching) for PC users, and its true that we did not plan to redevelop the product to work with 2024 as it was expected that model matching would have been addressed in some manner, if not at launch, then sometime in an early SU release. This has likely been deprioritized due to all the other bug fixes being worked on. There appears to be some basic model matching taking place for marketplace aircraft a user doesn’t own, but I’ve been out of the loop for a while now, so I can’t really provide any more comment on how well its working. Also, any 3rd party aircraft (outside of the marketplace) will not benefit from this.
As noted, M3 does work in 2024 if the user removes all 2020 default target aircraft and adds their own target aircraft found in their community folder. To generate the package, the user will need to have 2020 installed in order for any new ICAOs to be included in the updated ICAO file. We might consider creating a MSFS2024 version of M3 if the issue continues to linger, with some generic aircraft available for defaults (i.e. taildragger, helicopter, fighter jet, etc.), but nothing is planned atm.
- flyndive
@flyndive Whatever built-in model matching there is does not work very well, frankly it’s probably worse than it was in 2020. I’m utterly sick of seeing A320s instead of miljets that I don’t own.
You can make 2020 community folder aircraft targets as you described, but that does rely on you having lots of them. It would ideally be possible to use the 2024 default aircraft.
The problem with using many of the 2024 default aircraft as targets for the existing version of M3 is that it expects to find things in places that have changed for pretty much all of the aircraft produced by Asobo and some of the others. So the vast majority of default aircraft cannot be used in that way, short of doing all of the config and database updates manually and directly. And I’m not even sure if that would work.
If you don’t plan to update it for 2024, could I again appeal for you to make it open source so that somebody else can?
1 Like