@spud11 I’m sure you have this figured out now, but in your config I can see a few things that would cause your controllers to have input problems and also crossover.

In this line you are missing or between the two joysticks:

input_map[p1_button4] joystick_button[2,1] joystick_digital[0,0,2,1]

Should be:

input_map[p1_button4] joystick_button[2,1] or joystick_digital[0,0,2,1]

Also on the raspberry each controller port has a number starting with 0. In the config it’s the first number after the [ bracket. On your line above the P1 joystick_button[2,1] is mapped to Controller 3, but joystick_digital[0,0,2,1] looks good and is mapped correctly to Controller 1.

0 = port 1 (Should be P1) Controller 1
1 = port 2 (Should be P2) Controller 2
2 = port 3 (Should be P3) Controller 3
3 = port 4 (Should be P4) Controller 4

You would want to line all of these up this way. Theough your config I can see Player 1 mapped to Player 2 and vice versa. Also there are crossovers on the UI and Coin settings. Not your fault bro and I felt your pain.

Made this video and hope it helps as far as understanding the config and how to line things up. It’s for PS3 controllers but the same principles apply. Any questions reach out.

@backstander

That is funny. I guess he either meant that it doesn't work with RetroPie, or meant to list it under Pros. The review might have actually been written by a forum user named @PECONAUT. I don't know if he ever got his issue with the controller sorted out, but the "Liquid Metal" stuck out in my memory. It's a sharp looking controller and a good deal. It also might still be possible to get it working. You just never know with a 3rd party controller.

This seems to be my exact problem. My WiFi is down until I pair (press a + b) my wiimote. As soon as the pairing is complete WiFi connects. I manually configured WiFi setting right out of the gate in /etc/network/interfaces. I then tried setting a static IP in /etc/dhcpcd.conf. Still problem persists.

Any thought on how to resolve this?

Dont have turbo assigned to any button.

Just an update if anyone ever has the same problems. I went is a reset my controller configuration and rebooted to ES and was prompted to map keys like when you first boot. Mapped all the keys, switched to AM and everything works fine.

@vretro

I had the same problem and found a solution: the Remote Pi app!

It works like a virtual keyboard and mouse in one. Now you can type all keys and F1 etc. without mapping. And the mouse function is good too for Amiga use.

https://remotepi.io

And this app I use to check memory and shutt down the Raspberry Pi:

Command Pi

Hope this helps!

How would I access the emulator settings over keyboard then ?

Try and do reset all the buttons otherwise try and reset the SNES controller with keyboard.

@JonathanK 3 separate commands. Wait for each one to do its' thing then enter the next. Yes F4.

@theink
Can you share the source file of your instruction manual for your arcade ?
alt text
Thx in advance

@Phoenix_Rising66 I have the same problem. There’s no select button so i have to turn off the retro pie just to go to a different game, then after I do that I have to reconfigure the controller again

@Jeck11 I haven't messed with Bluetooth controllers yet, but when I do a Playstation controller will be one that I pick up. Apparently they're a lot more reliable than they used to be, thanks to software improvements.

Solved - THANK YOU!

@rrdein
Configuring the date is normal first time, if you're getting stuck it might not save until we get the emulator exit button mapped.

The blinking prompt is normal, there is a way to rid of it, but I think it is easier to play fullscreen. I think runcommand res 640x480 fits fullscreen on 16:9 tvs for whatever logic that exists in that.

The controller not working is normal too. Sometimes it will give you enough keys to be able to navigate the GUI and update the mappings from reicasts GUI menu.

In the folder /home/pi/.reicast/mappings/ can you identify with any existing controller.cfgs in this folder?
Are enough miscellaneous buttons working in reicast to directional navigate and select items? Often the Joystick will work, and I think select may have worked for me.
Could you also tell if either of these directories are symlinks?
/home/pi/.reicast
/home/pi/.reicast/mappings
Using ls -lawill show directory links and hiddenfiles, the symlinks should be colored lightblue.

Somehow the controller mapping needs to be made or edited to work, there is usually an existing configuration. In theory it should have the wrong mappings and all that needs to be done is get the right mappings, either from reicast-input config or copying the event number from evtest. But I guess anything is possible and it is could be loading a generic configuration until you exit the emulator normally. You could try editing in only the exit button on the generic .cfg and the other ones that match your controller, if you know the working event number from the configuration/evtest. Maybe then a proper emulator reboot will kick the configuration into line.

@PECONAUT

That would seem to indicate that it's not registering a joystick event at all, or at least not correctly. If that's the case, I don't think there's much that can be done. It's unfortunate, but third party console controllers are always in danger of limited compatibility outside of their own ecosystem.

@MadRikXIV if you remove the mic chip and capacitor on the original board you could rewire that volume slider on the board to be used

@burgoyne Did you ever get any resolution to this issue? I had the same thing happen to me and I am also looking for a solution to use the same gamepad.