On Windows 10 it is not there so I had to add a dead zone, but all evening my ships have been slowly rolling to the right. Saitek introduces the new X-56 Rhino H.O.T.A.S. System. Built to the same exacting standards of Saitek's award-winning Pro Flight range, Not happy at all with the direction computers are heading. And it isn't just Windows doing this stupid crap. Same kind of things happening on Macs as well. Combatible with Most Flight Simulation, Combat Simulation, and Space Simulation Software including:

after, you run the simulator, go to options-commands and put your own parameters (give a name to your parameters file) After the controls screen started, I then plugged in my Saitek X52 Pro into an open USB port. The sim found my controllers.Device DeviceName="Saitek X52 Flight Control System" GUID="745a17a0-74d3-11d0-b6fe-00a0c90f57da" ProductID="0255"> Sadly, I had to assign all the controls from scratch. There was not a single entry by default. Took me about 20 mins but I still have to play around with some things to get them how I like them. I find it peculiar that all other flight sims such as DCS, flight sim x, and even war thunder, have immediately recognized the X52 and had default assignments. 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. the X-56 Rhino delivers a multitude of customizable options including all the control surface options required to achieve the exact level of

The MFD in the throttle controller displays "No Profile" but the controllers function properly and have many useful functions I did not expect. A new controller device has been detected, but we were unable to set it up with a control preset. Go to "customize controls" and create a custom control layout. For more information, please visit https://fsi.microsoftstudios.com 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. 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 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. 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...... Just to confirm is this the problem people are getting. So it detects the controller but then doesn't recognise it has a profile built in for it?

I have the steam version but the same will apply for any version, just locatate the input directory in your MSFS2020 install directory. At this point, the first time I launched FS 2020, my HOTAS was detected. Hope this helps others. I think I was the only one not to have my X52 Pro detected at all, but never know. Then locate the Saitek_X52_Flight_Control_System.xml file and make a copy. Call it Saitek_X52_Flight_Control_System2.xml or something.Device DeviceName="Saitek X52 Flight Control System" GUID="9a117810-f09c-11e7-8002-444553540000" ProductID="075C"> I'm not sure because the directories all seem to be randomly generated names, but if you find a file listing your X52 then you could try copying and pasting the following into your file and saving it.