August 20, 20205 yr 23 minutes ago, shaggywolfhound said: 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? Full message: " 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 - X52 H.O.T.A.S " yes
August 20, 20205 yr Hello Flyers, Aug 20, 2020 1. I am running, Logitech Software Version 8.0.213.0 Driver Version 8.0.121.0 which I downloaded from Logitech today. Link: https://support.logi.com/hc/en-us/articles/360024838173--Downloads-X52-Professional-Space-Flight-H-O-T-A-S- 2. I have installed MFS 2020. 3. I started the sim with NO flight controllers plugged in. 4. After the sim started, I clicked on the OPTIONS Tab at the top of the screen. 5. Then I clicked the CONTROLS Tab at the top right side of the screen. 6. After the controls screen started, I then plugged in my Saitek X52 Pro into an open USB port. The sim found my controllers. 7. The sim added a tab named X52 Professional H.O.T.A.S. 8. I clicked on the DEFAULT tab under the X52 Professional tab above it that was just created by the sim. 9. I created a new flight plan and ran the sim. Other notes: All functions are present. You may have to teak the sensitivity on some control surfaces the first time. My stick was a bit over reactive but trimmable using stick hat POV2. The MFD in the throttle controller displays "No Profile" but the controllers function properly and have many useful functions I did not expect. Hope this helps 🙂 Jay My Home Brew Rig: Windows 10 Pro 64-bit Edition Intel i9-9900K 3.60GHZ 16MB Intel Smart Cache LGA 1151 32 GB Corsair Vengeance DDR4/3200MHz ASUS Turbo GeForce RTX™ 2080ti 11 GB GDDR6 (Turing) VR Ready ASUS Prime Z390-P ATX w/ WiFi 802.11 AC. Gigabit LAN Network 1 TB (1TBx1) Patriot Viper Gaming VP4100 Series (PCIe Gen4) NVMe M.2 SSD 2 TB (2TBx1) Seagate SATA-III 6.0Gb/s 256MB Cache 7200RPM HDD 850 Watts - Corsair RM Series RM850 80 Plus GOLD Certified Fully Modular Ultra Quiet Power Supply 1 Corsair Crystal Series 570X RGB ATX Mid-Tower Gaming Case All Tempered Glass Enclosure Edited August 20, 20205 yr by JayDog1
August 20, 20205 yr On 8/18/2020 at 9:32 AM, ep-irl said: I have the saitek X52 (not the pro, the silver one) and when i map the roll -X +X axis and pitch -Y+Y axis , i dont get the white slider bar under each of the assigments in the control configuration menu. and when i fly the X , Y axis is very sticky, doesnt return to center when i remove my hand from the joystick. currently the plane is not controllable . please help Hi, I just made an account because I was having the same issue and figured it out, so I'd like to help you out too. My mistake was only assigning the controls to the "essentials" tab. This doesn't let you map the axis, so all you're mapping is increase and decrease in a binary sense. When you move the joystick or throttle, it's treating the move as a singular increase in the control surface/throttle. What you need to do is set the filter to "ALL". This will let you assign not only increase and decrease buttons, but also the axis, which is what you want for the joystick. Once you assign the axis, you'll see a little bar on the bottom appear which shows the degree of movement. When you move the joystick or the throttle, you'll see the bar move accordingly. 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. Anyways, hope this helps out. Took me about an hour of frustration before I realized my mistake. Cheers!
August 20, 20205 yr On 8/18/2020 at 11:41 AM, PsyMan2000 said: Thanks Oaks, As suggested I started the sim with my X52 Pro unplugged and then while on the controls page I plugged it back in and it detected the new controller, followed the instruction to apply the defaults and now the thing is working. Great work, thanks again. Does the sim remember your joystick next time you start the game? Mine does not 😞 Help please. Edited August 20, 20205 yr by JayDog1 misspelling
August 20, 20205 yr 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). I noticed that right clicking on the X52 icon in Devices and printers and then trying to open "Game controller settings" wouldn't do anything. Same when trying to execute joy.cpl directly. Turns out my joy.cpl was corrupted, I'm assuming because of a driver but can't confirm. Therefore, I moved it to a backup folder (in case this wouldn't be the problem) from C:\Windows\System32, and then copied the original C:\Windows\SysWOW64\joy.cpl and pasted it in C:\Windows\System32 to start fresh. Rebooted, connected the X52 Pro, right clicked and opened the game controller settings successfully. 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.
August 20, 20205 yr 1 hour ago, Kabouik said: 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). I noticed that right clicking on the X52 icon in Devices and printers and then trying to open "Game controller settings" wouldn't do anything. Same when trying to execute joy.cpl directly. Turns out my joy.cpl was corrupted, I'm assuming because of a driver but can't confirm. Therefore, I moved it to a backup folder (in case this wouldn't be the problem) from C:\Windows\System32, and then copied the original C:\Windows\SysWOW64\joy.cpl and pasted it in C:\Windows\System32 to start fresh. Rebooted, connected the X52 Pro, right clicked and opened the game controller settings successfully. 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. Did it have preassigned values? As in, were you able to fly the plane without having to manually map the controls?
August 20, 20205 yr I had X52 Pro detected. Joystick was connected all the time. First time all buttons had functions and vice versa. After booting PC every field was empty and defaults gives nothing either. Had to input manually some to fly at least a bit. Waiting for fix to get defaults back. .
August 21, 20205 yr The following was in the folder listed in the path: C:\Users\swift\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\0009057C57C5B608_00000000000000000000000069F80140\553F7E85363B48629A7248F9830BE2EC 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. Hope this helps!! <?xml version="1.0" encoding="UTF-8"?> <Version Num="1238"/> <FriendlyName>X52 H.O.T.A.S. profile</FriendlyName> <Device DeviceName="X52 H.O.T.A.S." GUID="{74E9AD80-D994-11EA-8001-444553540000}" ProductID="1884"> <Axes> <Axis AxisName="X" AxisSensitivy="-50" AxisDeadZone="2"/> <Axis AxisName="Y" AxisSensitivy="-50" AxisDeadZone="0"/> <Axis AxisName="Z" AxisSensitivy="1" AxisDeadZone="2"/> <Axis AxisName="rX" AxisSensitivy="1" AxisDeadZone="2"/> <Axis AxisName="rY" AxisSensitivy="1" AxisDeadZone="2"/> <Axis AxisName="rZ" AxisSensitivy="-50" AxisDeadZone="2"/> <Axis AxisName="SliderX" AxisSensitivy="1" AxisDeadZone="2"/> </Axes> <Context ContextName="PLANE"> <Action ActionName="KEY_ENGINE" Flag="2"> <Primary> <KEY Information="Joystick Button 8">7</KEY> </Primary> </Action> <Action ActionName="KEY_GEAR_TOGGLE" Flag="2"> <Primary> <KEY Information="Joystick Button 12">11</KEY> </Primary> </Action> <Action ActionName="KEY_ALL_LIGHTS_TOGGLE" Flag="2"> <Primary> <KEY Information="Joystick Button 13">12</KEY> </Primary> </Action> <Action ActionName="KEY_AP_MASTER" Flag="2"> <Primary> <KEY Information="Joystick Button 2">1</KEY> </Primary> </Action> <Action ActionName="KEY_BRAKES" Flag="2"> <Primary> <KEY Information="Joystick Button 15">14</KEY> </Primary> </Action> <Action ActionName="KEY_SPOILERS_TOGGLE" Flag="2"> <Primary> <KEY Information="Joystick Button 11">10</KEY> </Primary> </Action> <Action ActionName="KEY_ELEV_TRIM_DN" Flag="2"> <Primary> <KEY Information="Joystick Button 18">17</KEY> </Primary> </Action> <Action ActionName="KEY_ELEV_TRIM_UP" Flag="2"> <Primary> <KEY Information="Joystick Button 16">15</KEY> </Primary> </Action> <Action ActionName="KEY_PARKING_BRAKES" Flag="2"> <Primary> <KEY Information="Joystick Button 14">13</KEY> </Primary> </Action> <Action ActionName="KEY_FLAPS_INCR" Flag="2"> <Primary> <KEY Information="Joystick Button 9">8</KEY> </Primary> </Action> <Action ActionName="KEY_FLAPS_DECR" Flag="2"> <Primary> <KEY Information="Joystick Button 10">9</KEY> </Primary> </Action> <Action ActionName="KEY_AXIS_ELEVATOR_SET" Flag="4"> <Primary> <KEY Information="Joystick L-Axis Y ">1042</KEY> </Primary> </Action> <Action ActionName="KEY_AXIS_AILERONS_SET" Flag="4"> <Primary> <KEY Information="Joystick L-Axis X ">1026</KEY> </Primary> </Action> <Action ActionName="KEY_AXIS_RUDDER_SET" Flag="4"> <Primary> <KEY Information="Joystick R-Axis Z ">802</KEY> </Primary> </Action> <Action ActionName="KEY_RUDDER_TRIM_LEFT" Flag="2"> <Primary> <KEY Information="Joystick Button 19">18</KEY> </Primary> </Action> <Action ActionName="KEY_RUDDER_TRIM_RIGHT" Flag="2"> <Primary> <KEY Information="Joystick Button 17">16</KEY> </Primary> </Action> <Action ActionName="KEY_AXIS_MIXTURE_SET" Flag="4"> <Primary> <KEY Information="Joystick R-Axis Y ">786</KEY> </Primary> </Action> <Action ActionName="KEY_TOGGLE_FEATHER_SWITCHES" Flag="2"> <Primary> <KEY Information="Joystick Button 30">29</KEY> </Primary> </Action> <Action ActionName="KEY_THROTTLE_REVERSE_THRUST_TOGGLE" Flag="2"> <Primary> <KEY Information="Joystick Button 7">6</KEY> </Primary> </Action> <Action ActionName="KEY_THROTTLE_AXIS_SET_EX1" Flag="4"> <Primary> <KEY Information="Joystick L-Axis Z ">1058</KEY> </Primary> </Action> <Action ActionName="KEY_PROP_PITCH_AXIS_SET_EX1" Flag="4"> <Primary> <KEY Information="Joystick R-Axis X ">770</KEY> </Primary> </Action> </Context> <Context ContextName="MODES"> <Action ActionName="KEY_CYCLE_PILOTVIEW_NEXT" Flag="2"> <Primary> <KEY Information="Joystick Pov Up">256</KEY> </Primary> </Action> <Action ActionName="KEY_CYCLE_PILOTVIEW_BACK" Flag="2"> <Primary> <KEY Information="Joystick Pov Down">258</KEY> </Primary> </Action> </Context> <Context ContextName="EXTERNAL_CAMERA"> <Action ActionName="KEY_CHASE_QUICKVIEW1" Flag="2"> <Primary> <KEY Information="Joystick Pov Right">257</KEY> </Primary> </Action> <Action ActionName="KEY_CHASE_QUICKVIEW2" Flag="2"> <Primary> <KEY Information="Joystick Pov Down">258</KEY> </Primary> </Action> <Action ActionName="KEY_CHASE_QUICKVIEW3" Flag="2"> <Primary> <KEY Information="Joystick Pov Left">259</KEY> </Primary> </Action> <Action ActionName="KEY_CHASE_QUICKVIEW4" Flag="2"> <Primary> <KEY Information="Joystick Pov Up">256</KEY> </Primary> </Action> </Context> <Context ContextName="COCKPIT_CAMERA"> <Action ActionName="KEY_COCKPIT_QUICKVIEW4" Flag="2"> <Primary> <KEY Information="Joystick Pov Left">259</KEY> </Primary> </Action> <Action ActionName="KEY_COCKPIT_QUICKVIEW3" Flag="2"> <Primary> <KEY Information="Joystick Pov Right">257</KEY> </Primary> </Action> </Context> <Context ContextName="INSTRUMENTS_CAMERA"> <Action ActionName="KEY_COCKPIT_CYCLE" Flag="2"> <Primary> <KEY Information="Joystick Pov Right">257</KEY> </Primary> </Action> <Action ActionName="KEY_COCKPIT_BACKCYCLE" Flag="2"> <Primary> <KEY Information="Joystick Pov Left">259</KEY> </Primary> </Action> </Context> </Device> Edited August 21, 20205 yr by Swifty76
August 21, 20205 yr 12 hours ago, Kabouik said: 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). I noticed that right clicking on the X52 icon in Devices and printers and then trying to open "Game controller settings" wouldn't do anything. Same when trying to execute joy.cpl directly. Turns out my joy.cpl was corrupted, I'm assuming because of a driver but can't confirm. Therefore, I moved it to a backup folder (in case this wouldn't be the problem) from C:\Windows\System32, and then copied the original C:\Windows\SysWOW64\joy.cpl and pasted it in C:\Windows\System32 to start fresh. Rebooted, connected the X52 Pro, right clicked and opened the game controller settings successfully. 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. 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. Edited August 21, 20205 yr by Kabouik
August 21, 20205 yr 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. Edited August 21, 20205 yr by Pottymoose PS Addition
August 21, 20205 yr 3 hours ago, 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...... Thanks for the info, seems like this issue might be a bug then. I think I'm just going to map everything in the Logitech software instead. I was playing with the sim mapping last night and pretty quickly realized it can't recognize the mode switch and just thinks it's the same buttons in each mode which really limits what you can bind to it. I typically have all 3 modes set up. Mode 1 is ground/pre-departure stuff, Mode 2 is take-off/landing stuff, Mode 3 is cruise functions. AMD Ryzen 9950X3D | Asrock X870E Taichi | Gigabyte Gaming OC 4090 w/EK waterblock | Full Custom Loop Cooling | Corsair Dominator Titanium DDR5-6000 | Samsung & WD NVME/SSDs | Phanteks Enthoo 719 | Seasonic Vertex Gold 1200W | Keychron Q5 Max | Corsiar Scimitar Elite SE Wireless | Honeycomb Alpha and Bravo | Logitech Pro Flight Pedals | VKB Gladiator Pro NXT L&R handed | MiniCockpit MiniFCU | Alienware AW34DWF | Asus PG279Q | Win 11 Pro
August 21, 20205 yr 9 hours ago, 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. Thank you...this worked a treat! Also have an original x52 and like yourself the hardware ID was 255...once I located the appdata input folder the defaults loaded! Good times!
August 21, 20205 yr So my last didn't show me going throw all the keybinds i have uploaded a new video showing you my complete set up and how it is done take a look im sorry for poor mic quality
August 22, 20205 yr Well I have same issue but the file folder because its the XBOX on pc version is locked so noone can get accdess to change anything That is BS...should have bought the steam version,,,second problem is when I try the start then plug it in it crashes to desktop so That won't work neather. so I can't change alter or any anything in the input folder.
August 22, 20205 yr HI, I have FS2020 from last Monday and a Logitech SaitekX52 Pro HOTAS. All is working fine ! But to obtain this result : 1- when you download FS2020, the first part (about 1Go) must be on your Windows drive (C:) and the second part (95.15 Go) on the drive you want. 2 I have suppress the X52 completely from windows and reload it. 3 after, you run the simulator, go to options-commands and put your own parameters (give a name to your parameters file) Don't forget to validate, push F11 then Enter keys (not clic on the button message). I have several files (it depens of the plane) and no probleme to choose the good Keyboard and Saitek profiles.
Archived
This topic is now archived and is closed to further replies.