Possible workaround for incompatible MSFS2020 marketplace packages in MSFS 2024 (PC)

Checked again and now it does work for planes and scenery. Weird, but nice find!

Is there a way to disable stock Asobo add on airports like Frankfurt/ EDDF? Would be great to see if the new Aerosoft EDDF works in 2024.

Thanks

Jan

If you didn’t buy the scenery from marketplace just install it as normal to see if it works.

Sir you win genius of the year award, thank you so much!

Fixed my 97% stuck loading problem in a few minutes. I just rebooted and loaded it again just to be sure it was not a fluke.

I was sure it was an incompatible package being streamed and this is proof. Why are Asobo not providing any solutions to this? 4 days I’ve struggled with this and a simple workaround was all it needed.

The Asobo and MS staff have been noticeably absent, only the community moderators who don’t have any insight have been present.

So much for MS testing the loadability of the addons before releasing them to users, they’ve failed hard on that one. The whole backwards compatibility has been an epic fail so far as I can make out.

I’d near enough decided to refund my aviator copy if the was no solution by Monday so you’ve saved me from that.

It doesn’t work unfortunately.

OK so I’m in for the first time in 4 days and despite being excited to actually use this thing I’m going to explain my approach to the method which was quite easy. Hopefully this will help others still stuck at the moment. Then I’ll go play…

These paths are for the MS store/Xbox Store PC version. They will be different for steam, and I’m guessing any poor Xbox users that have incompatible addons are just stuck until MS actually fix it. :cry:

  1. Open directory
C:\Users\fly\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState
  1. Open file in this directory Report-loading.toml (can use notepad)
  2. Search for FlightSimulator_Packages (around line 89 for me)
  3. Delete every line above and including this one.
  4. Search for FlightSimulator_PublishingGroups.
  5. Delete every line below and including this one.
  6. Now you have a list of packages-names=1.
  7. Search and replace to remove =1 on every line.
  8. Delete all of the lines that start with asobo or microsoft, it’s alpabetical order so very easy.
  9. Edit every line to add the prefix mkdir , ie. with the space.
  10. Copy this line to the very top:
cd C:\Users\fly\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community
  1. Save the file anywhere, and make sure you add a .bat extension on the name you choose.
  2. Double click.
  3. That’s it, restart and play!

To be clear, the top of my 2024fail.bat file looks like this:

cd C:\Users\fly\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community
mkdir 4simmers-a310-1-livery-pack
mkdir antsairplanes-tiger-moth
mkdir blackboxsimulation-bn3-trislander
mkdir cowansim-cowansim500e
...etc...

This workaround also works to solve the ā€œdouble sceneryā€ issue, when you have a 3rd Party Airport that is also part of the Sim Edition.

EG OMDB - Dubai.

I have the iniBuild and itisetterthan the default handcrafted version.
I have the iniBuild Version in my Community folder and 2024 is rendering both sceneries on to of each other as we can not deactivate the Asobo Airoprt in My Library.

So I simply renamed my iniBuild foldername in COmmunity to match teh streamed Asobo-Airport and it works.
I now have the iniBuild Airport in the game without default one.

So that workaround seems to work for several stuff.

Would this not also work for (say) famous flyers bought from Asobo/MS visa the marketplace too? Sorry, not at sim right now to check

I think you can probably use the empty directory method to disable any marketplace addon, even MS/Asobo ones.

I can’t seem to get it to work. Tried to deactivate several Asobo aircraft, I’m not fond of (Jenny, Hughes Hercules, Airbuses and Boeings etc.)

Had changed my Community folder to a different drive and tried the empty folders both in the new Community folder and the ā€œā€¦\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Communityā€ but the aircraft still appear. Any idea what I could be doing wrong?

I’m not sure if the workaround is needed any more since they disabled FS2020 scenery. As for incompatible aircraft, you need to have a full folder path in Community if you have something in streamed that you want to block. However you have to actively load one of the incompatible aircraft, so not selecting it to fly in has the same effect, where bad scenery kills anything you try to fly.

I want the aircraft not to appear in the aircraft list at all. There’s so much stuff there I’m not interested in and it feels cluttered. I used to do that by simply putting in a mod with an empty aircraft.cfg file for the one’s I wanted to block in MSFS2020

At least for scenery just needed an empty folder in Community to override whatever was coming down in Streamed. Not sure why it wouldn’t work for aircraft if you had the same folder name or same folder tree but I haven’t tried to wipe out an aircraft.

ok thanks.
Seems that some aircraft are gone with only the main aircraft folder (B787, Longitude). Others like the new B737 Max and the A310 are still there.

just very short - but what about things that start with Asobo - e.g. LSZH Zurich (default) - I have the version (which should already be compatible with FS2024) of FSDT in the community folder (properly installed) - yesterday while landing the airport was streamed for sure at the beginning - textures were washed out and where it became clearer again there was a ā€˜step’ in the runway - which led to the crash. I am sure that there was an overlap with the ā€˜default’ scenery or vice versa - after that the airport looked normal again. so which version is active here (since I cannot deactivate the Asobo version in the library) ? if I understood correctly - everything that is in the community folder - should not be streamed, which is certainly a ā€œbugā€ here. The deactivation will only be officially possible with the introduction of the marketplace, but I don’t find it really clear anyway what I have or don’t have there now (i.e. in my library). the community folder is also displayed as ā€˜empty’!

what will happen on that front? Are they planning a fix so that 2020 airports work again? Currently all my favourite airports (non -marketplace) either are not displayed over the autogen ones or are a strange mixture of double buildings. Unfortunately the developer doesn’t exist anymore.
But in all previous iterations of MSFS custom scenery with an exclusion rectangle superceded default scenery. This no longer seems to be the case.

The original dev needs to update anything that needs compatibility fixes to work in 2024. MS is adding the ability to deactivate specific packages in next weeks update which will eliminate the need for the empty folder trick. Maybe you can find a working combo there.

hopefully they will also decrypt the non-payware aircraft again. Currently modding existing aircraft is impossible. Thinking of all the cool flight model and camera mods on flightsim.to here. After all many stock flight model were and still are substandard

Hi, I have an opposite issue, I have the FFX Hondajet and it says ā€œdisabledā€ and every time I ā€œENABLEā€ the aircraft, it says I need to restart. So I do that and it just says ā€œDisabledā€ again (infinite loop). Any suggestions?

Never mind, for anyone who has this happen to them, I fixed this by renaming my community folder to something like community_backup. Also disabled/renamed my exe file. Not sure which combination fixed this but something did. (Incidentally, it wasn’t just the Hondajet I could not reactivate, it was all of the 2020 marketplace aircraft. All good now though!