We’re not endorsed by, affiliated with or supported by them, and they don’t warrant the accuracy or quality of the information.

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 a dedicated driver installed for the wheel, so I also have in those properties the option to to set default axis ranges - for generic devices that Windows sets up, those calibration settings are in another tab that says Calibrate. I'm using X56 HOTAAS, installed correctly, but Logitech's util won'y let me correct teh Z-Axis drift I've developed.The X52's LCD screen - with adjustable backlighting - enables you to view information about your button configurations with only a quick glance. 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.

I found what was my problem with the X52 Pro not showing up at all in FS 2020 (despite working in other sims and showing up in W10's Devices and printers).To use it correctly - and with results - first of all I have to open the Windows properties of my steering wheel where I can see how my device functions - which buttons I press and how the axis behaves. I have several files (it depens of the plane) and no probleme to choose the good Keyboard and Saitek profiles. I have the steam version but the same will apply for any version, just locatate the input directory in your MSFS2020 install directory.