I come to bring my stone to the building.
After multiple searches, tests, total re-installations (OS + FS2020), the problem was still present:
when the number of 1028 was exceeded, (even only by 1), whatever module I installed, it was the return of infinite “spinning circle” when checking for updates.
You should know that I only have paid modules on the in-game store of FS2020 (so I don’t have to worry about updates), and therefore it is the “Official/OneStore” directory which is loaded and “Community” is left empty.
These modules therefore come in addition to the standard modules and files installed by Microsoft (about 800 files with SU11)
During one of my tests, I moved all these modules into the “Community” directory → no change, still the “Spinning Circle”.
On the other hand, during my research, I realized that in fact, it was the number of “manifest” files that is the problem:
Indeed, I added a module beyond the 1028, and I renamed its “manifest” file of this module, and like magic, the “spinning circle” disappeared and FS2020 started.
Of course the module in question was not loaded.
This means that it is not the number of module directories that is in question, but really but a limitation (voluntary or not) of the number of modules referenced by their “Manifest” files.
With SU11, the number of authorized modules increased from 1028 to 1189, but beyond that, the problem reappears.
The consequence of this limitation is that I will no longer buy modules (planes, scenes, liveries, etc.), as long as this problem exists.
And although “AddOnLinker” is a great piece of software, I don’t want to spend my time constantly switching from one configuration to another as soon as I want to change part of the world.
Multiplied by the number of FS2020 users, this could represent a great financial loss to Microsoft and all publishers.
So, it is urgent for everyone that they solve this problem.
I have a PC with several Tera-bytes of disks and 64 GB of ram, this is not a hardware problem.
I read somewhere the following method to work around the problem:
During the “spinning circle”, simply disconnect physically, (or logically by the Windows network manager), the network connection, this will display an alert window saying that the connection is lost.
This window must be validated.
The loading will then start.
At this point, just re-establish the connection and simulator loads and run.
Unfortunately, the disadvantage of this method is that the “Content Manager” cannot perform any updates, but it’s a lesser evil.
To circumvent this last point, it is enough to use “AddOnLinker” while remaining under the limit of 1028 (or 1189 with SU11), to load the simulator in normal mode, to perform the updates in the “Content Manager” to loaded modules, and to do so for all modules.
I know, it’s a bit heavy, but it works, waiting for better.