Continuing the discussion from No Simulators detected:
Thank you both for your suggestions. Unfortunately the problem remains unresolved. The original location of MSFS is:
C:\Users\ronha\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe
In this folder there are the following folders: AC, AppData, Local Cache, Local State, Roaming State, Settings, SystemAppData and TempState.
Each of these now “empty” folders has a link that connects them to their populated equivalents located on the “S” drive. The S drive has two folders:
-
WindowsApps that is owned by Trusted Installer and I assume contains MSFS programme and executive file etc. Without taking ownership I have no current access to its internals.
-
WpSystem A subfolder of WpSystem is AppData that itself contains: Local which in turn contains Packages that contains Microsoft.FlightSimulator_8wekyb3d8bbwe.
Microsoft.FlightSimulator_8wekyb3d8bbwe contains the linked populated folders: AC, AppData, Local Cache, Local State, Roaming State, Settings, SystemAppData and TempState.
I did edit the UserCfg.Opt file pointing it to S:\WindowsApps on the assumption, as mentioned above, that it contained MSFS installation, rebooted and retried Navigraph NavCenter with no success.
Since I suspect that the simulator writes UserCfg, I started it and was faced with an unexpected “update” of files pointing to Installed Packages Path S:\ WindowsApps. This I did not do and exited the simulator (which has been and is working normally).
I then renamed UserCfg to make it unusable and restarted MSFS. Sure enough, UserCfg was recreated with exactly the same last line as it originally had viz.,
InstalledPackagesPath C:\Users\ronha\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages
So, I remain entirely flummoxed. I have no idea why what was a fully functional NavCenter now suddenly cannot see MSFS, not having changed anything, and I have no idea what governs where NavCenter looks for the root installation directory, why it should be different to that established by the Microsoft package or what to do next (sacrifice a mock chicken maybe?).
Ron
Just an addendum. In the Community folder there are two separate folders of interest that appear to me to be related to the preceding Airac cycle since they are dated 11/26/2022.
One is named navigraph-navdata-base. It contains folders and two files:
ContentInfo
Scenery
layout.json
manifest.jason
Weirdly, ContentInfo contains two folders:
Navigraph-navadata containing cycle.json and a jpeg thumbnail
Navigraph-navdata-base containing ContentHistory.json
Why there is this folder structure with its apparent duplication of folder name I’ve no clue.
The second folder of interest is named navigraph-navdata. It also contains folders and two files:
ContentInfo
Scenery
layout.json
manifest.jason
This Contentinfo folder contains folder Navigraph-navdata in which there is ContentHistory.json and the jpeg thumbnail as above.
The remaining folder Scenery, and the two files are identical to those above.
I realize this is a lot of information to process, for which I apologize. I’m not entirely sure of its relevance, save that it may show NavCenter was working. Do these folders make any sense and what would happen if they were removed? If I tried another uninstall of NavCenter without them would that replace them?
Ron