The only thing Ms/Asobo can do is to publish an official recomendation to third parties to stick to the right configuration. Asobo implementation is correct but addons are still sold by MS Store (marketplace). I think it would be good to warn third parties officially as the impact goes to the game features. This is most likely reaching third parties faster that way than the forum posts, and customers won’t suffer the issue, so it’s good for everybody at the end.
I don’t think they can publish anything more than they do. They did a super good job on the samples and SDK writeup on this area. One of the best descriptions of any of their features available. I mean amazingly detailed and informative. But I also find it amazing how developers just ignore instructions.
But, yes, you’re right, as I wrote the above, I realized their marketplace induction process can at least automatically reject addons with incorrect Services, too. The effect of poorly written ones is just too stark.
All you can do is to report it to the addon creators and manually fix it until an official update is published. You can link this thread in your report.
As MS is checking and encrypting files I’d expect them to vetify any those “sensitive” areas especially as on XBox I can’t do any help-yourself on file level.
It’s not up to MS to check 3rd party products. They only supply tools for development of products. they have no responsibility as to the quality of 3rd party products in any way.
Asking MicroSobo to be responsible for 3rd party products is like asking Ford to be responsible for aftermarket parts for their autos.
I believe they do check and make sure these products don’t cause a CTD when installed on a vanilla system with no other addons.
Yep, that’s what I’m talking about. They aren’t MS products, they just supply the store.
What I mean is, they install MSFS (and probably all of their own products, maybe, maybe not), then install the addon to be tested. Start MSFS. Make sure it doesn’t CTD. Quit. Uninstall addon. Test complete. Test next product.
If you buy a coke at Publix and you discover that it somehow smells strange you go to the Coka-Cola Company to get a replacement rather than to Publix?
Our Marketplace team is responsible for initial validation and Compliance Testing when a 3rd Party Developer submits a new product (or an update to an existing product) for Marketplace intake. Compliance Testing includes, among other things, confirming the addon meets our required standards and doesn’t contain hate symbols or sexual content, for example. Functional testing (confirming the product works as it should) is the responsibility of the addon developer, not Microsoft.
I find it helpful to think of the in-sim MSFS Marketplace like the app store on your mobile phone. Apple and Google are not responsible for the functionality of every app they sell on the iOS and Android stores, respectively. If an app is found to not meet their mandatary community standards, then they will remove it from their stores. If the app doesn’t function correctly, in whole or in part, then it is the responsibility of the app’s developer (not Apple/Google) to fix it.
For more details about the Marketplace intake process, including a description of what each party (Microsoft and addon developer) is responsible for, please see this article we published in March.
I think the situation described in this thread is the perfect example where required standards are not met, as addons are not following the SDK required configuration. It would be a good idea to warn third party devs about the faulty ground services configuration at least, when this is detected by Marketplace team, even if we all understand that further testing is not your responsibility.
Detection of the error is as simple as entering the ground services folder to see if the ICAO subfolder naming is used or any uncompiled file exists there. It takes less than 1 minute to do it and it saves a lot of problems on every end user.
Yep, I have zero issues with the MS induction process, and fully agree with its premises.
I could see them adding this, though.
The problem is, some addons their goal is to be system wide and not just at a particular airport. So… rock and a hard place.
Is there a way to make a faulty AirportService map or spb script that remove these services worldwide on purpose, or does anybody know an airport that does this? As i want a mod that does exactly this as i only use GSX anyways.