x56 HOTAS throttle counts as all inputs.

[ZombBlacksmith]

I really do apologize if this could've been posted elsewhere, but I have looked all over the place and I have not been able to find a solution.  IL2 registers throttle as literally all of my axis.  All of them, regardless of what they are mapped to.  Do you want to pitch? theres throttle for that.  You want to yaw and roll? youve got throttle.  Everything has been mapped to its respective axis, controller, toggle, or rotary, but the game only registers my throttle as the input.  

I've checked my logitech software, quintuple checked my drivers, and verified everything through my windows controller manager.  All axis check out, give and output, and register correctly. Its just IL2 doesnt care about any of those other inputs. 

 

Please help. this is my last ditch effort.

[North_Wolf]

I have a 52x Pro and I have been spending alot of time with its settings, so maybe I can help get closer to what the issue might be.

 

I know that IL2 is very particular about not allowing two controllers to do the same thing (lets imagine that IL2 thought the throttle was independent from the stick), but it does not put them into keybinds on its own so I would find it more likley that the issue is outside of IL2.

 

How does it behave in other games?  Does everything function correctly in "Controllers"? (found under "set up usb controllers" in windows 10 at least).  You can test things like deadzone there.  Same with the Logitech software, it should jump to whatever you give it input in the programable thing.

 

 

 

Ok maybe I did not understand your question well... so one thing comes to mind.

 

If this is happening only when you try to keybind things:  Throttle always comes up before whatever input you press.

 

It might be just a sensitivity issue with the throttle forcing it to give constant input (it wont settle).

 

First try using the (physical knob that adjusts the stiffness on the 56x throttle) if that does not help then try setting a bit of a dead zone on the throttle in the controller settings or the logitech software.

 

That should stop the throttle from being so over active, the main issue with doing this inside of IL2 is that its done after the keybind is set (and possibly its per keybind).  

 

Also you can try in IL2 setting Joystick Noise filter to 0.6 (that is recommended in general for the X52 series so it might be the same).

 

I hope this was the issue and you get up there and flying. 

 

 

 

 

Edited October 13, 2024 by North_Wolf

[ZombBlacksmith]

North_Wolf

 

In "controllers", and Logitech's software, everything with both the throttle and the joystick all check out (buttons, toggles, and rotaries included), behaves as it should in DCS.  To offer potentially offer a bit more clarity on the problem that Im experiencing, Ill kinda walk through what I was doing;

 

When I mapped Pitch or Roll, it would show up as "JoyStick1" after moving joystick back and then forward, which seemed correct.  When I mapped Thrust to the thrust controller, it would show up as "JoyStick0" (weird to me, but maybe naming is just weird). So, each one is mapped independently.  However, when I go into the adjustment window on the far right side, it only reads motion on the thrust controller (JoyStick0) as inputs for everything else, regardless of what its actually mapped to.  

This doesn't seem to be a deadspot, or noise issue; while I will adjust those as needed when I can get that far, it seems like the game just only focuses on reading inputs from thrust controller, and forgets about everything else for me.