MSFS 2024 Marketplace Cloud Texture Quality Reduction and Visible UV Seam

Version: 1.7.35.0

Frequency: Consistently

Severity: Blocker

Bug description:

Hi Asobo Team,

After further investigation, it appears that the texture quality delivered through the MSFS 2024 Marketplace cloud is not the same as the quality of the packages distributed through our third-party stores.

We build and submit the Marketplace package using the same high-resolution source textures used for our other releases. However, the texture files delivered through the Marketplace cloud are significantly smaller, indicating that they are being reduced or recompressed during the Marketplace packaging or deployment process.

We have not yet determined whether the visible issue is being caused by the albedo, normal, metallic, or a combination of these textures, since all of them appear to be reduced in size. The resulting quality loss creates a camouflage-like shading pattern at certain sunlight angles and makes the seam between two UV sections clearly visible.

We would like to determine whether there is something in our Marketplace package configuration causing this reduction or whether the textures are being altered automatically during Marketplace processing.

========

Image 1 – Correct Texture Quality

This image shows the aircraft using the package distributed through our third-party stores.

The package uses the original high-resolution texture assets produced by our build process. The exterior surface displays smoothly, without the camouflage-like shading artifacts, and the seam between the adjoining UV sections is not visible.

=======

Image 2 – Marketplace Cloud Texture Quality

This image shows the same aircraft selected directly from the MSFS 2024 Marketplace cloud.

The aircraft is correctly identified as version 0.3.3 and includes all of the latest systems and model updates, confirming that the correct product version is being delivered. However, the exterior textures are being displayed at noticeably lower quality than the package distributed through our third-party stores.

At certain sunlight angles, the reduced texture quality creates a camouflage-like pattern across the white exterior surface. It also reveals the exact seam between two UV sections, which is not visible when using our original package.

We have confirmed that the texture files delivered through the Marketplace cloud are substantially smaller than the files produced by our build and distributed through our other stores. We are therefore concerned that the Marketplace packaging or cloud deployment process may be reducing or recompressing these textures too aggressively.

Could you please investigate whether these texture assets are being resized, recompressed, or otherwise altered during Marketplace processing, and advise whether there is anything we need to change in our package configuration to prevent this quality loss?

Also why does the new SDK take a 8 gig project into 25 gigs only for the portal? And then once I take the MP cloud and download its just small again. Seems this new SDK process is weird. And it also causes my 3rd party packages to be too big so i have to run a clean all and then build again.

This is expected.
A package exported for Marketplace has uncompressed texture, and textures are compressed at ingestion, which can also explain some of the differences between the Community and Marketplace version.
We will review this particular case.

Regards,
Sylvain

I can confirm this is caused by the difference of compression on your normal textures.
This will be investigated further.

Regards,
Sylvain.

That makes sense. Thanks.

Hi @FlyingRaccoon

I hope you can do something where the quality for the MP PC users is the same for PC community quality. And just use this compression for Xbox. I feel this is not fair for PC users that buy on the MP store vs 3rd party stores.

Hi @FlyingRaccoon

I recently found out what happened with the quality reduction and visible UV seam. The Xbox build was apparently sent to PC customers during the last ingestion.

I went back and checked both of my builds, and they were configured correctly: PC was selected when I used Build & Export for the PC package, and Xbox was selected for the Xbox package.

Is it possible that I accidentally cross-assigned the packages during upload to the portal, such as marking the Xbox build for PC even though the packages were originally built for the correct platforms? Or could this have happened during ingestion? My contact at MS that normally handles these submissions and was off for the week, so I’m trying to understand where the mix-up may have occurred. It might have been from the replacement. Either way all good now.

So this means this post should be set to resolved. :grinning_face:

I’m confused, you no longer have the possibility to select a target platform when exporting for Marketplace in 2024.
Do you have different package sources with different quality level textures for PC and Xbox?

Regards,
Sylvain

Yes I can select the target. And we did select the target. And the zip manifest confirmed this as I checked this three weeks later when I found out the PC users had the Xbox version. This could somehow be my fault. Point is now all fixed and that was the reason the textures were low quality I suspect.

The Export window no longer allows to select a target platform:

So you meant you selected a target in MCP, which means you have different packages for PC and Xbox.

Regards,
Sylvain

Sorry you are correct this is what I meant. So what I normally do is I load the sim then load the PC and export to a PC folder. Then close the sim, load the sim again and load the Xbox version then export to a Xbox version.

So after 3 weeks I still had these files. And i checked and they were built correctly. So I suspect what happened is during the upload to the portal I must have selected the Xbox and uploaded to the PC. That would explain the low quality textures and the report from PMS50 that the GTN750 was internal. So it had to be my fault. Good news is no bug.

So the point of me showing the new image and recent update is that there is no texture bug. Just a mix up. So this topic can be closed.

Thank you as always.

1 Like

That seems to match what we see on our side where the size of the package you sent for ingestion on PC varies a lot between submissions.

Marking as resolved then.

Regards,
Sylvain

I also confirmed last night our Xbox textures have the full size albedo because those come from our livery folders and our comp and norm was half the size as these were custom only for Xbox. But the real issue was they were both outdated ones as we removed the oil canning because 2024 does not show this well at some sun angles. And i think the comp was also outdated and that is why we could see the seams. So these textures got replaced and this way our Xbox will also look as good as our PC version. So again this was our fault on accidental mix up but at least I now know I had to resolve the Xbox side since it looks really bad.