Unable to map controls on xbox one s controller.

[Laikulo]

On fedora 43, installed via flatpak, and running under wayland, button preses are mapped properly-ish in the input diagnostics, but are labeled improperly. As the control mapper doesn't allow mapping 'unlabeled' buttons, I can't use that as a workaround.

Hat maps correctly
A and B map correctly
X => Y
Y => LB
LB => Back
RB => Start
Back => Guide
Menu => (unmapped; b11)
Guide => (unmapped; b12)

[Laikulo]

[Laikulo]

Confirmed same behavior on a source build (SDL2) outside of the flatpak.

Following messages observed on console

nCine::Backends::SdlInputManager::handleJoyDeviceEvent() ‡ Gamepad 0 [0] "Xbox One S Controller" [050018dc5e040000200b000023050000] has been connected - 1 hats, 6 axes, 16 buttons, 0 balls
nCine::JoyMapping::OnJoyConnected() ‡ Gamepad mapping not found for "Xbox One S Controller" [050018dc5e040000200b000023050000] (0), using XInput mapping

[deathkiller]

I can't find this gamepad mapping in any SDL database, which is quite unexpected for Xbox controller. You can create your own mapping and save it to ./Content/gamecontrollerdb.txt or to the same directory where the config file is saved to (I don't remember the exact path on Linux though), or you can save it to SDL_GAMECONTROLLERCONFIG environment variable.

[Laikulo]

There are three maps with the same name in current nCine for other IDs, though the maps do not line up with what I am seeing. I suspect it may be that BLE and USB have different maps.

I'll cook one up based on what i see in the diagnostics. DYK where I can find the format of gamecontrollerdb.txt? I'll try just the same format I see in the .h an entry per line and see if that works. I'll share the map here (and possibly also to SDL) once I have it.

[Laikulo]

Had success with

050018dc5e040000200b000023050000,Xbox One S Controller,a:b0,b:b1,back:b10,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b12,leftshoulder:b6,leftstick:b13,lefttrigger:a5,leftx:a0,lefty:a1,rightshoulder:b7,rightstick:b14,righttrigger:a4,rightx:a2,righty:a3,start:b11,x:b3,y:b4

All inputs in diag map as I expect with this in ~/.var/app/tk.deat.Jazz2Resurrection/config/Jazz² Resurrection/gamecontrollerdb.txt (for the flatpak distro)

I'd consider this a workaround. Does that DB belong to nCine or SDL. I'd like to get this map included upstream for others.

[Laikulo]

Over USB, it presents a different ID 030082795e040000ea02000017050000, which shows as "similar mapping" but the device presents different buttons. Making a map for that too shortly.

[Laikulo]

USB for the same controller seems to use 030082795e040000ea02000017050000,Xbox One S Controller,a:b0,b:b1,back:b6,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,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

I wonder of the UUIDs and mappings might be firmware version dependent.

[deathkiller]

Yeah, it could be even different revision of the controller, or different combination of controller/platform/operating system, and it will have different ID.

Does that DB belong to nCine or SDL.

This database is mine. Some rows are from nCine, some are from SDL, and some of them are mine.

[Laikulo]

Ah. In that case, shall I open a PR for those two?

[deathkiller]

I don't usually copy mappings from these two, so it's up to you. There are so many different mappings that I prefer to leave it up to each player to set it up on Linux themselves (because on Windows and Android, it often works without it).