This works, but I'll need to test across other games which hopefully will not involve more than sorting out correct button mappings. I noticed that for scummvm, its only backend options are for SDL2 and therefore will not work (as far as I can tell) with xboxdrv.

That's because ScummVM is already a SDL2 application and there's no need for a compatibility shim like sd12-compat.

It's looking to me as if xboxdrv may be a bit of a dead end when it comes to button remappings for non-libretro emulators in RetroPie. Can such remappings be done in SDL2 or is there another option that could be applied system-wide?

Not dead, just not widely used. xboxdrv itself is mostly feature complete and there's little development nowadays, since compatibility with Xbox controllers is offered OOB by Linux kernel modules (xow, xpad, xpadneo).

There are no alternative re-mapping solutions in RetroPit, though anything that works in Linux and without X11/Wayland could work.

I see in process list "dbus-daemon" that probably launched by xinit. When controls fails at the first launch, this process is after the game process in the list. When controls are ok during next launches, this process is before. It looks like the game need this process before.

Is there a way to delay the launch of the game started by xinit command ?

xinit '/home/pi/box86/build/box86' '/home/pi/RetroPie/roms/ports/ut99/System/ut-bin-x86'

@mitu said in mapping select+start to Alt+F4, using xboxdrv:

Try with:

... --ui-buttonmap start=KEY_ENTER,back=KEY_BACKSPACE,back+start=KEY_LEFTALT+KEY_F4 ...

this works, thanks a lot! i could swear i'd tried this...

@mitu Perfect! That's solved it! Everything works brilliantly now, thanks again so much for all your help!

@mitu WELL after I did the jtest my original controller didn't work anymore in the GUI so I did a sudo reboot. While it was rebooting I removed the dongle in sadness and saw "xbox controller disconnected" small info tag in the corner, and BOOM now xbox 360 controller is working!! I have no idea after countless reboots it worked.

Thank you

@mitu Thanks. Unfortunately, jstest gives me yet a third set of inputs different both from what event_diag and the other program told me. IT shows for my old fat PS3 controller:
(Axes): X, Y, Z, Rx, Ry, Rz

(Buttons): BtnA, BtnB, BtnX, BtnY, BtnL, BtnR, BtnL2, BtnR2, BtnSelect, BtnStart, BtnThumbL, BtnThumbR, null, null, null, null

It's anyone's guess which of those axes the dpad uses, and how the hackfile would interpret it, since even the latest event_diag still shows nothing for anything except the analog sticks...

I'm thinking event_diag just has trouble reading from these types of controllers, since it reads my arcade joystick and button sets, and my buffalo controller buttons, just fine.

@fadangalini
Fixed the problem.
By putting KEY_#302 in place of where you would put BTN_THUMB for example, works.

@mitu That worked! Thanks a million

@derebo RetroPie logs every installation in $HOME/RetroPie-Setup/logs, can you look into the last log file to see if the xboxdrv installation was successful ? You can also re-run the installation to generate a new log file and then post the log file on pastebin.com.

@mitu said in xboxdrv dpad-as-axis: is it possible? (ps3 controller + intellivision):

--displaysize=%XRES%x%YRES%

Yes. So this needs to go, I think, after the -config option for those custom jzintv commands. It wasn't working for me until I did that. If all else fails, this version of the xboxdrv line worked for me:

jzintv-xboxdrv = "sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv --config /opt/retropie/configs/xboxdrv/intellivision.xboxdrv >>/dev/shm/runcommand.log & /opt/retropie/emulators/jzintv/bin/jzintv -p /home/pi/RetroPie/BIOS -q --displaysize=%XRES%x%YRES% --kbdhackfile=/opt/retropie/configs/intellivision/hackfile_trondd.cfg %ROM%; sudo killall >/dev/null xboxdrv"

But you will need to update RetroPie from source for the PS3 buttons to show up in event_diag.
Now if I could figure out why the config menus no longer work with controllers (I need my keyboard to use them)...
For updaters: RetroPie -> Run Command Configuration -> set Joy2Key version to udev (instead of sdl) and then re-enabling the launch menu from the same set of options will fix this

@churchill7 in mame2003-plus and mame2003 this core option will be hidden unless you're playing a game that uses the feature. I recommend running pacman then going into the core options.

https://github.com/libretro/mame2003-libretro/blob/7ea22d44c0d899cf7670d458cd6dac0942839d2d/src/mame2003/mame2003.c#L187

The default is probably decent though like you observed in Tron.

@mitu thanks for all your help!

@icebear81 For Spyhunter I have the pedal mapped to the pitch :

input_map[p1_pedalgas] -joystick[2,stick,y]

I think this works for Paperboy too.

This runs the throttle for Lunar Lander:

llander/input_map[p1_paddlex] -joystick[2,stick,y]

ws

It has worked!

In a bit more detail:

I didn't add entries for P3 and P4 on retroarch.cfg because, what would I set them to if I only have two controllers? 4 and 5, assuming that I could be plugging in additional ones?

Anyway, I tried to re-add the two physical Logitech controllers to EmulationStation; it detect 4 controllers, but it would keep detecting the button presses as coming from the emulated Xbox controllers.

I then reset the controller settings for EmulationStation on the Retropie menu and again, it would detect 4 controllers, but it also would keep detecting the button presses as coming from the emulated Xbox controllers.

I had to disable xboxdrv and then it would only detect 2 controllers and the button presses a coming from the physical Logitech controllers. The conclusion here is for EmulationStation the physical and emulated controllers don't clash; the emulated ones take priority and the button presses are understood to be coming from them.

I then checked that on the Retroarch menu the emulated controllers were assigned to P1 and P2 and removed the physical controllers that were assigned to P3 and P4. And then everything was fine. The crux here appears to be that I had a clash, as both the emulated and physical controllers were assigned to players and probably registering button presses. Something that support this hypothesis is that on games where you have a grid to select your character (e.g. Mario Kart) it was fairly obvious that when I was pressing once to move one cell to the right, for instance, the selection box was moving two cells.

Thanks again for all your time helping me figure this out.

@luzer I am in this exact situation, did you manage to solve it?