ID joypad error

Bimbo

Hi everyone, excuse my English.
I have a problem with batocera on a recent 64bit PC system with Ryzen3.
Practically everything works but it makes confusion on the joypads.
I installed it all in a cab with two identical arcade pads.
On the first start after the initial configuration, everything works.
Just enter a game and go out and the pads don't go anymore.
I noticed that first the player 1 was # 0 and the player 2 # 1 then strangely they become # 3 and # 4 and so on. Logically some emulators no longer go because the pad configuration skips.
I then have to delete the file with the pad configuration and start again from # 0 and # 1.
The pads are recognized as generic pads and are zero delay encoders.
What can I do?
What does it depend on?
Can you help me?
Thanks.

Bimbo

Let me explain better, two identical encoders, Dragonrise, are connected on two USB of the PC. At the initial configuration Batocera recognizes them as ID0 for the dragonrise player 1 and ID1 for the dragonrise player 2. Up to here everything is ok. Everything works. When I start a game I sometimes invert the players and when I exit the game and control the pad configurations from the menu, it tells me that pads with ID3 and ID4 are connected. This is repeated to the point where I even saw the pads with ID12 and ID13. In the end I have to delete the configuration by deleting the file and then batocera sees the pads again with ID0 and ID1. The thing then repeats itself. I also noticed this problem on another PC. I think maybe it's an incompatibility with the same encoders. I do not know. I ask your advice on this. To give you more information I can tell you that the PC is new and does not present this problem with Windows. If you have advice I await your info on this because I don't know what to do, if it depends on the encoder or is a bug of batocera. Thanks.

erik_over

I have a identical problem. But i have a twin usb controller cy-1121.

Bimbo

Have idea for solving this problem? Thanks.

erik_over

In beta 5.24 the problem continúe. Any ídea?

Bimbo

I tried the modified version of batocera called plus in the 64 bit version. It seems that in that version the pads are identified with a name instead of generic pads. Probably depends on some drivers added in the plus version. At that point I told batocera to select which was the encoder of the first player and which of the second and the problem was solved. At this point it looks like an original batocera problem and how it identifies the pads. I also noticed that in the fork plus, all the external emulators are configured from the initial drive, which on the original batocera does not and must be done by hand by pressing F1 and configuring the emulators. In the fork, wifi also finally works as it recognizes my wifi key. At this point I think I'll keep the fork as long as batocera won't solve the pad problem and the dolphin configuration that isn't stored. The only thing that does not work in the fork is the configuration of the PPSSPP which is not going in any way. However, I also tried 5.24 but it has the same problems. Moreover Flycast is very slow while in the fork it is more up to date and goes very well with Naomi and Dreamcast. In the hope that everything will be solved in 5.25 I look forward to it If anyone still finds an alternative to the pad problem I would be glad to know how he did it. Hello.

hootowlserenade

Bimbo

What is this "plus" version you are using? I posted another thread with a similar problem, but my issue was with one controller that won't work in games unless it's id number is 0.

Here is my post:
https://batocera-linux.xorhub.com/forum/d/2906-wireless-controller-id-number-issues

Bimbo

I did various tests, from what I understand batocera creates the problem of reversing the pads randomly ONLY if you have two equal USB pads. In the case of different pads, it can be locked by fixing the names of the encoders in players 1 and two in the configuration. Using batocera plus the problem occurs but does not reverse the names of the pads. The same encoders I tried them with windows / retroarch and with rear-view and the problem does not appear. So I think it's a bug in recognizing pads when they're the same. However it happens that from id0 and id1 you pass to id2 and 3 but fixing the position of the players, having different decoders names, the position of the pads is not inverted. If they are the same the system goes into confusion.

erik_over

I found this post from 6/01/19 where it indicates a problem like a we have.
https://batocera-linux.xorhub.com/forum/d/1791-bug-in-kodi-joypad-control-gets-messed-up-when-2-controllers-connected

Bimbo

hootowlserenade
I'm using the version of Plus 0.1 but the same problem is present from version 5.22 of classic batocera. Whenever there are two identical pads on USB in a PC, the 1-2 player swap problem is created and pads are not created and the commands no longer work. The Plus version is a modified version of batocera 5.23 in which emulators have been updated and added Wine, Openbor, and other retroarching plugins.

Tatayoyoh

Hi guys, I have the same problem with Batocera 5.24 on Tinker board and a "Twin USB Gamepad".
After booting, I have for example two controllers in configuration panel :

#0 TWIN USB GAMEPAD
#1 TWIN USB GAMEPAD

Each time I start a game, controllers are not usable and controllers IDs are rising. So I have then in configuration panel :

#2 TWIN USB GAMEPAD
#3 TWIN USB GAMEPAD

I want to mention that I had to specify the /boot/extlinux/extlinux.conf boot line to have my two controllers well detected (as two independants controllers) :

LABEL batocera.linux
  LINUX /boot/linux
  FDT /boot/rk3288-miniarm.dtb
  APPEND initrd=/boot/initrd.gz label=BATOCERA usbhid.quirks=0x810:0xe001:0x040 rootwait quiet loglevel=0 console=ttyS2

My controller is this one :
https://www.amazon.fr/gp/product/B078W5JQ1Q/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1

Thanks for your help !