If after the update the problem is still there, follow this steps:
To disable the multitap:
Open the RetroArch menu while the game is running and from the options, enable the Show other input settings.
After that, restart the game and open again the RetroArch menu and from the options set to off the Mutitap1 and Multitap2 and you are ready.
@arcadez2003 Thanks for pointing out it was an issue with m68k intf, i had looked into the game driver and couldn't find the fix.
I did a PR at https://github.com/libretro/fbalpha2012/pull/99, but i believe such change will have a performance cost, even on classic m68k games (additional condition on every cycle, and the code for 68ec020 looks like it'll be slower).
@uraverageplayer What emulator/game are you starting when it's not working ?
Configuring the joysticks in EmulationStation would automatically create a configuration for RetroArch based emulators (the ones that start with lr-), but certain emulators are not auto-configured (i.e. advmame or mame4all).
Alright, I've tried Ubuntu MATE 18.04 beta 1 extensively and the problem does not occur on Ubuntu at all. Must be a Raspbian issue. Definitely not my hardware. I hate to dig up a month old topic, but it is what it is. A Raspbian issue.
While SD cards are awesome for size/weight/etc., how much of a speed advantage would using an external hdd be? I can't imagine an ssd adding any value over a simple 2.0/3.0 mechanical drive being that the transfer rate is bottlenecked by the shared usb 2.0 bus which apparently is divided up by the all ports and the sd card reader. Is a top of the line sd card just as good as an external hard drive or are there any advantages?
@marion A very good point is made by @rbaker above. Those of us with arcade panels have built them differently, but we might also have our IPAC devices configured differently, so even if we did share config files, the hardware keys mapped inside the IPAC may not match.
The image above in rbaker's post shows the button layout as two rows of four buttons:
1sw1 1sw2 1sw3 1sw4
1sw5 1sw6 1sw7 1sw8
while my panel looks like this:
1sw1 1sw2 1sw3
1sw4 1sw5 1sw6
Furthermore, while rbaker uses LSHIFT for 1sw1, I am using LCONTROL. This is the keystroke that gets sent when I press my button wired to 1sw1 because that is how my IPAC is configured (i.e. using WinIPAC utility). The wiring matters, the location on your panel matters, and the actual key the IPAC is sending matters--and this is BEFORE any mapping is configured inside a retroarch.cfg file.
The easiest way to figure this out is to make a little drawing of your panel, label all of the switches as wired. Then, either run a test program or hook up the IPAC to a windows box and run WinIPAC. Then, mark on your drawing which buttons are sending which keys.
Finally, you should be able to look at a retroarch.cfg file which identifies the common gamepad button names, (a, b, x, y, etc) and you should be able to mark which IPAC keys should trigger these inputs based on which button/position you want to send each input.