Hi all,

I installed MSFS2024 a couple of days ago. The first thing I did was to move the Community folder to different drive, which I verified in the UserCfg.opt file. Then I installed all the compatible 3rd party airports I own. However, these airports don't show up in game. Do I have to install any bespoked airports made by Asobo? Has anyoneo had a similar problem? What did you do to fix it?

Thanks!

do you see your community folder airports under My Library? Else they seem to be not recognized. as per "bespoken ASOBO airports", do you mean the default detailed airports? they should be there by default. but in My Library you see what is available (and streamed) and what not

I don't see anything in the Community folder under My Library. This is very strange because the folder location is the same in My Library and UserCfg.opt. I tried moving the Community folder to another folder and the result is the same. All airport buildings are generic even though I installed iniBuilds YBBN.

Anything 'official' is now sitting in "StreamedPackages" from what I can tell. Nothing from Asobo ever went in the Community folder, that went to the "Official" folder in 2020. 

Though I can't say why your airports are not showing up. Have you tried putting them in the default folder in AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community and see what happens?

23 minutes ago, Sethos said:

Anything 'official' is now sitting in "StreamedPackages" from what I can tell. Nothing from Asobo ever went in the Community folder, that went to the "Official" folder in 2020. 

Though I can't say why your airports are not showing up. Have you tried putting them in the default folder in AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community and see what happens?

It's really odd. I created another Community folder and changed the link to F:/Folder/Community. Then iniBuild's YBBN worked. But when I located KPSP, the generic scenery showed up. It's very very strange. I'll try the default location next, but I'd rather have the Community folder in a storage drive.

8 minutes ago, mrcultureshock said:

It's really odd. I created another Community folder and changed the link to F:/Folder/Community. Then iniBuild's YBBN worked. But when I located KPSP, the generic scenery showed up. It's very very strange. I'll try the default location next, but I'd rather have the Community folder in a storage drive.

Saying this purely as something you could test, for the hell of it, if nothing else works. If you find using the real default Community folder in AppData/Roaming works and you still want the actual files on the F: drive, look into playing around with a symbolic link. Essentially a shortcut folder, so 2024 thinks your Community folder is sitting in AppData/Roaming but that folder is linked to your F: drive, so all files are saved there.

So instead of specifying a Community folder path, you're just tricking it a bit. 

2 hours ago, mrcultureshock said:

It's really odd. I created another Community folder and changed the link to F:/Folder/Community. Then iniBuild's YBBN worked. But when I located KPSP, the generic scenery showed up. It's very very strange. I'll try the default location next, but I'd rather have the Community folder in a storage drive.

Is KPSP the enhanced 2024 version? Also remember that since we cannot remove the default scenery it could be 'hidden' under the default.

It is important to note that wherever you choose to place your Community folder, the choice must be to the containing folder, like this:
 

Quote

InstalledPackagesPath "Your chosen Drive:\Your chosen folder"

 

If, as many people seem to do, you set the path as InstalledPackagesPath "Your chosen Drive:\Your chosen folder\Community", the result will be
Your chosen Drive:\Your chosen folder\Community\Community, which opens up the possibility of installing into the wrong one.

For the record, the Axonos version of KPSP, when placed into the correct Community folder, works seamlessly.

I've solved the issue. I went back using the default Community location and used Symbolic Links. Still, I see some oddities. Under Marketplace/My Library, if I click on "Community", it'll show up blank. If I check the download folder directly after that, I see "Xxxxxx". I guess these are just bugs until Asobo fixes them.

50 minutes ago, mrcultureshock said:

I've solved the issue. I went back using the default Community location and used Symbolic Links. Still, I see some oddities. Under Marketplace/My Library, if I click on "Community", it'll show up blank. If I check the download folder directly after that, I see "Xxxxxx". I guess these are just bugs until Asobo fixes them.

Why are you creating your own symbolic links instead of using Addons LInker?  I have over 300 USA and Caribbean airports in MSFS 2020 and I have experienced only one so far that does not show perfectly in MSFS 2024.  I am using one common addon library and accessing that one common library from the recently released pair, Addons Linker 2020 and Addons Linker 2024.

Add on aircraft and liveries, and 3rd party avionics (PMS, TDS) are a totally different matter however.  Appears nothing was done to embrace what already existed, and even WTs endorsed efforts have produced flaws. The proverbial definition of NIHS (not invented here syndrome). Totally ignores great developers who clean up deficiencies in the sim, as well as ignoring the needs and wishes of a large installed base of users.

And Asobo believes their most recent failing was the flawed rollout issues.

Sorry Asobo. Now that we have finally and successfully installed 2024, we are well past that and into "today".  What is in store is more than just mop up.  More like a major case of "catch up" to what already existed.

History certainly has a way of repeating itself.

Edited December 6, 20241 yr by fppilot

3 minutes ago, fppilot said:

Why are you creating your own symbolic links instead of using Addons LInker?  I have over 300 USA and Caribbean airports in MSFS 2020 and I have experienced only one so far that does not show perfectly in MSFS 2024.  I am using one common addon library and accessing that one common library from the recently released pair, Addons Linker 2020 and Addons Linker 2024.

Add on aircraft and liveries, and 3rd party avionics (PMS, TDS) are a totally different matter however.  Appears nothing was done to embrace what already existed, and even WTs endorsed efforts have produced flaws. The proverbial definition of NIHS (not invented here syndrome). Totally ignores great developers who clean up deficiencies in the sim, as well as ignoring the needs and wishes of a large installed base of users.

And Asobo believes their most recent failing was the flawed rollout issues.

Sorry Asobo. Now that we have finally and successfully installed 2024, we are well past that and into "today".  What is in store is more than just mop up.  More like a major case of "catch up" to what already existed.

History certainly has a way of repeating itself.

I really long for the past days of RXP and other developers who brought this passion to such great heights. Certainly rewarding to see the "break-through-it-all" efforts of HiFi and REX.

 

Edited December 6, 20241 yr by fppilot

FWIW all my 3rd party sceneries are working using my self defined community folder and addon linker for FS2024.

-B

6 hours ago, mrcultureshock said:

I've solved the issue. I went back using the default Community location and used Symbolic Links. Still, I see some oddities. Under Marketplace/My Library, if I click on "Community", it'll show up blank. If I check the download folder directly after that, I see "Xxxxxx". I guess these are just bugs until Asobo fixes them.

Not bugs.

Set up correctly, this is what happens.

Once that's done all the mainstream installers and the Addons Linker for MSFS 2024 will see the Community folder and put either files or links into it.
As mentioned, no need at all to intervene manually. 

 

Edited December 6, 20241 yr by Reader