Hi can anyone confirm whether there is a limit to the number of folders you can have in the game’s community folder? I came across flightsim.to and there are sooooo many mods available for download. Hence I am wondering if there is a maximum amount of mods you can install/have in your community folder.
Thanks.
Hilkiah
I never heard of a limit, but the more you put in there the slower loading the sim is going to be. Depending on the quality of the addons, it might become less stable and harder to debug, too. 
no limit but be careful, the more you put in that folder the longer the loading time of the sim will be. My sim now takes a solid 20 minutes to load cause all the mods so I started deleting them to lower my wait time. Hopefully they can some how fix/improve this.
Hence the need for a Manager utility, to only keep active (turned on), the items you want for a given flight.
Like the Scenery Manager in FSX maybe
Certainly, as we have seen after this last patch, a way to disable Community content, would make tracking down Bugs a lot easier
There are folder, file and path name limits. Those are Windows limits and not MSFS. Some paths are pretty long so I imagine people could hit the path name limits fairly easily. The other two though a pretty large though I can’t remember what they are now but the number of addons shouldn’t matter.
Oh, there a file system limits and Windows limits. The Windows limits are much smaller.
You can mitigate the path length limits somewhat if you install the game to top level folder. In other words don’t accept the default install path. I installed to C:\FS2020 so my community folder is only two levels down (C:\FS2020\Community) and very short for a path length. However I have the MS Store PremLuxe version, and I don’t know if you can change the install though for other versions.
something like JSGME? I was going to give that a whirl, but can’t do anything on my rig for the next couple of days. RL/work thingy’s hammering me.
You can also use simlinks to put stuff on other disks or different folder paths.
I have the Steam version, and have mine in F:\MSFS, so it works too.
One thing to watch with the filename-path length limit.
If you have a .zip file, and are trying to expand it into community, sometimes it may fail with the filename too long error. (seems to be a “feature” of the W10 decompression program)
However, if you unzip it in a lower folder, ie c:\ZIPTEMP say, then it will typically decompress fine, and then you can copy (move) the result to the community folder, and not get that long Filename error, that occurred when in the unzip program.
Happened to me a few days ago – the above method worked fine.
For now I divide my mods up into numbered Community folders and just rename the one I want to use based on what I want to do.