When I installed KORD for MSFS2020 it just allowed me to install an addon manager folder to the NVME ssd where my MSFS2020 installation is located. I was keen to have all my MSFS2020 stuff on the same very fast drive. My P3D4.5 and P3D5.3 installations are on their own separate SSD drives. I guess the key in registry that prevents another addon folder being created didn't do its job on that occasion.
Sorry, but that's not possible, the only possible way this could have happened is if you uninstalled FSDT and reply YES to the question about removing the Addon Manager, and this CLEARED the registry key, so you were allowed to choose a new one for the MSFS installation.
This, or you manually removed the key, to force the MSFS Addon Manager to let you choose a different folder freely.
Or, you created a new user account on that PC, because the key is by-user, not by-system.
After you cleared the registry key, your old P3D install, while still having all files and still having all the sceneries working, was now ignored by the FSDT Live Update so, from its point of view, even if your P3D sceneries were still working, because their add-on.xml were still valid and pointing to their actual locations, it was now frozen in its last state, because the update would now consider only the new MSFS location.
But keeping FSDT stuff on my PC is just becoming too complicated.
You are making it complicated, because you fixated on having "P3D stuff" and "MSFT stuff" separated, as this would make ANY difference for something that is ALWAYS installed OUTSIDE THE SIMULATOR, like FSDT.
If you stopped considering the products "by sim", and started to reason as "the whole FSDT stuff", you wouldn't even tried to separate them, because it doesn't really many any sense, when they our outside the sim.
Other developers seem to manage things in a less convoluted more streamlined way and their addons continue to work over successive P3D updates with little effort on my part.
That's not the case. Other developers are making it convoluted, by doing strange things like installing something inside the sim, something outside. Or using the add-on.xml to point to something inside the sim. Or using the add-on.xml without an absolute path, putting all their stuff in the Documents folder, instead of JUST the add-on.xml
THESE questionable methods must have lead you to assume you should "separate by sim" because yes, developers doing all these convoluted things forced you to think this way, when in fact, the reality is the opposite: the PROPER way we use the add-on.xml, which is:
- DO NOT install ANYTHING into P3D
- Place ONLY the add-on.xml in the Documents folder, but use absolute paths to ANY drive you want.
This is PRECISELY what allow you to "have the addons continue to work over successive P3D updates with NO effort on your part" ZERO effort, because the place where you install "THE FSDT STUFF" is not related in any way to the simulator used, and P3D has been *designed* to have add-ons surviving an complete simulator reinstall, but not all developers use this feature in the proper way, which I assure you it's the one we use. There are *whole* P3D Add-ons ( Lorby's Addon Manager, for example ) to achieve exactly what we already do BY DEFAULT!
Clearly, this means the whole issue of wanting to keep MSFS and P3D stuff is completely irrelevant, when the folder is completely separated from the simulator. What's simpler than:
- EVERYTHING from FSDT installed in a SINGLE place, the main Addon Manager folder
- The P3D products being visible because their own add-on.xml, placed in the Documents\Prepar3d Add-ons folder, pointing to Addon Manager folder, regardless where it is
- The MSFS products inside the Addon Manager\MSFS folder, with just a Symbolic Link to the Community folder so, again no Community folder is being harmed here. There are whole MSFS ADD-ONS (Addon Linker ) made just to achieve with other products what we already do BY DEFAULT ( creating a Symbolic Link to the Community folder to let you install the scenery everywhere )
If Cloudfare does work, or rather does not work, as you describe then it puts a big roadblock on the efficient transfer of content over the internet - what a bummer! Has it always been that way?
Of course it has, that's the way a CDN works but, after a day or to, the whole world gets all the latest files, and all complains stops immediately.
Developers that don't use CDNs have their own server down or incredibly slow for a few days after a major release, people complain ( or they just say "wow, that product launch was a success!!" ) but the end result is the same: affected users still can't get their download for a day or two, then the problem disappear by itself once the traffic goes to normal levels.