Community folder confusion

User Support Hub Aircraft & Systems
,
1

Hi all, hope I’ve got the right subsection for problems with liveries and community folder not working for me.

I have recently done a complete reinstall of MSFS. I have 2 ssd’s…C and E.

OS is on C drive so I asked the installer to install MSFS on my E drive. For some reason the installer still installed most of MSFS on my C drive…I now have 2 community folders. One in C:\Users\gaznj\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages

… and one in E:MSFS

While running the sim, developer mode tells me I it is using the community folder on E.

I have downloaded several liveries and I have followed the FlightsimTo download and install instructions to the letter…Extracting them directly into the Community folder on my E drive…None of the liveries show up in aircraft livery selection in the Sim.

I have also tried extracting them in the community folder on the C drive…still no luck

I’ve probably done something dumb or missed some part of the instructions but for the life of me I can’t get these liveries to work…Can anyone help?

2

I am also having problems on d drive with comunity folder no aircraft showing up when go into mfs This last update appears to be the problem

3

The Community Folder can be found:

MS Store

C:\Users[Your User Name]\AppData\Local\Packages\ Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community

Steam

C:\Users[Your User Name]\AppData\Local\Packages\Microsoft.FlightDashboard_8wekyb3d8bbwe\LocalCache\Packages\Community

Custom Install

If you happened to use a custom location for your Flight Simulator installation, then proceed there. Example: F:\Flight Simulator\Community\

Still can't find it?
  • While running MSFS 2020 do the following:
  • Go to Options / General
  • Click on Developers which you will find at the bottom of the list on the left
  • Switch Developers Mode on
  • On the Dev Menu on top select Tools > Virtual File System
  • Select Packages Folders > Open Community Folder
2 Likes
4

Thanks for that but I have no problem finding it, the problem I have is making it work as it should.

Is it my installation, is it a general issue for folks, is it a known issue?

…all these questions :slightly_smiling_face:

5

Check your usercfg.opt file. At the bottom of that file there will be an entry specifying where it is looking for the packages folder.

1 Like
6

Thanks for that. Worth checking. I found the file and the line reads:

InstalledPackagesPath “E:\MSFS”

Since my Community folder is in my E drive I assume this is correct.

Here’s my folder. It’s the two middle files that do not work.

Com Folder
Com Folder980×458 45.7 KB

7

I have my packages folder outside the default installation location because I joined the beta program. It keeps me from losing things when releases go from beta to GA. I just have to remember to chage the path whenever Microsoft releases an update. I have my packages installed in "C:\MSFS_2020" so the line in my usercfg.opt file is InstalledPackagesPath "C:\MSFS_2020\Packages". Within that path I have both my Official folder and my Community folder.

1 Like
8

The path in the User.cfg needs to have the entire Local Cache - Packages folder in the location that is specified.
The Packages folder contains the Official folder (which contains the One Store folder), and the Community folder.
That is probably why you don’t see any aircraft, a lot else must be missing as well.

1 Like
9

check also that the two middle files ( I assume liveries ) aren’t in another folder within the folder. That can sometimes happen when extracting liveries to the community folder. a livery folder containing another folder wont show up. hope this helps as in …>> community / Asobo Klm livery / Asobo klm livery/ for example another thing to check is that the liveries aren’t outdated that will also cause them to not show up

1 Like