Hi, thanks for the new linux version! It works great, except it doesn't recognize my Xbox360 wireless controller at all. The controller works in Steam Big Picture Mode, and the input shows up in jstest-gtk.

Thanks.

I'm having the same issue, joystick works fine in other games and with jstest, but not detected in the game. I'm using a non-wireless Xbox 360 controller.

I ran deadcells under strace, not sure if this is normal or a clue:

readlink("/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/input/input20/js0/subsystem", "../../../../../../../../../class"..., 1024) = 38
openat(AT_FDCWD, "/run/udev/data/c13:0", O_RDONLY|O_CLOEXEC) = 7
fstat(7, {st_mode=S_IFREG|0644, st_size=646, ...}) = 0
read(7, "S:input/by-id/usb-\302\251Microsoft_Co"..., 4096) = 646
read(7, "", 4096) = 0
close(7) = 0
stat("/dev/input/js0", {st_mode=S_IFCHR|0664, st_rdev=makedev(13, 0), ...}) = 0
openat(AT_FDCWD, "/dev/input/js0", O_RDONLY) = 7
ioctl(7, EVIOCGNAME(128), 0x7ffc7e227c70) = -1 EINVAL (Invalid argument)
close(7) = 0

system : Arch Linux
Have the same problem. Did the same as torham, and initially didn't work on my Xbox360 wireless (another non-wireless controller I have worked fine though).

using the standard xpad module.
sdl2-jstest -l returned the non-wireless as

Joystick Name: 'Microsoft X-Box 360 pad'
Joystick GUID: 030000005e0400008e02000014010000
Joystick Number: 0
Number of Axes: 6
Number of Buttons: 11
Number of Hats: 1
Number of Balls: 0
GameControllerConfig:
Name: 'XInput Controller'
Mapping: '(null)'

and wireless as

Joystick Name: 'Xbox 360 Wireless Receiver'
Joystick GUID: 030000005e040000a102000000010000
Joystick Number: 0
Number of Axes: 6
Number of Buttons: 15
Number of Hats: 1
Number of Balls: 0
GameControllerConfig:
Name: 'X360 Wireless Controller'
Mapping: '030000005e040000a102000000010000,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b14,dpleft:b11,dpright:b12,dpup:b13,guide:b8,leftshoulder:b4,leftstick:b9, lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7, x:b2,y:b3,'

Using xboxdrv to mimic the wireless controller as xpad did the trick.
xboxdrv --mimic-xpad --silent

thx. this worked for me.

My controller wasn't working either on Fedora 28. So I did some digging. It turns out SELinux was blocking access to the controller.

For the moment I just disable SELinux whenever I am launching the game ('setenforce 0' as root). I will try to generate the proper rules later on post them here

I am experiencing the same issue... Adding myself to the input group does not resolve it and I am not currently using xboxdrv.

In addition to what torham suggest, i.e. adding user to input group, I had to rename the file libSDL2-2.0.so.0 inside the game directory so this is the system library that is loaded.

Source and more explanation here https://steamcommunity.com/app/588650/discussions/9/1727575977525396103/#c1727575977551753884

Manjaro user here. I was able to get my controller working by deleting the libSDL2-2.0.so.0 file in the game's directory [/user/.GOG Games/Dead Cells/game for me]. From what I gather, that one was made with Ubuntu in mind, so deleting it will force the game to use the system's version.

My wired XBox 360 controller works just fine out of the box (Arch Linux), so I guess it's the wireless flakyness once more.

Hi, I am a little new to Linux, but could you please explain how I can make my xbox 360 wireless controller work with this game, I am using linux mint 19, and to be honest I don't understand how to add myself to the input group, thank you for your time.

Should be something like this, remember that you have to re-login before your groups are updated:

usermod -aG input cgr37712

so is that something that i put in my terminal:

usermod -aG input <computerusername>

is that correct?

Yes, replacing the value for your username in the <> spot. You should run `man usermod` first and read it to make sure you understand what it does.