Microsoft has a huge glider airports package as you may know. And it overrides with MSFS2020 ports of those glider airfields if they don’t have exclusionrectangles. My airfields had these issues at the beginning but I placed exclusionrectangles and issues are gone. I released it on various shops and also on MSFS Marketplace.
When my scenery is loaded from the community folder, there are no issues.
So it looks like those packages are overriding my scenery since my has exclusionrectangels for disabling them.
I can’t reproduce and do things to fix because I can’t stream my own scenery so this looks like should be fixed from the Microsoft side. Can you help me? I think package load priorities should be fixed. 3rd party contents should be on top?
We are having the same issue on our latest Marketplace release.
Our package has an exclusion rectangle and relevant excludes to replace the glider scenery. This works perfectly well in the Community folder, but when the package is streamed via Marketplace, the Glider package is taking priority.
We have had a number of Xbox customers complaining with this issue.
The only workaround is to disable the 3 glider packages, but that’s an awful user experience when purchasing a new scenery.
See Burning Blue Design Bodmin airfield on the Marketplace if you need to replicate the issue.
How does it pass Microsoft Testing like that? This should be immediately get fixed. I said tag these airports as currently incompatible to Teams people. Also I contacted them about the issue but it was weekend so no response still.
I am able to replicate the issue.
If we stick to the example on LSZX, I can only see a single Exclusion Rectangle that only excludes Car Parking.
Is there supposed to be more exclusion rectangles?
When I stream it on marketplace, I can see my exclusionrectangles but overlapping issues are continuing. See the package names of exclusionrectangles below. But they dont to anything.
I’m now sending you the package that i uploaded to MCP, by following the steps you sent.. You can take the package there and copy to your community folder.
Well, still It looks like it includes all the airport and should exclude microsoft package. I also took the screenshot by enabling it from marketplace. Don’t know why is the difference but, it looks like it should work anyway but its not working.
No, the single exclusion rectangle I have on the Marketplace version only excludes Car Parking.
Your other rectangles with the flag “excludeAllObjects” are the ones missing.
I have the expected behavior with your Community version.
I checked the BGL files and they are slightly different so likely something going wrong when the package is ingested.
We will investigate this further.
Thank you for providing the package.
Possibly I checked a previous version.
Did you send an update of this package without incrementing the version in the ProjectEditor/manifest.json maybe? There seems to be multiple 0.1.2 versions.
The other possibility would be an issue with package order hints.
We will keep investigating and will let you know when we have a definitive explanation.
Hi Syvlain @FlyingRaccoon ,
1.2 update is only for the MSFS24 exclusionrectangles, its packaged on 23 November and since then its untouched. It went live on 2024 Marketplace last week. Also I only have one marketplace export on my PC for the 1.2 update.
I think it can be seen that I only uploaded one version of 1.2 update to MCP from my MCP history which I don’t have access.
I don’t even remember this was an option until recently? I could be mistaken. I had this build from a while back as it doesn’t have the package order hints either.
I’m now reuploading to MCP to see if it fixes our issue.
The main issue is that even without excludeAirports checked, the package works completely fine in-sim while editing and when built for the Community folder. It correctly takes priority over the glider packages.
When streamed via Marketplace, the glider packages take priority.
Is it possible for streamed packages to take priority over base content by default?
I’ve also just noticed this in the manifest.json of the freshly built Bodmin:
“globally_overriden_base_sim_files”: [
“fs-base-genericairports”
Maybe this is somehow related to the issue of packages without this getting incorrect priority?
It’s maybe not relevant for a VFR glider field, but be mindful that an airport exclusion rectangle will also delete the navdata airport, so you will lose all navdata.
@Gobby I’m not sure about that because our airports are not overriding with base generic airports. It’s overriding with microsoft gilder airports which is a different package than fs-base-genericairports
We gotta wait until their solution. The whole process of uploading and waiting for microsoft testing on MCP takes too long for us to test our content from marketplace stream.
Seems indeed a bit weird that “default” content in Official is still loaded alphabetically in the VFS (so AgSim or Burning or not able to override Microsoft)
Shouldn’t it be put in the same loading pool right after fs-base ?
ExcludeAirports is not new, it was a flag from the Exclusion Rectangle from the start when it was added in MSFS2020 afaik
Adding it will not change the result.
The culprit seems to be the lack of order hint on MSFS 2020 packages.
This is visible in the Package reorder tool.
There is a dedicated bucket for Community packages, which explains why your packages are loaded after the glider ones when mounted through Community.
But when purchased on the Marketplace, they end up in the same bucket and alphabetical order determines the order.
There are discussions on our side on how we can mitigate this for 2020 packages.
In the meantime, using the Package reorder tool (that players can also access in the game settings) to put your package further down the list is the only workaround.
