question

We reported the same to our Marketplace contacts but, likely because of the thanksgiving holidays, haven't got a reply yet.

I also flagged it as a bug in the SU7 Beta and, basically, it's a problem that, content that is part of the Standard Package has no "Delete" button in the Content Manager on XBOX. It does it on PC, of course so, no problem on PC, where users can also act on the Content.xml file to sort out priority problems.

But right now, it's impossible for Xbox users to disable a default handcrafted airport that is not part of a World Update or a Premium upgrade and, in some cases, is preventing user to use what they already paid for because of new default airports being introduced to cover the same airport that might have been already on sale in the Marketplace for a while.

Case in point, our scenery for Zurich. While for PC users it's enough to Delete the default Microsoft version to fix any conflicts of double objects like the ones above, XBOX users can't so, they have no choice other than uninstalling the product they bought.

While I might understand the reasoning behind not letting Xbox users mistakenly remove something that might be required for the sim to work, this should not include airports.

Not fixing this will seriously hamper any future airport development, because nobody knows what Microsoft might include in the *future* so, any airport might be at risk of becoming unusable for those that bought it.

While PC users might react by simply preferring to buy outside the Marketplace, Xbox users (or PC/Xbox dual users that might want to pay for something only once ) won't have this choice, and will just be frustrated of losing access to something they already bought, because of a future update.

If the problem Is layering, can you Asobo please consider the idea of content.xml delete and re create right After the addition of new packages?

Maybe you can upvote this idea ?

https://devsupport.flightsimulator.com/idea/2712/exclusions-and-contentxml.html

Hello.

This a problem with package order management. Your custom airport was installed before the asobo one and they're now conflicting.
On PC, this can be solved by clearing the Content.xml but on Xbox, the only solution I can think of is to reinstall the game.
We plan to address these issues and improve the Content Manager to avoid this kind of problem.

Regards,
Sylvain

On PC, this can be solved by clearing the Content.xml but on Xbox, the only solution I can think of is to reinstall the game.

Wouldn't be easier if the Xbox version removed the Content.xml at each restart of the sim, or when a new scenery is downloaded from the Marketplace ?

Thank you for your response on this matter @FlyingRaccoon

However, it's a matter that should be in looked into expeditiously for the nearest possible update since it's a major inconvenience for our customers to reinstall the sim (~100+GB?) just to get our scenery working when it isn't an issue that's been provoked by any wrongdoing in our development process.

It's rather a pain to tell the customer the issue is with the sim, and then when they open up a ticket with Microsoft/Asobo, they receive an automated response being told that the developer is responsible for this issue.

I really hope it can be resolved ASAP.

Kind Regards,
Max
iniBuilds

My 2 cents. This might not be politically correct, but I guess the real question is: do we/MSFS customers need Handcrafted Asobo Airports when basic features (like VGDS) are still not available, models have no snow, the glass shimmers during fog and the installer/update system sometimes works and sometimes doesn't? CTDs are a standard behavior now but almost never happened in Alpha/Beta. Is it Microsoft's requirement that Asobo would create their own airports? I mean - the whole Marketplace system was created to cooperate with 3rd-party devs, basically removing the need for Asobo to create any more custom sceneries. Perhaps I am dumb but I see no reason for Asobo's to make free custom sceneries...

The thing is - there are plenty of people worldwide able to create airport sceneries and a very limited amount of Asobo engineers able to dig into the MSFS code and add/fix features. In my opinion, Asobo is wasting time and resources with all those customized sceneries, which are of course better than just default but not as good/detailed as commercial 3rd-party sceneries. It almost seems like a conflict of interests. Besides, they introduce additional bugs when used together with 3rd-party and this should have been the first thing to analyze, investigate and fix. All these bugs directly influence sales.

The last thing - all our products are checked and tested by the Marketplace team however these products behave differently on our customer's computers, which means, that the testing process is wrongly performed. For over two months users got CTDs when loading some products, there were no jetways and, as mentioned above, we can't test Xbox content relying on the Marketplace team to do it. The tests are good but some users still get major issues, including purchasing of products. I myself tried to install a product on my friend's Xbox and did not succeed, the product just wasn't visible in the sim although it was active and marked as Installed.

Tech issues with the sim (or lack of features) only Asobo can handle while thousands (hundreds) of people can do good custom airports and airplanes. This probably will not happen, but I sincerely believe that these priorities should be reconsidered.