Logitech Gamepad F310 trigger buttons not being detected

steamopen Distro Family: ArchGeneral controller / Steam Input

ValveSoftware/steam-for-linux#7296 · opened 2020-07-29 by kozross · updated 2023-03-02 · 7 comments · github

Kkozross 2020-07-29 github

Your system information

Steam client version (build number or date): Jul 16 2020
Distribution (e.g. Ubuntu): Arch
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

In at least two games (namely Slay the Spire and Othercide), my Logitech Gamepad F310's left and right trigger buttons are not being detected. This ranges from annoying (Slay the Spire) to basically rendering the game unplayable (Othercide).

I can confirm that my controller is detected by my OS, and that the trigger buttons register when pressed (as confirmed by jstest).

Steps for reproducing this issue:

Plug in controller set to XInput mode
Start Slay the Spire
Choose a new game
Try using left trigger to set the seed
Observe nothing happening

Kkozross 2020-08-09 github

I can add more evidence to the pile that this is a Steam issue - another game I have (running under Wine) detects the trigger buttons fine on the same controller.

Kkozross 2020-08-15 github

Any progress on this issue @kisak-valve ? I am happy to supply additional information if it would aid a speedy resolution.

NNobutarou 2020-10-19 github

Hi,
I have F310 but play STS via GOG. I also meet the issue. I don't think this is a Steam issue.

I think the controller mapping file, game/betaPreferences/STSInputSettings_Controller is wrong,

As the Linux kernel default behavior of xpad module, the left trigger is act as axis-2 and the right trigger is axis-5. The right stick up/down is axis-3, and the left/light is axis-4. The STS default wants axis-3 as left/right triggers.

Then I modified the file to the following and now I can use the left/right trigger in my play,

{
  "SELECT": "0",
  "CANCEL": "1",
  "VIEW": "2",
  "PROCEED": "3",
  "PEEK": "8",
  "PAGE_LEFT_KEY": "4",
  "PAGE_RIGHT_KEY": "5",
  "MAP": "6",
  "SETTINGS": "7",
  "LS_Y_POSITIVE": "-1000",
  "LS_Y_NEGATIVE": "1000",
  "LS_X_NEGATIVE": "-1001",
  "LS_X_POSITIVE": "1001",
  "RS_Y_POSITIVE": "1002",
  "RS_Y_NEGATIVE": "-1002",
  "RS_X_POSITIVE": "-1003",
  "RS_X_NEGATIVE": "1003",
  "DRAW_PILE": "1002",
  "DISCARD_PILE": "1005"
}

Kkozross 2020-10-19 github

@Nobutarou Yeah, it does seem game-specific. Have you reported this to the dev team for StS?

NNobutarou 2020-10-20 github

Hi,
No, I didn't. I hesitate to report the issue since I don't use any
supported Linux distribution.
Thanks,
Nobuyuki

2020年10月20日(火) 1:28 Koz Ross [email protected]:

@Nobutarou https://github.com/Nobutarou Yeah, it does seem
game-specific. Have you reported this to the dev team for StS?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/7296#issuecomment-712282936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKOKX5YGE6LGPSYW2MME7TSLRSLXANCNFSM4PLFEOKQ
.

Kkisak-valve maintainer 2023-03-02 github

Hello, per "Fixed Logitech F310 controller input on macOS and Linux" in the 2023-03-01 Steam client update, please opt into Steam's client beta and retest this issue.

Kkozross 2023-03-02 github

@kisak-valve - just tested Slay the Spire again, using the beta client. Same exact issue.

Upstream links

ValveSoftware/steam-for-linux/issues/7296x1 2020-10