Wireless Xbox 360 controller d-pad still broken with SDL-3.2.28

Support Gaming
1

Hi there,

I faced this issue with kernel 6.17 and now installed the latest version of SDL3 onto my testing branch. I have also picked the latest version of sdl2-compat, as I read somewhere that is needed too…

:: Starting full system upgrade...
warning: sdl2-compat: local (2.32.60-1) is newer than extra (2.32.58-1)
warning: sdl3: local (3.2.28-1) is newer than extra (3.2.26-1)
 there is nothing to do

However, my d-pad is still broken under 6.17 and 6.18. Does Steam come with its own SDL or what is the issue here?

Thanks for the help!

2

I’m unable to help with this generally, however, does it work with only sdl2-compat or only sdl3?

You’re in Testing. Did you recently switch to Unstable, and then back to Testing without allowing downgrades (-Syuu)? That might explain the warnings.

But wait, there’s more:

If this is indeed the issue you’re facing, then it looks like that bug has already been squashed with version 3.3.4 – you might only need to wait for it to trickle down through Arch and Manjaro branches.

I hope this is helpful.

Regards.

2 Likes
3

Thanks for the response!

I guess the warning is just because I manually build SDL and installed it onto my testing branch, which is behind the latest SDL. I was never on unstable.

The issue is actually a kernel related one, the controller works under 6.12. As the release notes list this fix in the latest SDL version I assumed it should work now.

I guess I then just wait, my hope was to switch to 6.17 as it comes with a couple of improvements for my AMD and seams to be more stable.

Regards

1 Like
4

Kernel 6.18 is the new LTS.

Given the choice, I’d prefer that rather than 6.17, and of course any improvements from 6.17 will be incorporated with 6.18 (LTS).

5

As I am curios, I need to ask this anyway:

it looks like that bug has already been squashed with version 3.3.4

I see the fix is mentioned with this release (3.2.28) and don’t see a version 3.3.4?

Could you explain what version is actually responsible under Manjaro in conjunction with Steam?

6

Yes, I first tried it under 6.18 with no luck, also I had some audio issues with 6.18. so I guess I need to wait a bit until 6.18 is more mature.

7

The bug report you gave earlier indicates;

That points to the link I gave and if you look closely, you’ll see prerelease-3.3.4 pointing to the GitHub pre-release page indicating a preview release only 10 hours ago.

I’m afraid that’s something I can’t help with, though you might be able to track it down using pacman and Branch compare to keep track of versions in each branch.

For example, pacman -Si sdl3 and pacman -Si steam will return information on the current versions of both sdl3 and steam.

Regards.

1 Like
8

Update on this one. I build SDL locally and ran the testcontroller tool. That works, so I guess it must be Steam related.

image
image963×365 56.8 KB

1 Like
9

A guess is still a guess, rather than a solution.

Perhaps you could add more detail that might benefit others facing the same or a similar issue. For example, which version of SDL you successfully built, and any other information that might be useful to those reading.

Regards.

1 Like
10

True, you are right, it wasn’t a solution and I didn’t solve the issue, as I didn’t get it working, I just realized it does not seamed to be related to SDL.

I did build 3.2.28 and ran test/testcontroller. There I see the mappings are correct, so at least related to my topic title, this does not seam to be an SDL issue. I even see the correct mappings now when I test it within Steam, but in any game they are still wrong. So my next guess is Proton.

11

This may be premature, especially considering the bug you pointed out is apparently solved by SDL 3.3.4, which might indicate SDL is still the problem.

The best I can suggest is that we close this topic without a solution, for now, and when SDL 3.3.4 is made available we can re-evaluate the issue status.

Naturally, as the OP, if you find additional information to add in the meantime you can ask a Moderation staff member to re-open the topic.

It that’s fine by you, I’ll go ahead and close it for the time being.

Regards.

1 Like
12

Yes, that’s fine for me. Sorry for the confusion.

1 Like
13

Topic closed pending release of SDL 3.3.4
OP to confirm whether it solves the issue after release.

15

I found this script as a workaround to fix the issue until SDL 3.3.4 hopefully ships the actual one.

#!/bin/bash

# Fix XBOX 360 Wireless Controller for kernels >= 6.17 and SDL < 3.4.x
export SDL_GAMECONTROLLERCONFIG=$(cat <<-END
060000000d0f00009601000000000000,Steam Controller (HHD),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,paddle1:b13,paddle2:b12,paddle3:b15,paddle4:b14,misc2:b11,misc3:b16,misc4:b17,crc:ea35,
0300a81c5e040000a102000000010000,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b12,dpleft:b13,dpright:b14,dpup:b11,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,platform:Linux,crc:1ca8,
$SDL_GAMECONTROLLERCONFIG
END
)

/usr/bin/steam

Just for convenience I’ve created a xbox_ctl_fix.desktop for triggering it quickly.

1 Like
16

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.