Kai Krakow

Closing old Bluetooth issues, please report to the bluez project if the problem persists.

Could you run `evtest` with the ds4drv: It lists the name of the devices. I suspect that this game only looks for the name of a device to identify it.

Do you run the game through Steam? If yes, please try disabling or enabling Steam Input for Xbox controllers (it can be switched in Big Picture mode, or per game...

Okay, I've looked at the ds4 driver: It doesn't do anything specific to mimic a X360 pad, it's just a HID standard driver. So I suspect the culprit being somewhere...

BTW: There seems to be some process stealing the device from us and exposing it via uinput: ``` [ 1756.090628] input: Xbox Wireless Controller as /devices/virtual/misc/uhid/0005:045E:0B13.000A/input/input33 ``` Comes anything to...

> Okay, I've looked at the ds4 driver: It doesn't do anything specific to mimic a X360 pad, Ah wait, I found this: ```python create_mapping( "xpad", "Microsoft X-Box 360 pad",...

Could you try this hack: ```patch diff --git a/hid-xpadneo/src/hid-xpadneo.c b/hid-xpadneo/src/hid-xpadneo.c index 8876cea..306bb8e 100644 --- a/hid-xpadneo/src/hid-xpadneo.c +++ b/hid-xpadneo/src/hid-xpadneo.c @@ -922,6 +922,9 @@ static int xpadneo_input_configured(struct hid_device *hdev, struct hid_input *h break;...

In my patch queue, I've added a module parameter `xpad_emulation=1` which may fix this for you. To properly use that, use `git remote add kakra https://github.com/kakra/xpadneo && git remote update`...

I moved this to a pull request so you can better follow the updates or easily extract a patch for local package installation: * https://github.com/atar-axis/xpadneo/pull/283 * https://github.com/atar-axis/xpadneo/pull/283.patch

@Kzimir Can you retry with the latest version without applying the Xbox360 emulation hack? We changed some quirks and fixups which may affect how such games handle and detect the...