Author Topic: (SOLVED) How can I select my AddonLinker Community Folder  (Read 1200 times)

EdB

  • Newbie
  • *
  • Posts: 27
(SOLVED) How can I select my AddonLinker Community Folder
« on: November 28, 2024, 10:39:00 pm »
Hello All,

I bought O'Hare today off of SimMarket. I installed the Universal Installer and it directed me to a page where I was able to activate it with my key. All good so far. The problem is, the installer wants to place it into my community folder on my C Drive. I do not want it there. I want it in my AddonLinker tree on my F Drive. How can I direct the installer to a different location ie: to my AddonLinker Folder Tree on my F Drive where all my other scenery is loaded?

Thanks in Advance,
Ed

EDIT:I wonder if I can trick it into installing to a folder in a different location by modifying the Community Path in the Usercfg.opt to point to the folder on another Drive or will this result in broken links?

EDIT 2: Strangely enough, this trick worked. If anyone else decides to try this, save the original path or else MSFS will try to install another 169 GB as it will think it's not installed because it can't find it's way to the original community folder.
« Last Edit: November 29, 2024, 03:06:33 am by EdB »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51949
    • VIRTUALI Sagl
Re: (SOLVED) How can I select my AddonLinker Community Folder
« Reply #1 on: November 30, 2024, 01:28:16 pm »
This whole issue was caused because you moved your Community folder alone, and made a link to it with the Addon Linker. This is wrong, and explains why the FSDT Installer was still pointing to the original location: because the UserCfg.opt didn't change with this method.

What must be understood, is that MSFS is designed to move your entire CONTENT folder, not just the Community folder! The Content folder is what *contains* both Community and Official, so the proper way to moving it outside of C: is moving the containing folder (called "Content" in MSFS 2020 and "Storage" in MSFS 2024), and that's even better, because you'll save MORE space on C: since you are moving the whole Content. This is how MSFS was designed to work, and of course it's what the FSDT Installer fully support.

By following this method, you don't need to create links, you just move the containing folders AND update in the UserCFG.opt to show that, so MSFS won't complain about missing 169GB, the FSDT Installer will recognize it, everything will work, because this is the ONE and ONLY official method that you are supposed to use.

For example, assume you have the Content folders here ( MS Store version example ) by default:

C:\Users\YOURNAME\Appdata\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official
C:\Users\YOURNAME\Appdata\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community

Your UserCfg.opt will show this:

InstalledPackagesPath "C:\Users\YOURNAME\Appdata\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages"

It shows the CONTAINING folder, not the individual ones, because MSFS assumes that Official and Community will ALWASY be together! Changing this with Addon Linker links will break this concept, so you'll either confuse the FSDT Installer which clearly complies with the official supported installation method, or you'll make MSFS itself complaining about missing 166GB of stuff, because you broke the relationship between Official and Community.

So you want to move it on F: let's say you made a new folder called F:\MSFS, what you should do is:

- Move all Official and Community INSIDE this new folder, so they'll end up like this:

F:\MSFS\Official
F:\MSFS\Community

- Change the UserCfg.opt like this:

InstalledPackagesPath "F:\MSFS"

This is the correct way to move your CONTENT, MSFS will recognize it, the FSDT installer will recognize it, every other installer will recognize it, and not only MSFS won't complain it's missing 169GB but, you would save an additional 169GB on C:, because you moved Official as well!

And, you don't even have to handle this with the Addon Linker, it will just recognize it as a properly moved Content, and that's it.