What’s unclear about it?
Check out Top Wish #27
https://msfs-cdn.azureedge.net/wp-content/uploads/2021/09/c38783.jpg
You misintertpreted what I said.
The file system is a base feature of how MSFS works. You’ll of course notice that MSFS exists as an app in the Microsoft Xbox style ecosystem under Windows 10/11. Yes, MSFS retained the simconnect methodology and included WASM and C++ programming API for interacting with other programs from FSX. But, hmm, let’s take a look at all of the controversy around the RXP applications, which can’t work in MSFS anymore because of the changes in interaction with MSFS, hmm, very similarly to how Xbox doesn’t allow external programs to interact.
I’m not a programmer, so I can’t speak exactly to the issues I’m discussing above, but there’s plenty of discussion on this board around this subject if you do a little searching.
My point was, the community folder is not likely to get subfolders, because that is a very base functionality of how the program interacts with the OS, and, if it’s not going to work on Xbox, they are not going implement it on PC.
Anyone who hopes to see the PC version fork from the Xbox version is dreaming. If anything, the program is going to get more “locked down”. I’m obviously not saying they are going to remove the ability of developers to extend the capabilities of the software. But it’s going to follow rules based on the Xbox ecosystem, with some extensions available on PC, that still follow the rules of “sandboxing”. And, when I say “locked down”, what I mean is, the 3rd party developers, in general, would like to see more DRM so they can keep their IP safe.