Recalbox not recognizing 2nd player 03H Dual Arcade 3...

[Andrei]

Still not working :S

i installed fresh recalbox with updates to 4.1

https://file.ac/bM5uh6Yd7xk/

I am thinking to connect 2nd player to Pi GPO ...it will work?

[acris]

@Andrei
Post your cmdline.txt too

you need to connect all joystick and buttons on your usb encoder.

[Andrei]

dwc_otg.fiq_fix_enable=1 sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0 console=tty3 loglevel=3 elevator=deadline vt.global_cursor_default=0 logo.nologo root=/dev/mmcblk0p7 rootwait fastboot noswap ro

all mjoysticks buttons are connected, #1 and #2 in mirror.

[Andrei]

sadly i could't fix it so i connected 2nd player to pi gpio.thx for help

[RebeccaRGB]

I fixed this by editing boot.ini and adding usbhid.quirks to this line:

setenv bootargs "${bootrootfs} ${console}"

like so:

setenv bootargs "${bootrootfs} ${console} usbhid.quirks=0x16c0:0x75e1:0x040"

I know this topic is old but I was having this same problem with recalbox 17.12.02 and this was the top Google result for "recalbox 3h dual arcade".

[Substring]

@rebeccargb don't necro such annold topic ... You're using an odroid, not a pi. Boot confg files and syntax are quite different

[Andrei]

Fixed with Recalbox release: 18.03.16

Thank you

[JHaleIT]

Sorry to bring up an older post, but I have the same issue with a different product ID. I found information about it, but it's in Chinese..

I have no clue what it all means.. lol I'm on x86 version of Recalbox..

Up and left on both joysticks refuse to work..

https://www.tipga.com/e/59cfad8a3286fe2a4ac123c8

[JHaleIT]

Any update with this?

[JHaleIT]

More information here: https://retropie.org.uk/forum/topic/7832/fix-up-left-joystick-direction-for-tht-2p-arcade-controller-with-device-id-0x75e1

but it's for Retropie.. I'm using x86/x64 version and ID information: 0x16c0:0x05e0:0x040

[JHaleIT]

There's a patch file I found that fixes the problem, but how do I apply it?

Here is the patch: http://ithink.ch/blog/files/xin-mo/0001-hid-Add-new-driver-for-non-compliant-Xin-Mo-devices.patch