Check out the weekly Development Update blog post here:
Please use this thread for feedback and discussion. Thank you!
Appreciate that you can now see how many days it has taken for each third-party product (New and Updated) to be released on the Marketplace after the Creator signed-off that it was ready to go. You can see this information in the dedicated Marketplace release page-very handy to have, bravo!
8 Likes
When it was submitted is what we rly need to know. Signing off is the absolute final step of many for the developers.
A LOT of the time the problems end up on Asoboâs end on products that work fine on PC and wonât ingest.
That actually feels deliberately misleading to me.
1 Like
Hello @QueazyTable959,
This information is already available for MSFS (2020) Marketplace submissions (see screenshot below). The left column represents the number of days between the developer submitting that version of the product for Marketplace intake and when they signed off that it was ready for release, and the right column represents how many days after signoff until it was released for players to download.
Letâs look at the Got Friends AS 33 Me as an example. In this case, it took 9 days after they submitted the product for the initial Microsoft intake and developer testing/signoff to be complete. It then took a further 5 days after signoff for the product to be released to players on the Marketplace.
Iâm unsure why we only have the âDays from Creator Sign Off to Releaseâ and not also "Days from Last Submission to creator Sign Offâ for MSFS 2024 products, but we can check with the Marketplace team and see if we can get that information added for future weeks.
Thanks,
MSFS Team
10 Likes
I think the confusion may be the language on the table of âLast Submissionâ which I think is meant to reflect âmost recentâ but it also means (in your example) the first submission. Without that information, I think users may infer that there are many back-and-forths that occur (theoretically causing a delay) and then weâre given the âfinalâ submission date and the duration between that final/last submission and sign off here.
Hope that makes sense.
1 Like
Hello @Zadma,
I wrote the below text (emphasis added) in my comment above, indicating that the left column represents the number of days between developer submission to intake of the most recent version of the product:
The left column represents the number of days between the developer submitting that version of the product for Marketplace intake
As you know, each Marketplace developer is responsible for testing their own products. If they submit a version of one of their products and then during testing after the initial MP intake they discover bugs that necessitate a new version before they will sign off that it is ready, that will obviously cause a later release date for the product. However, any delay in that scenario isnât attributable to Microsoft. The Marketplace team can only control the speed at which initial intake of each version of a product is completed and then how quickly products are made available to players on the Marketplace after the developer signs off that they are ready to release.
For this reason, it only makes sense to publish the number of days since the developer submitted the final release version, not any earlier versions that were never approved for release by their respective developers.
Thanks,
MSFS Team
4 Likes
I think this is the sticking point that some users, and even developers, (incorrectly or not) will say is the part that causes the proverbial holdup, and they will blame the Marketplace intake process. I wouldnât know how real transparency around this could be achieved without tediously publishing the dates of every step for every addon, which is obviously not feasible.
Maybe providing the following dates (or durations between each date, if thatâs easier):
- First submission to the Marketplace/Intake process begins
- Intake process by MS is completed and the product is ready for testing
- Final version is submitted to MS
- Final version is signed off by Creator
- Product is released
But honestly, I think weâre already being provided more information than weâre necessarily entitled to, so this would certainly be above and beyond.
3 Likes
As blurry ground texture and lod started as 2024 but now with su16 has affected 2020 also, they should really change the column with version â2024â to note 2024/2020?
Given this issue looks to soon overtake vram bug as the top voted item now that we canât escape it by using 2020 anymore, sure hope there is a concerted effort underway to resolve and not just in su4 of 2024!
5 Likes
Yep, this topic got some âairtimeâ during the last developer Q&A where they said this was not an intentional change and theyâre looking at ways to restore the old textures when/where possible and (effectively) artistically desired.
2 Likes
Yes was indeed reassuring to hear Seb note that. The fact that 2024 has been in such a state since launch a year ago in terms of aerial / ground textures quality vs what 2020 had, and that the bug list as yet still only notes MSFS 2024 and su4 as timeline, would be nice if they could at least acknowledge further by amending the list to show it includes 2020 and either su16.1 or under investigation. (Or even better, here is su15 back) 
1 Like
The âExcessive Reflectionsâ bug has now made it onto the front page, but it is still only marked as âPlanned for SU4â.
We are now well into the beta, with some people calling for the current version to be the release version (despite the various problems left unresolved). I hope there wonât be some last-minute patch on this, like just turning the intensity of the reflections down rather than making the reflections correct.
For a bug which was not present in FS2020 but has been in FS2024 since launch, and which badly affects so many aircraft, it certainly needs more attention than it has received.
2 Likes
Sorry, but I still don´t get it. In the case of the Blacksquare Aircraft for FS2024-Marketplace, they were submittet for release 2 months ago (Piston and Turbine Dukes). These aircraft are sold by Justflight and other third party shops for FS2024 and work well with no problems.
According to Justflight the Dukes (and other BS titles) were submitted to the marketplace and the release is in the hands of MS. They have some issues that need to be resolved on their end before release.
Source
I´m asking myself, how can it be? Airplanes, that worki without problems if you buy them in a third party shop need weeks or months to get in the marketplace? What can be so difficult?
In my point of view there has to be a systemical problem at Microsoft/Asobo in the Marketplace implementation process.
YES
to be corrected before SU4 public release !
While I never really cared about Marketplace speed, I do appreciate the attempt at transparency here.
1 Like
@DataX05DX
I believe you pinpointed the issue.
To me that seems to be a delay in the developer signing off that their product is in fact ready to go.
Not much the Marketplace can do in that case.
They may have submitted the product, but it seems they havenât yet completed all the required steps.
I think the âtheir endâ in their post was MS/Marketplaceâs end - BS handed it off to the Marketplace team and the Marketplace team has issues to resolve (allegedly). All speculation at this point though, unfortunately.
You are indeed correct, Tthat is what was said, though I do suspect that the issue is with the devâs given the ingestion process, and hence my statement
Thank you for addressing this. According to Blacksquare, they handed the package over to Microsoft in August and are now just waiting for Microsoft. They have stated this in several places. Microsoft ist the one that has some problems. And Blaqusqare is just waiting.
This is what I don´t get, because you can actually buy the same planes in the Justflight shop and they do work without issues.
That might be what the devs say and might even be what they honestly believe. Unless we see some proof we have no idea what the situation really is. Wouldnât be the first time a dev has messed up something on their end that just matters when products are released via the marketplace (like, for example, following naming conventions) or just forgot to click a button. Doesnât mean they did something like that, doesnât mean the delay isnât caused by an issue on Microsoftâs side. Bottom line is, people are pointing fingers but that doesnât prove anything.
1 Like
2 posts were split to a new topic: Marketplace Inaccessible [Oct-24-25]