May 10, 20224 yr Hi, so before the PMDG 737 I decided to do a full windows reinstall. From before, I had MSFS on a separate SSD drive, away from the Windows partition. But if I install it now (from the Xbox app), it makes a community folder on C no matter what (AppData\Local\MSFSPackages\Community etc). When you install MSFS, you can choose where to install packages. On default that is C drive, but I selected the drive where I wanted to install MSFS. Still, with this solution, it creates all these folders within the C partition (where windows is installed), meaning it will fill up quickly. What is the point of having several locations for this folder??? Brynjar Mauseth
May 10, 20224 yr Part of MFS always ends up in your system partition, but "heavier" content of the "Community" and "Official" folders will be void if you choose to install to another partition / drive. Edited May 10, 20224 yr by jcomm Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
May 10, 20224 yr Author 1 hour ago, jcomm said: Part of MFS always ends up in your system partition, but "heavier" content of the "Community" and "Official" folders will be void if you choose to install to another partition / drive. But it didn't - I directed the MSFS install to another partition / drive, and it still makes a community folder within the C drive (which would end up taking alot of space since the content is copied / located twice). Makes no sense... Brynjar Mauseth
May 10, 20224 yr 51 minutes ago, Fi5kuS said: But it didn't - I directed the MSFS install to another partition / drive, and it still makes a community folder within the C drive (which would end up taking alot of space since the content is copied / located twice). Makes no sense... Well, if the "dummy" Community folder under C:, which I also have in my install, is "loaded" then something went wrong during the install... Strange... Please let us know if / when you find the culprit ! Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
May 10, 20224 yr Author 2 minutes ago, jcomm said: Well, if the "dummy" Community folder under C:, which I also have in my install, is "loaded" then something went wrong during the install... Strange... Please let us know if / when you find the culprit ! I'm going to try this solution: https://forums.flightsimulator.com/t/how-to-change-the-installation-path-of-installed-packages-inc-community-folder/471682/3?fbclid=IwAR1FyjPWPpKJ8ZnYT0te8NyTpQNUFFaaRmxQuQDrEZ4RZWKtOSPuY61LAcA Delete and start over again with fill MSFS reinstall. In short, what the poster suggests is: The Installed Packages (Community and Official ) folders do not need to be on the 😄 drive if you move them to the 😧 or other drive (D:\MSFS). Be sure that UserCfg.opt identifies where these folders are. These folders are taking up disk space on the 😄 drive and are not needed. They can be deleted to free up disk space. Brynjar Mauseth
May 10, 20224 yr 8 hours ago, Fi5kuS said: But if I install it now (from the Xbox app), it makes a community folder on C no matter what (AppData\Local\MSFSPackages\Community etc). When you install MSFS, you can choose where to install packages. On default that is C drive, but I selected the drive where I wanted to install MSFS. Still, with this solution, it creates all these folders within the C partition (where windows is installed), meaning it will fill up quickly. What is the point of having several locations for this folder??? Are you sure that you are not looking at links to the packages files, on the C drive? Is there anything on the drive you designated? My Userconfig.opt file states: InstalledPackagesPath "C:\Users\User\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages" However, the LocalCache entry is actually a link to my MSFS drive.. Bert
May 10, 20224 yr I agree with Bert, given that the custom installation was done correctly. Here are some easy-to-determine stats using right-click and selecting "properties" for folder sets. My custom installation path is on my "D": drive SSD. The links to that and a few other files such as config files and controls profiles are on my "C:" drive. Here are the folder/subfolder stats C:\Users\Owner\AppData\Local\Packages, includes C:\Users\Owner\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\ and all of it's subfolders 3,880 files consuming 276 megabytes. That is it for MSFS on the "C:" drive. A mere 276 MB. My custom install directory is D:\MSFS2020\ 92,770 files consuming 134 gigabytes As I measure those I should point out that my Community folder is included as a subfolder in those D:\MSFS2020\ stats and currently holds only 8 of those 134 gigabytes. Yes, only 8 gigabytes for Community. I use Addons Linker to manage the active contents of my Community folder, keeping in place only what I will be using during a given day or perhaps week. With Addons Linker it only takes seconds to update. My total library of MSFS addons is stored in another set of folders on my "D:" drive and currently totals 412,976 files and 250 gigabyes. So my overall MSFS installation is 384 GB of which only 276 MB is on my "C:" drive. Edited May 10, 20224 yr by fppilot Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
Archived
This topic is now archived and is closed to further replies.