Zero Delay USB Encoder - Proper Button Order?

icebear81

I found this older thread which alludes that a Zero Delay Encoder has a preferred order for the buttons - https://retropie.org.uk/forum/topic/17439/zero-delay-usb-encoder

The reason I ask, is that when defining buttons in MAME, the buttons do get a naming convention that does not align with my gamepad definitions in emulation station. In other words, I press what Ive defined as "A" in emulation station, and MAME will say JStart (or something like that) ....

I have read numerous times (and also ETA Primes video) where it is said 'Just plug them in, making sure P1 and P2 are in the same order.

Looking for thoughts or confirmation on this?

mitu

The encoder has no 'preference', if you've done the mapping in Emulationstation, that mapping is saved for RetroArch based emulators and it's up to emulator how it maps the RetroPad to the game's inputs. Arcade games are different than consoles, since each arcade game its own set of buttons.

You didn't specify which emulator are you using and which game you started, MAME based emulators allow you to configure the inputs (for that game) by using the MAME menu (pressing tab while in game).

As far as RetroPie is concerned, then yes, just plug them in and make sure they're wired identically, then you map one of them and that's it.

icebear81

Thanks .. I understand that it can all be configured, I was more so asking that if it was wired as specified (with certain buttons connected at specific places start == start, etc) that by default (and with some of the retro-pi images) it may work better out of the box

mitu

This post is deleted!

icebear81

@mitu man, now I want to know what you wrote that got deleted :(

mitu

@icebear81 Here what it should have been written:

we don't support 3rd party images - only the one available from the RetroPie project
if the encoder vendor has a preferred wiring scheme, then use it, otherwise the order is not so important for buttons, since you can always remap them. You haven't specified what encoder you're using - model/vendor/# buttons, etc.

icebear81

@mitu Thanks for the help ...

Encoder is a "Reyann-Arcade-Encoder-Joystick" [Amazon] 12 buttons

mitu

@icebear81 I see in the Amazon 2nd picture that it does have a preferred way of wiring (ST= start, SE = Select ?), so maybe follow that diagram.
You can check what each slot sends with jstest - exit Emulationstation and type

jstest /dev/input/js0

and see what button names is reporting, then press them one by one to see which is which. Exit the test by pressing Ctrl+C and type emulationstation to go back to the systems carousel.

icebear81

Thanks again! ... will check via jtest

icebear81

TLDR; -- map your USB encoder to match USB console pads

REYANN ENCODER appears to work best as
0:B, 1:A, 2:R1, 3:Y, 4:X, 5: L1, 6: L2, 7:R2, 8:SELECT, 9: START

Did some more work with this. The joysticks work great when (when mapping of multiple are the same - as discussed). There was an issue where I started to need to remap per system if I was using USB console-like controllers.

It started out to be fine, then started to become a pain - especially once I found and started to use this GEM by @meleu
https://retropie.org.uk/forum/topic/740/having-more-than-one-player-1/18

Since one set was remap, and the other wasnt, the graceful fallback didnt work.

I rewired the USB encoder pins and its all working great. PIN:BUTTON layout at the top. LOVE I