Not getting 2024 until Christmas, but was wondering what success people are having with these as I have hundreds of freeware and payware airports, photosceneries, landmarks, etc and would hate to have to trash too many of them.  Some of them appear to have been updated, but mostly not.

So far the FS2020 scenery that I ported to FS2024 work flawlessly.

Hello, may I chime in and ask a question. Can I re assign the folder where MSFS2024 looks for its community files to my MSFS2020 installation, so that I don't have to move or copy the files over to the default 2024 folder location? Thanks a ton in advance.

6 minutes ago, DieselTen said:

Hello, may I chime in and ask a question. Can I re assign the folder where MSFS2024 looks for its community files to my MSFS2020 installation, so that I don't have to move or copy the files over to the default 2024 folder location? Thanks a ton in advance.

Yes you can. Just use MS_Addonlinker to do so.

14 minutes ago, hvw said:

So far the FS2020 scenery that I ported to FS2024 work flawlessly.

That's good to hear.  Would you mind naming just a few of them?

I will be super happy if most of them work.

2 hours ago, cianpars said:

That's good to hear.  Would you mind naming just a few of them?

I will be super happy if most of them work.

A random set of my first tests all worked nicely: Samscene3D Vancouver and Toronto,  DD Chicago and Seattle,  Orbx KORS,  Bowerman airport, Nanaimo airport, etc..

2 hours ago, DieselTen said:

Can I re assign the folder where MSFS2024 looks for its community files to my MSFS2020 installation

Just to expand on the Addons Linker recommendation...  MSFS2024 will still look for its files in its Community folder, but you can use the linker to link any number of addons that are in your MSFS2020 folders to the new Community folder, without copying or moving them.  Works like a charm.

What Bert said. The GB of addon 3rd party data thus needs to only reside in one folder. And from there only the AOL links need to be placed into 2 separate community folders. Links take up almost no space.

I've got more than 300GB of addons linked using Addons Linker. Trying to avoid linking addons that are not officially compatible yet. 

https://fselite.net/content/our-microsoft-flight-simulator-2024-compatibility-list-is-live/

Does this apply to marketplace scenery also? I have some airports from MP of 2020 but I don't see them working / loading in 2024...

You might have to disable Asobo Scenery if it's provided and you have an addon for it. The good example is Atelic LPMA. This is now possible with the latest version of the sim directly in My Content.

1 hour ago, GEKtheReaper said:

Does this apply to marketplace scenery also? I have some airports from MP of 2020 but I don't see them working / loading in 2024...

Some marketplace scenery are temporarily disabled because the MSFS team is testing their compatibility for MSFS 2024. 

FSimStudio CYVR was enabled for me in the marketplace when MSFS 2024 was released. But as of the last patch, it was then disabled. I suppose it got caught up in the set of sceneries that needed to be tested for compatibility for MSFS 2024.  I have other FSImStudio sceneries that are enabled in the marketplace so I suppose those ones passed the compatibility test.

I don’t blame the MSFS team for disabling FSimStudio CYVR though. Stability is important now in MSFS 2024 so it’s okay if they take some time to test all the add-ons for compatibility. Hopefully within 2 months, it will be enabled again.

Edited December 15, 20241 yr by abrams_tank

10 hours ago, Bert Pieke said:

A random set of my first tests all worked nicely: Samscene3D Vancouver and Toronto,  DD Chicago and Seattle,  Orbx KORS,  Bowerman airport, Nanaimo airport, etc..

Oh, you tested my little Bowerman? Thanks. Cool to hear it works. I did some tests on others of mine small sceneries (not pro at all) and saw these type of issues :

• The new Bing satellite images. The whole scenery is slightly misplaced. It’s more visible on some areas than others. I had to fine tune my whole Agua Dulce. It has been updated on flightsim.to and one version is compatible with both MSF2020 and MSFS2024,
• Some object inexistant: sometimes, even MSFS stocked objects have wrong LoD and appear only at very close distance. I had this issue on (at least) my Le Touquet airport,
• Some fences visual artefact. Frankly speaking I’ve no clue on what to do. I’m in Stand-by mode on here,
• Bigger issue with vegetation’s biome that change and disappear in MSFS2024,. Had to rework on my Marble Canyon. Here again, I’ve published a single version update for both sims.
• DEM issue for example on my Monument Valley airport,
• Taxiway lines disappear or are displayed as light Pink for example at Oceanside. I'm surprise none mentioned this. Maybe it's only on my PC.

Just wanted to share with you feedback from an amateur dev unable to allocate time yet on all these MSFS2020 -> MSFS2024 compatiblity and because I have the feeling that MSFS2024 is still under heavy development and awaiting fix.

Should I be blamed to wait that the platform get stable at least to avoid doing and redoing, running after system updates that we’re barely aware of, for example the server side ones without any Release Notes ?

Edited December 15, 20241 yr by vbazillio

13 hours ago, cianpars said:

Would you mind naming just a few of them?

Sure, although I don't remember the developer names. Here goes: EDDK, LGAV, LEMD, LEBB, LEVX, GCTS, ENBO, EDDH.