There are many. The root path to the folder may differ from person to person. Here is mine:
%LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\SystemAppData\wgs\00090000025CC6EC_0000000000000000000
Inside this are a bunch of other randomly named folders, and inside each of those is another file named “container.x” with x being a number, and one other file with a long random string of letters, and numbers. To make it fun this file changes its name when the sim is launched, or rather it did in 2020, and I’ve not observed that process in 2024 yet.
Here is a tree view of that folder:
tree /F
Folder PATH listing
Volume serial number is E0F5-3DC8
C:.
│ containers.index
│
├───00EBC8207E9549E78EF9B9361346202E
│ container.17
│ DA85CBF428FC41BEBA4E223452F72F1A
│
├───1ECA0A684706450B900332DBD6589B01
│ 2AC3567FFF064AA1BA73676AAF8D41B6
│ container.7
│
├───4A54D6EA73E24CF1B3395B1D29DF5E5F
│ C99C03D02C664122B8A2D392D31A16F9
│ container.1
│
├───55D6346ADC394BABAB50112032348337
│ container.1
│ E79101382C984CBE87EE3EE9B6F5B656
│
├───5887F15B178E40088F9D51E008829E93
│ C1A2E854F40D4FDDA1B4B8C4D0D22DEE
│ container.1
│
├───92E2F686C9D04D0FB76243FA5216C773
│ 86B4DBEE36B24969B9FC0225699EF7A4
│ container.4
│
├───B8CB3A4ACC4A43C388DA8F26BE34947C
│ 932B6A97D4E24E20AF742B267204EDAF
│ container.1
│
├───C77204C7B104422BBEE13FFF60026FCC
│ 4971B1690022427D80EDB1AFAFE8CE11
│ container.1
│
└───D0E21BAA805D48E49FF1FAEA81FAB418
445C3CCF642E4DEEBA1D50ECD33E0383
container.1
You can’t discern what file is for what device from the outside, and not all of them are for controllers. For example, the filename below is for my TQ6+.
E79101382C984CBE87EE3EE9B6F5B656
I’ve had a quick play with some PowerShell code to pull useful information out of these files. The first three lines are breaking the XML parsing, so I made a copy of the file, and it was then imported okay. In the example below “tq6.xml” is a copy of the file above on my desktop with the first three lines removed.
You can skip the first “n” lines with this command added:
$tq6xml = [xml](Get-Content .\E79101382C984CBE87EE3EE9B6F5B656 | Select-Object -Skip 3)
$tq6xml = [xml](Get-Content .\tq6.xml)
$keys = $tq6xml.Device.Context.Action.Primary.Key
foreach ($key in $keys) { $key.ParentNode.ParentNode.ActionName;$key.Information;$key.InnerText}
It’s ugly, and could do with some tidying, but it gives me this:
KEY_AXIS_MIXTURE_SET
Joystick R-Axis Y
786
KEY_AXIS_MIXTURE2_SET
Joystick R-Axis Z
802
KEY_PROP_PITCH1_AXIS_SET_EX1
Joystick L-Axis Z
1058
KEY_PROP_PITCH2_AXIS_SET_EX1
Joystick R-Axis X
770
KEY_THROTTLE1_SET
Joystick L-Axis X
1026
KEY_THROTTLE2_SET
Joystick L-Axis Y
1042
It lists the simvar, the physical device bound to it, and its value. Actually, I’m not 100% sure what that value refers to, because I see a similar thing in the keyboard file, so it may be ome arbitrarily assigned value withing the controller configs in MSFS, possibly a unique value? Yes, that seems likely. Looking for the number “123”, I see that all refers to the F12 key.
