Help! X52 HOTAS

[creighton]

I recently upgraded to a far better PC gaming computer. I am no longer able to bind the controls of my X52 Pro HOTAS to the game. Even when I attempt to use the X52 profile or custom nothing works. The ship constantly just goes in circles. The game is not allowing me to bind anything at all, it simply says "input AXIS already expected". The X%@ is working perfectly on other flight games.

[Geekbyte]

Have you tried resetting the controls to default first and then attempting to use the HOTAS control scheme?

[Geekbyte]

Just a follow up if possible. You've recently updated your pc and this is a new Windows installation I'd presume too. Have you downloading any recent Windows Updates since your received your new PC? What is your current Windows version?

Also, could you take a look the the Joystick keybindings not saved / lost after restart debugging thread to see if there's anything in there that could help resolve your issue.

[creighton]

Hello and thank you for the reply. Yes I have tried resetting the controls to default and loading the proper control scheme. I am using windows 11 and all drivers including Joysticks up to date. I attempted again tonight and I am getting the same result. It worked perfectly on my old computer with Windows 10. I think this would be a lot more simple if i could bind pitch up/down separately as a button?. But the game only allows me to bind the entire axis. It automatically binds pitch/yaw/roll to the exact same axis no matter what I do.

[Geekbyte]

Weirdly this bug wasn't present with Window 10, but is happening with Windows 11? Wonder if W11 has introduced the issue, but we'll need to check further.

So if you move the stick left or right it's assigning pitch, roll & yaw to that axis?

[Geekbyte]

Doing some digging into this, it does appear that W11 is altering settings, for me at least. (Using an x56 to test on my system)

What I've found currently is that W11 assigns a huge deadzone so that no inputs are registered on any axes.
I had to re-run the calibration within the Logitech software on the stick, then we could see the inputs.
Also, the Rudder (yaw) doesn't get fixed until you manually alter the deadband. Changing the Deadband to 100 for example and then switching it back to 50 (default) appears to work.

Also, it seems that Logitech haven't updated the drivers to W11 yet either so we're relying on the W10 driver version.

Still doing more digging into this with the team.

[creighton]

Hello and thank you again for the reply. You have pointed me in the right direction. So when I switched to Windows 11 it was using an older driver version of the X52. I was able to update that. However, I still had the same problem. When I went into the X52 controller properties (as you have stated above) I found the X52 to have NO dead zones at all. Therefore when attempting to bind the Pitch/roll/yaw Axis, It was attempting to bind on all the same axis as the game could not tell the difference between them. I gave everything a very small dead zone and this solved the problem.
Thank you very much!

[Geekbyte]

Glad it's sorted!

I was very confused about why the inputs on the axes were not registering so had to rely on some googling to find that information. Go Windows 11!

Fly on pilot!