Open up properties and then click on the ‘Details’ tab. device (either USB or HID, the IDs are the same so it doesnt matter). In order to find your correct GUID and product ID open up windows device manager.įind your X52 H.O.T.A.S. In my personal case, I had to modify it to:ĭevice DeviceName=“Saitek X52 Flight Control System” GUID=“745a17a0-74d3-11d0-b6fe-00a0c90f57da” ProductID=“0255” This line then needs to be modified to match your hardware ID:ĭevice DeviceName=“Saitek X52 Flight Control System” GUID=“9a117810-f09c-11e7-8002-444553540000” ProductID=“075C” Then edit this file in a text editor of your choice (I used notepad++). Call it Saitek_X52_Flight_Control_System2.xml or something. Then locate the Saitek_X52_Flight_Control_System.xml file and make a copy.
Logitech x52 flight control system install#
I have the steam version but the same will apply for any version, just locatate the input directory in your MSFS2020 install directory.ĭ:\Games\Steam\steamapps\common\MicrosoftFlightSimulator\Inputīut your location upto the STEAM folder is likley to differ. It turns out that the MSFS2020 controller profiles for the X52 has a hardware GUID ID and product ID that does NOT match those of my X52 for keymapping detection. That asside, I still manged to get it working eventully with some file tweaks. Its funny that the latest version of the X52_HOTAS_圆4_8_0_213_0.exe driver package only seems to contain the 8.0.116.0 drivers rather than the 8.0.213.0 drivers that the professional version driver package does. So - I went through the same process as you all and messed about with drivers and several attempts at unplugging and replugging at different stages.
So I had the same issue as all of you with a standard old X52 (not pro).
0 kommentar(er)
