I had no intention of spreading misinformation, and I’m sorry if I did. My point was, your software used to pass information between FS and an external program directly as it were, and that’s not allowed anymore. Essentially for “security” reasons, in this case, as opposed to a UI reason which I implied above for managing a multiple folder system for storing packages. But, I imagine, also, that there are “Xbox related” file system /VFS reasons as well that pushed them to choose not to have multiple “Community” folders as part of the MSFS file system structure, as FSX used to have.
(I put “Xbox related” in quotes, because, I imagine, Microsoft is looking to make Windows itself similar to Xbox OS as it moves forward)
Is that incorrect?
(I did not mean to get into any business related reasons that got in the way of implementing RXP products in MSFS. I’m sad discussions fell apart, and I do hope that gets worked out/resolved someday. And, thanks for the links to the discussion related to the subject.)
(I’m also assuming that “Asobo” couldn’t have been so “stupid” as to not realize users would be managining hundreds if not thousands of addon packages; I’m assuming there is a technical reason for a single “Community” folder.)