Problems while building my arcade with - DragonRise Inc. Generic USB Joystick
-
I found something interesting with dmesg :
login as: root root@Recalbox's password: # # dmesg | grep DragonRise [ 1.923431] usb 1-1.2: Manufacturer: DragonRise Inc. [ 2.123462] usb 1-1.3: Manufacturer: DragonRise Inc. [ 2.613596] input: DragonRise Inc. Generic USB Joystick as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:0079:0006.0001/input/input0 [ 2.613853] dragonrise 0003:0079:0006.0001: input,hidraw0: USB HID v1.10 Joystick [DragonRise Inc. Generic USB Joystick ] on usb-3f980000.usb-1.2/input0 [ 2.615054] input: DragonRise Inc. Generic USB Joystick as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0079:0006.0002/input/input1 [ 2.615295] dragonrise 0003:0079:0006.0002: input,hidraw1: USB HID v1.10 Joystick [DragonRise Inc. Generic USB Joystick ] on usb-3f980000.usb-1.3/input0 #
Is there an error in the last line and position, should it not be input 1 instead of input 0 ?
-
@dragu should compare with 2 xinmos. I believe it's normal when a controller handles a single player
As long as they are mapped on separate /dev/input/eventX
-
@Substring
I totaly agree with you that 1 controller handles a single player. But here he just forget controller #1. So I think that you should be able to map controller #0 to all possible players, with controller #1 (not existing) should be the same.
If I now define in Retroarch Menu, that Player 1 is not existing, after this he map the controller #0 to Player 2, also in game. -
@dragu do your encoders respond on separate events when you try
evtest
? -
@Substring
Absolutely# evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: DragonRise Inc. Generic USB Joystick /dev/input/event1: DragonRise Inc. Generic USB Joystick /dev/input/event2: 1byone Keyboard Select the device event number [0-2]:
and he even dont forget my keyboard
-
@dragu so it's a pure ra problem
-
@Substring
Small chance that they resolve with newer version. -
@dragu have you checked their github to see if an issue points at your problem ?
-
@Substring
Not yet deep inside. Just find traces everywhere. So I will collect. We have 1.6.9 so that's important also. -
@dragu they won't bother with a not up to date RA ...
-
@Substring
Perhaps, but the time that this story is trailing over the versions...
Discussion in Retropie : https://github.com/RetroPie/RetroPie-Setup/issues/1798
(The USB Socket toggeling remember Bells phone time with a lot of young ladies and electric plugs )
and in the Retroarch Github I found the following about controllers :
https://github.com/libretro/retroarch-joypad-autoconfig/tree/master/udevWhat I cannot find in our version is the definition : input_device_display_name,
this is perhaps a possibility to distinct the twins ? -
@Substring
May be one solution, if not resolved in new version to add usb port number in udev rules ? Like this you would have different device names. -
@dragu what a pain
-
Just made my own arcade an came up with the same problem when I set up one the other f**ks up. checked the device ID thing and the were both "ID 0079:0006"