search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.22k stars 174 forks source link

DS4 Controller not recognized in game #5036

Open chronics23 opened 7 years ago

chronics23 commented 7 years ago

Your system information

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

I am using Steam on Linux Debian 9 and after one of the steam client updates (I think April) my ps4 controller is no longer being recognised when playing by most games such as Hitman, ETS2 and Deus Ex. Previously I would just start the game from normal steam interface and the games would pick up that a PS4 controller was connected, now these games arent even recognizing that a controller is connected.

When I go into BPM it recognises the controller and I can configure it, however this only works for certain games and subsequently I cannot use the in-game options to configure the buttons, this happens regardless of whether or not I enable PS4 controller support in BPM settings. Is there anyway to prevent steam from picking up the controller altogether so that the games can recognise it by themselves and allow me to configure in game as was happening before one of these updates that has completely broken the usability?

Note, if I disconnect/connect the controller in-game it very briefly sees the controller (for about 1 second) and then the in game menu greys out again, I am connecting via usb. Thanks

Steps for reproducing this issue:

  1. Connect DS4 controller via USB
  2. Open Steam Client and open any game that supports controller.
  3. Controller is not able to use in-game configuration regardless of whether PS4 controller support is checked in BIg Picture Mode settings.
ghost commented 7 years ago

I have the same problem on both SteamOS and Ubuntu Budgie.

Ozymandias117 commented 7 years ago

Don't know if it's at all useful, but when plugging in the DS4, steam client appears to spawn a thread with the name "CSteamControlle" (presumably Connect Steam Controller?). That thread appears to be stuck in an infinite loop calling libusb_handle_events (after 5 minutes, it was still in the same loop).

This is also on Debian Stretch. Originally, it was using the Steam Runtime libusb, which I thought might be causing an issue, so I installed my distro's version of libusb-1.0-0, and am seeing the same thing.

asim-vax commented 7 years ago

Same issue with steam link & ubuntu gnome 17.04

Unshackle8078 commented 6 years ago

Same issue in 17.10.

Why is Steam not mapping it to standard XInput for games that don't support SDL?

chronics23 commented 6 years ago

Problem is still occuring in Debian Testing (Buster). BPM now has the option to "Force Off" steam configuration for non steam controllers, unfortunetly this doesn't seem to have fixed the problem as these games now just don't recognise their is controller connected at all.

GargleBlaster259 commented 5 years ago

I assume my issue is closely related: my DualShock 4 v2 controller is recognized by Steam Input correctly (connections via USB and Bluetooth are both working), I can control BPM menus, turn on PlayStation support, configure different profiles and so on. In short, everything seems to work as intended.

Once in-game, however, no input from the controller whatsoever is recognized by the game (and yes, I made sure PlayStation support is turned on globally or forced on for the games I tested).

I made sure the respective udev rules are in place and working. In fact, a virtual "Microsoft X-Box 360 pad" device gets created at /dev/input/js1 and /dev/input/event22 with the proper permissions when PlayStation Configuration support is enabled. If these (virtual) devices are tested with tools such as evtest, no input is recognized as well.

I'd be happy to provide additional information that might help fixing this issue.

stijnb1234 commented 1 year ago

Replying to https://github.com/ValveSoftware/steam-for-linux/issues/5036#issuecomment-511111166

Having the same issues. Have you ever resolved this?