On 8/21/2020 at 9:25 AM, Kabouik said:

The problem appeared again, and just replacing joy.cpl was not enough. What worked is:

 

1. Devices and Printers

2. Right click on X52 Pro

3. Properties, Hardware tab, click the Properties button while the HID line is selected

4. Change settings

5. Driver, Update driver

6. Browse my computer, Let me pick from a list, and pick the only X52 HID occurrence

7. And replaced joy.cpl as described above, not sure if that was mandatory or not

 

This was after installing X52_Professional_HOTAS_x64_8_0_213_0.exe but I guess this is not necessarily a good idea, as now my hardware driver in the properties tab has "Driver date: 2017-04-20" and "Driver version: 8.0.121.0", so maybe the later updates (X52_Professional_HOTAS_x64_8_0_213_0.exe was released in September 2018) break things. We'll see how long it holds.

I wonder if there is a way to freeze things in that state and prevent updates.

Okay, that was still not it. Sometimes Windows was still failing to open joy.cpl with this, and in those cases, FS2020 doesn't see my X52 Pro. I tried something else:

1. Add or remove programs, uninstalled the X52 software. Not sure if necessary.

2. Admin command prompt

3. sfc /scannow

This detected joy.cpl as corrupted and refetched it from the MS Store. I think now it works, hopefully it'll keep working for more than two sessions.

Edited August 22, 20205 yr by Kabouik

ATTN:  LOGITECH CONTROLLER USERS!  Microsoft Flight 2020 (MS20)  has bindings already installed for most of their controllers.  The method used to find those bindings is such.  Prior to launching FS20 unplug it from the USB port.   What till the game completely load then Click on OPTIONS at the top of the screens.  Once there, click on CONTROL.  Once that opens PLUG IN THE CONTROLLERS.  Now, a screen will pop up with DEFAULT or CUSTOM.   Select DEFAULT (selecting custom will show the controller but no bindings)  Once  you select DEFAULT the screen will pop up showing your LOGITECH controller with a list of BINDINGS under it.

I hope this helps.

Logitech X52 PROFESSIONAL HOTAS

So I found something out the hard way tonight. Hopefully this helps anyone using the profiler software vs keybinds. I haven’t used a keyboard with a number pad in a while. Plugged one back in to program the profile software with some of the drone etc keybinds that are used when num lock is on. If you accidentally turn num lock off then switch back to a TKL the controller actually send the key and since num lock is off you get the non num lock command.
 

I assumed it sent whatever was originally put in the profile but no num lock has to be on whether you have a keyboard that can toggle it or not if the keybind is one of the numbers vs other functions the keys can do. I spent 30 minutes figuring this out and assuming it was a steam version issue vs the game passed Xbox one I was using previously. finally opened up notepad and realized what was going on. 

21 hours ago, ElektroShok said:

ATTN:  LOGITECH CONTROLLER USERS!  Microsoft Flight 2020 (MS20)  has bindings already installed for most of their controllers.  The method used to find those bindings is such.  Prior to launching FS20 unplug it from the USB port.   What till the game completely load then Click on OPTIONS at the top of the screens.  Once there, click on CONTROL.  Once that opens PLUG IN THE CONTROLLERS.  Now, a screen will pop up with DEFAULT or CUSTOM.   Select DEFAULT (selecting custom will show the controller but no bindings)  Once  you select DEFAULT the screen will pop up showing your LOGITECH controller with a list of BINDINGS under it.

I hope this helps.

Logitech X52 PROFESSIONAL HOTAS

Tried this...it worked to a certain extent. Switched to default but the assignments were essentially just what I had set them too. Didn’t seem to load any presets even in default settings. 

On 8/20/2020 at 8:26 PM, usgiorgi said:

Did it have preassigned values? As in, were you able to fly the plane without having to manually map the controls? 

No, I had to set everything up sadly. I got it to a working state now, but am not sure whether I forgot really useful functions. I still haven't mapped all keys, I'm keeping some free in case I later realize I need more commands on the controller.

Spoiler

 

On 8/21/2020 at 2:41 PM, Pottymoose said:

Hello there!

So I had the same issue as all of you with a standard old X52 (not pro).

I goggled for the issues and found your forum and this post which I was monitoring. Seems Ive now found a solution so thought Id sign up  to this forum and create a post to help you all out. Its my first post so a mod needs to approve it. Hopfully you'll see this all soon......

 

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. Its funny that the latest version of the X52_HOTAS_x64_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.

That asside, I still manged to get it working eventully with some file tweaks.

 

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.

 I have the steam version but the same will apply for any version, just locatate the input directory in your MSFS2020 install directory.

For me this was the steam directory:

D:\Games\Steam\steamapps\common\MicrosoftFlightSimulator\Input

But your location upto the STEAM folder is likley to differ.

 

Then locate the Saitek_X52_Flight_Control_System.xml file and make a copy. Call it Saitek_X52_Flight_Control_System2.xml or something.

Then edit this file in a text editor of your choice (I used notepad++).

This line then needs to be modified to match your hardware ID:

<Device DeviceName="Saitek X52 Flight Control System" GUID="9a117810-f09c-11e7-8002-444553540000" ProductID="075C">

In my personal case, I had to modify it to:

<Device DeviceName="Saitek X52 Flight Control System" GUID="745a17a0-74d3-11d0-b6fe-00a0c90f57da" ProductID="0255">

 

In order to find your correct GUID and product ID open up windows device manager.

Find your X52 H.O.T.A.S. device (either USB or HID, the IDs are the same so it doesnt matter).

Open up properties and then click on the 'Details' tab.

Under the property pulldown, the GUID can be found under 'Class GUID' between the curly brackets.

And 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.

 

I dont know why the ones in MSFS are incorrect. Perhaps some USB controllers change things (unlikley) or perhaps the X52 was sold with different IDs depending on age or geo location. Either way, this works.

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. It did for me. Although there is still no device picture on the right like other supported devices. Perhaps other files have to me modified for that in order for it to match a picture.

 

 

 

I hope this helps you all!

PS. Im sure this will also work with other 'supported' controllers that have the same issues.

 

 

 

 

 

Created an account after finding this thread.  I'm almost certain this is the issue I'm having as well, but I cannot access these files with the version from the Xbox app as Windows says I do not have permission.  Does anyone have any idea how to bypass or get around the file restrictions?

50 minutes ago, ConanThePilot said:

  Reveal hidden contents

 

 

 

Created an account after finding this thread.  I'm almost certain this is the issue I'm having as well, but I cannot access these files with the version from the Xbox app as Windows says I do not have permission.  Does anyone have any idea how to bypass or get around the file restrictions?

As per the second post it should be located here...make sure hidden files are showing (show hidden files in windows 10). 
 

C:\Users\bruyn\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\000900000086B2C1_00000000000000000000000069F80140\B04F0D41FAE24D70A734D1D8211AC716

 

where ‘brunt’ is your username

8 hours ago, TypeR said:

As per the second post it should be located here...make sure hidden files are showing (show hidden files in windows 10). 
 

C:\Users\bruyn\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\000900000086B2C1_00000000000000000000000069F80140\B04F0D41FAE24D70A734D1D8211AC716

 

where ‘brunt’ is your username

The quoted post points to a different folder:  D:\Games\Steam\steamapps\common\MicrosoftFlightSimulator\Input

The equivalent for the Xbox store version of the game for me is here:  D:\WindowsApps\Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe\Input

I do not have permission to edit these files though.  If somebody could upload a copy of the default Saitek_X52_Flight_Control_System.xml file I think that would help me.

Hi all,

I've got my X52 working but the throttle is basically only 0% or 100% it is really hard to get anywhere in between - I've tried playing with the sensitivity but doesn't seem to be making any difference.

Any suggestions?!

On 8/25/2020 at 10:26 AM, maxpax444 said:

Hi all,

I've got my X52 working but the throttle is basically only 0% or 100% it is really hard to get anywhere in between - I've tried playing with the sensitivity but doesn't seem to be making any difference.

Any suggestions?!

Did you assign the correct axis?  Assuming you're talking the original and not the Pro mine at least is "Joystick L-Axis Z" in the controls section of the sim.  There are other similar named functions that act like buttons instead of an axis.  Just thinking maybe you accidentally assigned those.  Only other thought is go into the windows settings for it and check the deadzones and make sure it looks like it's working correctly.  The window you get if you go to the Win10 Search Box and type in "Game Controller" and click on "set up USB game controllers" then "properties" for the X52.

Hi.

Another one here with an unmapped Saitek X52....

after reading some threads (including this thread so far...), I concluded that the main issue is that the GUID and ProductID values are wrong in the "Saitek X52 Flight Control System.XML" in C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe\Input.

i'm trying to change the file, but of course, i don't have the permissions to do so. even after watching every Youtube video on how to get full control on that folder...

I've also tried placing the edited XML in C:\Users\maste\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\0009000007888DDB_00000000000000000000000069F80140   sub-folders...

Anymore thoughts ???

 

thanks to pottymoos post. for all the info.

 

Edited August 26, 20205 yr by Master_bebe

Just wondering why everyone is trying to get these to show up with default mappings?  You only get one set of buttons that way.  Using the Logitech (or Saitek if you haven't updated) Profiler software you can use the mode switch and get 3 sets of bindings and keep a lot more things out of the keyboard.  You can't do this in the sim.  I tried after switching the mode and of course it just thinks it's the same switch.  I bound buttons in the profiler as well as hat switches 2 & 3.  I bound switch 1 in the sim for cockpit and external view panning, and also the control axes and the slider in the sim itself.

13 hours ago, flyinion said:

Did you assign the correct axis?  Assuming you're talking the original and not the Pro mine at least is "Joystick L-Axis Z" in the controls section of the sim.  There are other similar named functions that act like buttons instead of an axis.  Just thinking maybe you accidentally assigned those.  Only other thought is go into the windows settings for it and check the deadzones and make sure it looks like it's working correctly.  The window you get if you go to the Win10 Search Box and type in "Game Controller" and click on "set up USB game controllers" then "properties" for the X52.

Yea that was the problem, meant to reply here yesterday incase it helped anyone else! I had assigned it to increase and decrease rather than the throttle axis - now assigned to just throttle axis and all working like a charm!

8 hours ago, flyinion said:

Just wondering why everyone is trying to get these to show up with default mappings?  You only get one set of buttons that way.  Using the Logitech (or Saitek if you haven't updated) Profiler software you can use the mode switch and get 3 sets of bindings and keep a lot more things out of the keyboard.  You can't do this in the sim.  I tried after switching the mode and of course it just thinks it's the same switch.  I bound buttons in the profiler as well as hat switches 2 & 3.  I bound switch 1 in the sim for cockpit and external view panning, and also the control axes and the slider in the sim itself.

Great shout! Going to work on setting this up today!

19 hours ago, flyinion said:

Just wondering why everyone is trying to get these to show up with default mappings?  You only get one set of buttons that way.  Using the Logitech (or Saitek if you haven't updated) Profiler software you can use the mode switch and get 3 sets of bindings and keep a lot more things out of the keyboard.  You can't do this in the sim.  I tried after switching the mode and of course it just thinks it's the same switch.  I bound buttons in the profiler as well as hat switches 2 & 3.  I bound switch 1 in the sim for cockpit and external view panning, and also the control axes and the slider in the sim itself.

Can you post your Logitech profiler profile please. 

1 hour ago, TypeR said:

Can you post your Logitech profiler profile please. 

Sure, should I just open the file and post the XML?  (think that's what's in them)  Or do I need to host the actual profile somewhere for download?  Mine might seem a bit odd and it's still a WIP.  I based it on my old FSX one that was kind of set up for mode 1 being stuff I'd do on the ground, mode 2 is take-off/landing oriented, and 3 is more for like cruise stuff.  Though with the new keybinds, removal of some stuff vs older sims, some of the modes are just copies of binds from other modes still.