I’m waiting to hear from Asobo for a permanent solution. We are in a sale season in Marketplace and we are getting the highest sales figures right now. That issue comes back to me as tons of customer care e-mails and low star ratings.
In the meantime, is it possible if we can add “z” to my package names as first character without whole process of regular add-on MCP update?
I mean something like that:
z-agsim-lszm
z-agsim-lsze
z-agsim-lspv
z-agsim-airport-lszi-fricktal-schupfart
z-agsim-airport-lszx-schanis
z-agsim-lszp
It’s being worked on, but this is going to require some time to develop and test so I’m not expecting this to be addressed in SU3.
In the meantime, we are in the same situation as in MSFS 2020, where there is no solution for Xbox players, and PC players will need to use the Package reorder tool that is accessible from the “Advanced Options” setting menu in such case.
I will update this thread as soon as I have more news to share.
I hope it gets fixed before another sim update. This is affecting MSFS Marketplace partners’ business. Thanks for your information, I’m waiting to hear from Asobo soon for a date.
Same issue with three released sceneries “conflicting” with generic ones. I agree with Ardguler : this bug is affecting our business as MSFS Marketplace partners. Many Sim Pilots are complaining now. The least Asobo and Microsoft can do is releasing an official communication to explain the source of the problem. We are not who must bear the load of it.
Nothing that will be of interest for you or players at the moment.
I can just say that this is an active topic, continuously discussed by Microsoft and Asobo and I hope to be able to provide an update soon.
just want to hook into here, because I encounter this issue at my freshly published scenery. Cost me sleepless nights so far and some bad reviews. Hopefully there will be a solution soon.
Thank you FlyingRacoon for your reply; We, the MSFS Markertplace partners, are facing a growing wave of discontent clients. Our business is badly hit. We are who pays the price. We cannot be held responsible for errors beyond our capabilities. The least ASOBO & MICROSOFT can do is releasing an official statement about this major issue and communicate to the whole community of MSFS Sim pilots.
Following your suggestion that the packet order hint was the culprit, we updated our Bodmin EGLA 2024 package to include the “CUSTOM_AIRPORT” hint.
It’s gone live on the Marketplace, but users are still getting the same issue with it being superceded by the default glider airport.
As others have pointed out, this is really poor for our customers and the least we need is an idea of an ETA for the fix
