Hey all, probably more of a MSFS question, but just in case it's related to Fulcrum. . . 

 

The January 31 MSFS update is great, except that now every time I shut the sim down and restart, it forgets all bindings to the Fulcrum Yoke and I have to set up both axes and all buttons again.  I've been looking for the yoke configuration file in the MSFS folders and I havn't found it.

1)  anybody but me having this issue?

2)  anybody know where the yoke config file is located, so I can just save a copy of it to drop back in the next time I boot up?

 

 

Mine are in the following folder

Users\username\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\000901FB94F5029A_00000000000000000000000069F80140\

Within that folder are several subfolders, most with a seemingly random name. Each controller profile in MSFS has its own folder there.
Inside these are files without extension but most of them can be viewed with notepad and will contain the name of your profile in MSFS.
Apart from making a backup copy you can directly edit them to make changes to your configuration.

The first possible cause that comes to mind is a problem syncing your profile to the Xbox cloud. That can be difficult to remedy.

I solved that a few years ago (2021) the following way:

Disconnect your network and start MSFS. At some point you will see a message that your profile can't be synced. It's ok to reconnect the network after that. MSFS probably won't start at all if you don't.

Since it couldn't sync your cloud profile you are forced to use the local backup copy instead. Go to the controller configuration and set everything up as desired if it isn't. I suggest that even if it is fine you make a few changes to force your local profile to be modified. This is important because it will cause MSFS to see a conflict between the local and cloud profile which is exactly what we want!

After changing your controller configuration, close MSFS and start it up again, this time with the network connected as you normally would. If all went well MSFS will see that the cloud profile is different from the local one and ask you which to keep. You should keep the local profile which will then be written to the cloud. Hopefully after this the problem will be gone.

Edited February 19, 20233 yr by orchestra_nl