Can't turn off joystick deadzones

[Avimimus]

Hello,

 

I'm not sure when this happened (either after an update, or once I switched which USB port I was using) - but I had to reconfigure my joystick inputs.

 

I've since discovered that there is a dead zone of about 0.10 - this is confirmed through the axis configuration screen.

 

However, reducing the deadzone in the axis configuration screen to 0.01 or 0.00 does nothing - the minimum dead zone remains 0.10

 

P.S. It is hard to correct one's aim if one has to move the joystick ten percent of its range of motion to the other side in order to make an aileron input!

 

 

[Hoss]

Joystick?

[9./JG52_J-HAT]

Have you tried assigning some key to another command and seeing if it is still there after you restart the game?

 

Control configs being reset (or set to something else in your case) are usually caused by SteamCloud synchronizing some wrong configs. Try turning it off in case it’s on and see if it solves it. 

Edited October 5, 2021 by 9./JG52_J-HAT

[FTC_Karaya]

15 hours ago, Avimimus said:

Hello,

 

I'm not sure when this happened (either after an update, or once I switched which USB port I was using) - but I had to reconfigure my joystick inputs.

 

I've since discovered that there is a dead zone of about 0.10 - this is confirmed through the axis configuration screen.

 

However, reducing the deadzone in the axis configuration screen to 0.01 or 0.00 does nothing - the minimum dead zone remains 0.10

 

P.S. It is hard to correct one's aim if one has to move the joystick ten percent of its range of motion to the other side in order to make an aileron input!

 

 

 

Unless you've set deadzones in the game itself, this is some fault of your joystick.

Did you check the windows game controller settings that there is in fact a deadzone?

Also keep in mind that the display for joystick input/output in CloDs control menu lags a bit and doesnt really give a representative picture of what the response is while flying.

Another thing is that "sensitivity" is in fact "non-linearity". Setting it to 0 means fully linear response, setting it to 1 gives a sort of exponential response.

Edited October 6, 2021 by Karaya

[Pict]

On 10/5/2021 at 9:17 PM, Avimimus said:

Hello,

 

I'm not sure when this happened (either after an update, or once I switched which USB port I was using) - but I had to reconfigure my joystick inputs.

 

I've since discovered that there is a dead zone of about 0.10 - this is confirmed through the axis configuration screen.

 

However, reducing the deadzone in the axis configuration screen to 0.01 or 0.00 does nothing - the minimum dead zone remains 0.10

 

P.S. It is hard to correct one's aim if one has to move the joystick ten percent of its range of motion to the other side in order to make an aileron input!

 

 

 

I would suggest as a step in diagnosing the problem that you back up your input setting folder, if you havn't already done so, then delete that folder and run the game to see if the problem persists. The game will rebuild the folder, so that's not a drama.

 

Then you should know if it your hardware or if the setting files have become corrupt in some way.

Edited October 10, 2021 by Pict

[Avimimus]

Thanks for all of the replies.

 

I think it might partly be my ancient X-52 becoming a bit less responsive, but things seemed to improve when I reduced the sensitivity and made responses more linear (Karaya's tip was most helpful here).

 

I'd also gone into the windows USB controller settings, and the Saitek software settings as well - so I can't gurantee that I didn't fix it elsewhere... but my impression is that lowering the sensitivity made the aircraft responsive again!