Suggested configs for Wireless work for wired

[Rumbles]

I have just tried using the suggested steam string for my wired controller:

[ 40.205654] hid-generic 0003:2DC8:310A.0007: input,hidraw1: USB HID v1.11 Keyboard [8BitDo 8BitDo Ultimate 2C Wired Controller] on usb-0000:00:14.0-3.2/input1

But it didn't fix the issue

I compiled the C and ran the program and it output the same string as the wireless example, so I tried that and it worked (I don't have a wireless controller, so no idea why that worked)

Not a major issue, but maybe worth nothing that the string does not always match the controller...

Regardless thanks for this, I was pulling my hair out as I can't get a modern pad that works on silksong/linux! Until now!!

[NelsonAPenn]

Hi, I'm not sure I understand completely. The string you shared doesn't look like a controller config... which configuration was it that you tried?

[Rumbles]

Hi, no sorry, the string I shared was from lsusb, just to show you I'm using a wired pad The wired pad line didn't work for me, I had to use the wireless pad line. I first tried the wired pad line, when it didn't work. I compiled the c code and found the output was the same as the wireless pad line in your examples The wireless line seems to work for some wired pads too

…

On Wed, 29 Oct 2025, 23:56 Nelson Penn, ***@***.***> wrote: *NelsonAPenn* left a comment (NelsonAPenn/silksong_linux_controller_fix#5) <#5 (comment)> Hi, I'm not sure I understand completely. The string you shared doesn't look like a controller config... which configuration was it that you tried? — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB626UUN4IZZ2WIIIZ3LET332FAZJAVCNFSM6AAAAACKOVBHNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINRUG4ZDSMBYGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[NelsonAPenn]

OK gotcha. So when you said it was the same as the wireless pad line, did that include the name as well?

The wired config in question was added in #3 ... perhaps it could be some sort of version differences with SDL3?

I'll leave this issue open and people can upvote if they run into the same problem.

[Rumbles]

Yes, including the name, I have two of these pads, tried with both, they work fine if I use the wireless string in the game options, but if I use the wired string it doesn't fix the issue where the trigger toggles

Thanks again!

[thalesfmac]

I believe that, when in XInput mode (connecting the cable while holding X), the 8BitDo Ultimate 2C Wired Controller is identified as the Wireless one by SDL. If you set it in Direct Input mode (connecting the cable while holding B), it is identified as the Wired version.

[thalesfmac]

For me, the output from the C program is slightly different from the one in known_configs.md.

When configured in XInput mode, the C program outputs

SDL_GAMECONTROLLERCONFIG='03000000c82d00000a31000014010000,8BitDo Ultimate 2C Wireless Controller,a:b0,b:b1,x:b2,y:b3,back:b6,guide:b8,start:b7,leftstick:b9,rightstick:b10,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,crc:4e60,platform:Linux,'

which differs minimally from the one for 8BitDo Ultimate 2C Wireless Controller for the crc:4e60 part.

When configured in Direct Input mode, now the output is
SDL_GAMECONTROLLERCONFIG='03000000c82d00001d30000011010000,8BitDo Ultimate 2C Wired Controller,a:b0,b:b1,x:b3,y:b4,back:b10,guide:b12,start:b11,leftstick:b13,rightstick:b14,leftshoulder:b6,rightshoulder:b7,dpup:h0.1,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,leftx:a0,lefty:a1,rightx:a2,righty:a3,lefttrigger:a5,righttrigger:a4,crc:1939,platform:Linux,'
which also differs minimally from the one for 8BitDo Ultimate 2C Wired Controller, now for the crc:1939 part.

The only difference between my controller and a factory-default one is that I have upgraded its firmware, following the procedure at 8BitDo's website on Windows.

[SM64User]

My experience mirrors thalesfmac with Dinput and Xinput (I have a 8BitDo Ultimate 2C wired controller). if I use the 'known_configs.md', the controller only works in Dinput mode. but using your program mine outputs the exact same as thalesfmac and then Xinput mode works.

I also updated my firmware on the controller and while I used Windows (Win10) I did it on Linux through a QEMU/KVM virtual machine to update the firmware on my controller.

======

I have tested it on the current Hollow Knight v1.5.12620 (native Linux version) through Lutris using a ".sh" file and even rumble function works when dashing etc. so given that works, I would assume it will work on Silksong to (which I still have not actually played yet) as I have only tested basic menu function and at very beginning there and no obvious issue.

my '.sh' file is this (which I load from root of game directory with Lutris as I am running it completely outside of Steam (one just has to rename 'steam_api64.dll' to '_steam_api64.dll' as that disables it so it runs outside of Steam AND the in-game achievements menu works (I think GOG version is similar))...

SDL_GAMECONTROLLERCONFIG='03000000c82d00000a31000014010000,8BitDo Ultimate 2C Wired Controller (Xinput),a:b0,b:b1,x:b2,y:b3,back:b6,guide:b8,start:b7,leftstick:b9,rightstick:b10,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,crc:4e60,platform:Linux,' ./hollow_knight.x86_64

NOTE: one can tweak the last part to match whatever your executable file is named as. if there are spaces in your file name (which is the case with Silksong) just use, for example... "./Hollow Knight"

on Silksong, since my executable file is named exactly 'Hollow Knight Silksong' I use... "./Hollow Knight Silksong"

p.s. for a '.sh' to work it must be marked executable and the same with the main games executable file otherwise Linux simply won't allow it to start up. so from terminal for example... chmod +x NameOfShellFile.sh