We’re having a huge problem with our latest VFR North-East and North-East VFR Airports scenery in the MSFS2024 marketplace version!
All exclusions no longer work (they worked during my validation tests), so most objects are duplicated (airport buildings, wind turbines, electricity pylons, etc.), whereas in the Community version everything works perfectly! The ground surfaces (aprons, taxiways, etc.) are replaced by those from the default MSFS scenery and cover our custom ground surfaces.
After analysis, it seems this is simply a loading order issue! Our scenery should be loaded after the default MSFS scenery, but the opposite is true; the MSFS scenery covers our scenery, overwriting most of our objects and polygons.
It is not normal the sceneries work fine with community version and not with marketplace version…
Under the Marketplace PC version, there is a solution: moving to the “packs re-organization tool” and moving the scenery at the bottom of the list, to force the scenery being loaded the last one, this is not reliable because many users will not be informed of this feature, and a new third-party scenery should work immediatly after installation without any specific action !
And more than that, this feature is NOT available under Xbox, so in this case there is NO solution !!!
Thanks
1 Like
I think this is the same issue: https://devsupport.flightsimulator.com/t/streamed-packages-overriding-with-my-streamed-airport-add-on/14590/23
It may be a naming convention problem. If the package name started with a letter after the default packages (z-myname-package) then it may load properly. Or perhaps setting a dependancy for the default packages might work. The addition of the package to Community will always work as Community packages load after the streamed packages.
1 Like
thank you but is it a joke from Microsoft ? whatever the addon is a FS2020 compatible version or a FS2024 native version, the third-party addon has to be streamed so loaded AFTER any default package, the opposite should be totaly stupid !
1- in the marketplace version the package name is automatic from the compagny name and other data
2- we cannot change the packagename for all existing products !!! so does it mean all of our FS2020 products cannot become compatible with FS2024 ?
3- if the organization tool exists in the PC version it should exit in the xbox version !
now if microsoft let this issue as it, it means we’ll not be able to provide sceneries properly working under FS2024, and we’ll have a lot of support and bad rankings for something that is not from our side ! This is something that could make the customers move to the community versions outside the marketplace ! is it the goal for microsoft ?
1 Like