Logitech F310 broken analogue stick controls

[hateball]

I'm unable to use both the right stick to go down or rightwards. Can't see any way to reconfigure this. They don't feel too great in the other directions either, but at least the game registers something then.

I can't even remember the last time I had trouble using this controller in a game.

[Miss]

Yeah, gamepads on Linux in the current build seems to be broken for all gamepads, it's a known issue. Hopefully we'll be able to fix this in a patch tomorrow!

[Lucki]

I can confirm this with a F510. The pad worked correct in Hammerwatch.

[hateball]

Great, nice with a fast response! I'll hold off playing more and getting used to kb/m before gamepad works then :)

[Miss]

Hey guys, I've fixed this for the next update.

[hateball]

It's... better. I can now aim by rotating the right stick. If I let go of it, it will "reset" but in random directions. I am not sure what the intended behavior is. What I expect is that it remains where I last aimed.

For the left stick then, well touching move will make "up" stick, or sometimes "left". I can still move in the other directions, I'm just fighting myself doing so. So it's not very smooth.

Are there any logs I can provide to help troubleshoot?

[Miss]

Hmm, it sounds like your deadzone is very big. You can debug it a bit by having an open terminal and setting "debug_controls 2" in the console. This will print to stdout each gamepad axis value and you can hopefully kinda see what your deadzone is. You can then modify this deadzone (currently only manually but this will be added to the settings soon) in the "res/controls.cfg" file, at the "delta="X"" values.

If your bindings are incorrect, you can also implement them manually (there's default bindings for Dualshock 4, your game is probably using this for a detected joystick). I will be able to write a guide on the controls configuration file soon.

Alternatively you could set Steam to emulate your "generic controller" (that's how Steam calls it) as a Steam Controller, and you could use the Steam Controller interface to re-bind your controller.

[Lucki]

Works as expected here now.
It feels like there is no deadzone at all, but that's not a problem with my pad.

[hateball]

Originally posted by ♥ Scratch ノ:

Hmm, it sounds like your deadzone is very big. You can debug it a bit by having an open terminal and setting "debug_controls 2" in the console. This will print to stdout each gamepad axis value and you can hopefully kinda see what your deadzone is. You can then modify this deadzone (currently only manually but this will be added to the settings soon) in the "res/controls.cfg" file, at the "delta="X"" values.

If your bindings are incorrect, you can also implement them manually (there's default bindings for Dualshock 4, your game is probably using this for a detected joystick). I will be able to write a guide on the controls configuration file soon.

Alternatively you could set Steam to emulate your "generic controller" (that's how Steam calls it) as a Steam Controller, and you could use the Steam Controller interface to re-bind your controller.

I'm sorry, I dont understand how you mean I should set "debug_controls 2" in a terminal, at all. Is it a variable I should export before launching the game from a terminal?

I also tried attaching my Steam Controller. The game actually recognizes it as Steam Controller rather than Gamepad 1. It does however not register any input what so ever from it.

I tried attaching a Dual Shock 3 as well, but I cant get that to work in any game I tried at all. Also tried using xboxdrv for that one.

[Miss]

I don't suggest using xboxdrv, in my tests having that driver always messed up a few things in gamepad recognition.

As for the debug command, you can open console in-game by pressing ~ (tilde) or the equivalent key for your keyboard layout. You should have a terminal open with the game running in it because it spams all the output to stdout.

[hateball]

If I bring up the console with § (key left of 1) and enter either "debug_controls 2" or "debug_controls=2) and press enter there is no output in the console and all input freezes all together. If I press § again then I can resume fighting the controller. Anything else I can try?

[Miss]

Yes, I mean it will output to stdout, not the console. Meaning you will need to run the game from a terminal to see what's happening.

I might actually redo this debugging command as that's admittedly not very practical.

[hateball]

Regardless if I do "debug_controls 2" or "debug_controls=2" (still not sure what to use here) this is the output https://pastebin.com/pJLctVvg

Sometimes if I press up on left stick, it will get stuck in down... and so on. No rhyme or reason.

[Miss]

Ahhh, crap.. I didn't realize this cvar is only available on developer builds.. sorry for the confusion there. :(

As an alternative, you can also look at the values on something like on this website: http://html5gamepad.com/

[hateball]

Hmmm, so according to that page, Axis 1 (left up) is sometimes -0.000061 after having let go of it. So I should add that value to the controls.cfg file then?

[Miss]

Talking about controls.cfg, there was a bug reported earlier that makes the deadzone non existent sometimes. Can you post your controls.cfg file? It might be the same issue.