About this deal
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 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...... Then locate the Saitek_X52_Flight_Control_System.xml file and make a copy. Call it Saitek_X52_Flight_Control_System2.xml or something.
I have the steam version but the same will apply for any version, just locatate the input directory in your MSFS2020 install directory.
Otley - Harrogate
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. 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. 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?
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'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.Device DeviceName="Saitek X52 Flight Control System" GUID="745a17a0-74d3-11d0-b6fe-00a0c90f57da" ProductID="0255">