T3 gamepad on GameCube

loredin

Hello Batocera community,

I have an issue with a T3 gamepad (multi environment/purpose) and observed on gamecube.
When I plugged the gamepad via usb for the first time , I configured the keys for it and it worked like a charm.
After I set some mode on the gamepad by pressing a combination of touch I was able to pair it via the bluetooth but I had to configure the keys once more for the same gamepad (I cant remember if such a step was necessary for a PS3 dualshock that I am also using on the same config).
And in that case for the first try on gamecube this seemed to work but after that (not sure if only by quitting the GC or rebooting) , some keys were not respondin anymore, and the left or right direction signql seems t be sent continuously.
In the batocera environment and even in the PS one this seems to respond properly.
So I suspect that there is a conflict between the USB and BT key configurations (key indexes are different when I configure the gamepad in USB and BT) and I am not sure if there is something Batocera can handle or if this is an emulator issue. Any further step to troubleshoot my problem would be welcome.
I am using batocera29 on a N2 board.

Kind Regards

loredin

Here is an extract of a snoop using btmon just in case ?

`Bluetooth monitor ver 5.47
= Note: Linux version 5.8.18 (aarch64) 0.091060
= Note: Bluetooth subsystem version 2.22 0.091076
= New Index: 00:1A:7D:DA:71:15 (Primary,USB,hci0) [hci0] 0.091080
= Open Index: 00:1A:7D:DA:71:15 [hci0] 0.091081
= Index Info: 00:1A:7D:DA:71:15 (Cambridge Silicon Radio) [hci0] 0.091084
@ MGMT Open: bluetoothd (privileged) version 1.17 {0×0001} 0.091089
@ MGMT Open: btmon (privileged) version 1.17 {0×0002} 0.091181

ACL Data RX: Handle 72 flags 0×02 dlen 16 #1 [hci0] 0.110471
Channel: 65 len 12 [PSM 0 mode 0] {chan 0}
a1 07 80 80 80 80 88 00 00 00 00 00 …………
ACL Data RX: Handle 72 flags 0×02 dlen 16 #2 [hci0] 0.855444
Channel: 65 len 12 [PSM 0 mode 0] {chan 0}
a1 07 80 80 80 80 88 00 00 00 00 00 …………
ACL Data RX: Handle 72 flags 0×02 dlen 16 #3 [hci0] 1.604204
Channel: 65 len 12 [PSM 0 mode 0] {chan 0}
a1 07 80 80 80 80 88 00 00 00 00 00 …………
ACL Data RX: Handle 72 flags 0×02 dlen 16 #4 [hci0] 2.335404
Channel: 65 len 12 [PSM 0 mode 0] {chan 0}
a1 07 80 80 80 80 88 00 00 00 00 00 ………… `

loredin

hi I am really looking in all directions since I could not troubleshoot that in one shot, today I checked ps -a after launching the game with the controller connected via bluetooth :

I see there partially :

python /usr/lib/python2.7/site-packages/configgen/emulatorlauncher.py -p1index 0 -p1guid 0500000049190000020400001b010000

I check in /usr/share/batocera/datainit/system/configs/emulationstation/es_input.cfg and I found following entry :

But afaiu it should take either :

or <inputConfig type=“joystick” deviceName=“SHANWAN Android Gamepad” deviceGUID=“03000000632500002605000010010000”>

loredin

ok after looking a bit more around I found my gamepad in /userdata/system/configs/emulationstation/es_input.cfg

(deviceGUID is also there for inputConfig type=“joystick” deviceName=“ipega Bluetooth Gamepad)

So I thought maybe there is some kind of conflict with the “ipega Bluetooth Gamepad" but trying to remove it , didnt help.

I looked then in the dolphin side (since the gamepad is working fine with psx that is using retroarch); I found the following lines in /userdata/system/configs/dolphin-emu/GCPadNew.ini :

[GCPad1]

Device = evdev/0/Gamepad

I have then googled a bit and following evtest gives me :

/dev/input/event0: meson-ir

/dev/input/event1: Logitech M705

/dev/input/event2: Gamepad Keyboard

/dev/input/event3: Gamepad Consumer Control

/dev/input/event4: CHICONY HP Basic USB Keyboard

/dev/input/event5: Gamepad Mouse

/dev/input/event6: Gamepad

Only when I type in 6 , I have a response after pressing the buttons, so I am wondering if dolphin is not using the “wrong” event ?