Connect the stick to the throttle with the PS/2 cable.There should be six in the head of the plug. Make sure the pins are straight and all ok. Check the PS/2 Cable that comes with the controller.May I know what version your X52 has since the title under discussion speaks clearly of Hardware issues? Exactly GUID and Product ID.Before you install, make sure that you have everything connected correctly: Probable a bad contact of the bridge cable between devices and nothing has to do with the difference of the USB 3.0 or 2.0 ports. Your problem with LCD throttle reporting is certainly a problem with your X52. This problem can be solved simply by unlocking the file concerning X52 so that the users themselves without any effort from the developers, or, if they don’t want to unlock the files, they create a compatible one so that they can also use version IDs 0255. For now those who have the X52 ID 0255 are not automatically detected as well as the owners of the Saitek X52 version ID 075. It does not seem to me that with the latest update they have solved the problem encountered with the Saitek X52 version IDs 0255 that many report and send support tickets. Not sure if I should try and install the later ones.Īlso the Throttle lCD doesnt light up using a 3.0 USB but that isnt a FS 2020 issue.””"" It shows the Logitech driver fore the USB as 8.0.116.0. I could edit the bindings to the controls over the last week but could not get them to operate when I flew. ““The FS 2020 update yesterday seems to have fixed this issue. This will probs work for other ‘supported’ controllers with the same issues. Perhaps other files have to me modified for that in order for it to match a picture. Although there is still no device picture on the right like other supported devices. When you plug in now, you should find MSFS2020 gives you a correct default profile for the device with a lot of mappings now in place. Perhaps some USB controllers change things (unlikley) or perhaps the X52 was sold with different IDs depending on age or geo location. I dont know why the ones in MSFS are incorrect. Under the property pulldown, the GUID can be found under ‘Class GUID’ between the curly brackets.Īnd the product ID can be found under ‘Hardware IDs’ - The 4 digit product ID is the numbers after ‘PID_’ and before ‘&REV’ in the first string of the several listed. 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |