Yesterday I few all over the place. My Ch Products yoke, pedals and throttle quadrant worked great. As well, my Saitek panels. I went to fly this afternoon and the yoke assignments were wonky. I.e., the pedals were not working at all and the yoke was controlling the rudders. I have no idea what changed.
I went to Options–>Controls and the screen is now showing a spinning icon and will not load. As well, when I go to quit the app to the desktop, it’s hanging on close. It never closes and I have to kill it through Task Manager.
I will be very grateful to anyone that can help me with this. Something seems to have been corrupted and I feel like the game needs to be reinstalled to get this all to work again, but I just don’t know how I would go about doing that.
Very frustrating when finally you get things working as you want them to and this happens…
Thanks,
Rick
I too have this very issue, Controls only shows loading, and trying to quit to desktop requires killing it in task manager. It was working fine last night. Any help would be appreciated.
What I have found so far is that you can delete the following directory -
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs
The next time you start the game it will try to sync with whatever settings are stored in the cloud. If you catch it quickly enough, you can stop it and it will walk you through a clean setup without having to reinstall the game.
The only problem is that for some reason, my new settings are not overwriting the ones stored in the cloud. So, the next time that I open the game the settings are overwritten.
This is incredibly frustrating. If they corrupted people’s settings they should just come out and say so and fix whatever needs to be fixed (or cleared from the cloud) so that we can perform a fresh reconfiguration.
This has all been working fine for me since day one and all of a sudden it’s not working. My guess is that it’s something on Microsoft’s end that is broken.
BTW, Zendesk ticket has been opened and so far no response.
Thanks for the info, I will also open up a ticket. I have to think that it is probably happening to more people, but they may not have discovered it yet since they may not have gone into Controls recently… Thanks for the update.
GaloreAlarm5372, I went to the directory you mentioned, but instead of deleting the directory, I went into the directory and deleted the sub-directory [t] which had nothing in it. I restarted the sim, went to options/controls, and it loaded all of my peripherals. I exited that, shut down the program to desktop, and it exited without hanging. I then looked back at the directory wgs, and the [t] sub-directory was back again with nothing in it. I left it there this time, restarted the sim, and all worked well again. I don’t know if that fixed it, or if as you theorized it was some sort of issue on the MS end, or maybe none of the above, but for now it’s working for me. I’ll let you know here if that changes.
Thanks Flyrduatc, but that procedure didn’t work for me. I’m dead in the water at this point, which really stinks. I really like the sim, even with it’s very obvious issues.
@Flyrduatc, I think I finally have it fixed. I contacted Xbox Live Support and the very helpful guy there had me update the Microsoft Store app. In there there was an update waiting to be installed for “Gaming Services”. I was skeptical at first, but I cleared the entire wgs directory again and restarted. I let the sync do it’s thing and voila all was working again! One thing to note was that AFTER the update and during the restart of MSFS I received a firewall warning for flightsimulator.exe. I let it go through my firewall again. This may have had something to do with it as well, but the files stored on the cloud and populating the wgs directory seemed to make it there OK. At any rate, thanks for the help.
@GaloreAlarm5372, thanks again for the update. Now that you mention it, I did get that update on one of my reboots. Mine as well seems to be doing great. I appreciate your efforts and your time sharing your results. It’s great when we in the community can help each other out. Zendesk still hasn’t responded, but I went ahead and closed out my ticket saying that the community was able to solve the issue.
1 Like
That must’ve been it then! Very strange. I think the folks that didn’t see this issue must have had that update auto install.
Thanks to you as well for helping me work through this. I guess the community forum did its job!