Hi guys, getting the X52 setup is a fairly lengthy and detailed process. I now
have a working profile, and have defined almost ALL of the buttons on my X52.
Here’s the BAD NEWS. You too will need to define all of the functions one
button at a time and create your own custon profile. I cant copy mine and
send it to you, because it is hidden in the guts of the executable game
somewhere. The good news is that you can also do a process and map you own.
And it will stick around game to game. Im LOVING IT now. So here goes.
Plug in your X52 first.
Start the simulator.
Go to the options menu.
Highlight the X52 (and keep the for now)
In the Search by name block, type in axis.
Under filter,
Just a suggestion. You don’t have to manually select the Input number or Axis using “Select an Input”. MSFS will recognize the input if you physically activate it (button, trigger, slider, etc.). In the “bindings window”, instead of clicking on “Select an Input”, click on “Search by Input”. It will light up. Then trigger the physical input on your controller. It will automatically fill in the Input description. Finally click Validate to save.
This is not true. Due to different GUID´s at Saitek / Logitech X52 (Non Pro) MSFS will not recognize my older X52. My GUID is “745a17a0-74d3-11d0-b6fe-00a0c90f57da”, Product ID is “0255”
The XML-Profile only works with GUID=“9a117810-f09c-11e7-8002-444553540000” ProductID=“075C”
With the Gamepass-Version there is no way to edit, copy or duplicate these XML-Profiles, so no way for Users with older X52 to get this to work without manually assign all Buttons and Axis.
I have an older X52 and the sim recognized it and offered me the mapped default. I think the reason is that I had updated the driver to Logitech’s latest.
In my Device Manager, that is the Product ID (PID) for my X52, but the Class Guid is: {745a17a0-74d3-11d0-b6fe-00a0c90f57da} This Guid is for Human Interface Devices (HID), and I have several usb devices registered under it, including the X52 whose product id is 075C. The GUID 9a117810-f09c-11e7-8002-444553540000 , on the other hand is not found in my Windows Registry at all.
Now that’s an interesting statement. I’ve assumed all along that when a new driver is added to the system, it is registered in the registry, and the device manager reads it’s info from the registry. Is this not so? Perhaps in my case, it did overwrite, but the value was unchanged.
You may be interested in this thread. , started by me. It discusses this issue in more detail, and someone actually posted for me what he says is the Saitek_X52_Flight_Control_System.xml file. It contains the same Guid as you post (9a117810-f09c-11e7-8002-444553540000; I’m curious where you got that from?).
So either there’s some mixup here, or MSFS2020 doesn’t use the GUID - only the PID - to recognize the HOTAS (even though there is a value in the XML file.)! Because, as I say, my X52 was properly recognized.
The GUID and PID probably changed when Saitek (who made my OLD X52 silver version) was bought out by Logitech. More than likely Logitech has a different GUID and PID. Seems like Asobo/MS need to make a second file for the older X52 with the propoer ID’s…
It recognized my x52 and had a default profile for it. I re mapped all the buttons though because I didn’t like them how they were. I left the axis stuff alone since those were correct.
This will however not fix ALL the buttons as your title says. Just like Xplane some of the buttons on the joystick will not work. Like the pinky switch and mode selector on the side. It will let you map the pinky switch, but it doesn’t actually control anything.
When you get this controller you get the impression it will do all these cool things wiht extra buttons and modes. Which it probably does in the game it was designed for. However in flight sims it tends to be a bit crippled. Unless I simply don’t know what I am doing which could be very possible lol. I have googled it though and mostly what I found was that is just how it is.
I don’t have a driver installed for mine, or rather just what windows decided to install for it to work..As such, my pinky switch doesn’t work either. However, I installed the drivers and profiler and then the pinky switch worked. I was just testing stuff though, I have no use for that button and didn’t want all the logitech rubbish installed / running, so reverted back. Every other button / function works, aside from the pinky one.
I have all the drivers and software and updated firmware. Like I said, I can map the pinky button, it recognizes it. It just doesn’t actually do anything when you try to use it. Maybe my switch is broke? But I don’t think so because it registers as working when you test it.
At this point though I can do without it. Even if I could get it to work I don’t think I would re map my buttons again.
Hi, I have the x52 pro and an struggling to set the brakes up properly. I am currently using the slider on the front of the throttle control (I believe this is the U axis) but the slider only works as an off and on, is there any way to have gradual braking? Thanks.
I have just opened a ticket as well. While I can use the controller after manually mapping all the buttons, it would be nice if there was a default to select and if the image shows so I can reference it quickly in game.
UPDATE: They have responded to my ticket similarly as above. They’ve added it as a bug. There is hope.
I thought it was just my old stick, appears there are others with the pinky switch functionality not being recognized by the sim…perhaps it will be addressed in the next patch…i’ve been able to utilize most of the buttons and switches as I had them configured with FSW and FSX…I am hoping that this time around the sim continues to grow and improve…
I have the same issue. Mode switch and pinkie all recognised in the Logitech software and control panel, but do nothing in the sim. I hope it gets fixed as will make life easier instead of going back to the keyboard!