Beluga add-on installed in Community folder but not showing up in MSFS aircraft list

A few common “Community folder” gotchas to check

This usually comes down to (1) the add-on not being in the actual Community folder MSFS is using, or (2) the folder structure is one level off after unzipping.

1) Confirm you’re using the correct Community folder
MSFS can have more than one “Community” depending on whether you installed from MS Store / Steam and whether you moved the Packages location.

If you’re not 100% sure, the quickest way is to check what MSFS thinks the Packages path is:

1. Start MSFS
2. Go to Options > General > Data
3. Open Rolling Cache settings and note the path shown there (it’ll be under the same “Packages” area)
4. From that same base path, you should see a \Community folder next to \Official

Then make sure the Beluga folder is in that Community, not another one you happen to have on the drive.

2) Check the folder nesting (this is the #1 cause)
After unzipping, it’s very common to end up with:

Community\Beluga\Beluga\manifest.json

…but MSFS needs the aircraft package folder to be the one that directly contains the manifest/layout files, like:

Community\Beluga\manifest.json
Community\Beluga\layout.json
Community\Beluga\SimObjects\Airplanes\...

So open the Beluga folder you dropped into Community and confirm that manifest.json and layout.json are right there at the top level.

3) Make sure it’s not sitting in a ZIP or blocked by Windows

1. The package must be extracted (MSFS won’t read a .zip sitting in Community).
2. If you downloaded it from the internet, right-click the .zip (or the main folder after extraction), go to Properties, and if you see an Unblock checkbox, tick it and apply.

4) Rule out a simple conflict/cache issue
If you have any other Beluga/related livery packages, temporarily move them out of Community to avoid name collisions.

Also, a full PC reboot isn’t required; what matters is that MSFS fully restarts. Make sure MSFS is closed (not just minimized) before re-testing.

Quick questions so I can narrow it down

1. Which MSFS version/install type are you on (MS Store or Steam)?
2. What is the exact folder name you placed in Community, and does it contain manifest.json at the top level?
3. Do you see the Beluga package listed in MSFS Profile > Content Manager at all?

If you can paste the top-level contents of the Beluga folder (just the filenames you see when you open it), I can tell immediately if it’s a nesting/structure issue.