@edward_ci that's how I understand it, yeah. As far as the emulator is concerned, it's just another USB gamepad. If the two gamepads have identical device names/IDs, then they'll use the same config file. So whatever mapping like button_12 = "A" or whatever is set in the config file, will be the same for both gamepads. If "button 12" is whatever button is wired in position "6F" on the board or whatever, and you have that wired to a different physical button, then your "A" button will be that different physical button. They need to be exactly the same.

@demonscythe Hey!, I never got this resolved unfortunately. I stopped using the Piboy and got an Odroid Go Super instead, because of some multiple reasons. Maybe if you post your log here others may be able to help out. I don't know if ExperimentalPi's script auto makes the DMG controls 1st player, but that is also something to ask them about. Let me know if I can help in any way though.

My point is that when I try to install the drivers for the WM8960, I get kernel header issues on the older version of the kernel:...

The advice to update to the latest kernel/firmware was so that you don't have to install any drivers and just configure the HAT's overlay in config.txt. Doesn't that work ?

I’ve asked the software developers, but they keep telling me to upgrade to 5.10 kernel, which RetroPie seems to not work with for me anyway.

RetroPie always uses the same kernel as Raspberry Pi OS. Version 5.10 has been available for quite some time now and there's no inherent incompatibility or problems running it with RetroPie (well, except maybe this issue, but that shouldn't lead to a crash in RetroPie).

Have you experienced any issues after updating to 5.10, or can we expect any update to the kernel any time soon for RetroPie?

No, I haven't experienced any issues with 5.10. As said above, RetroPie uses the Raspberry Pi OS (nee Raspbian) kernel/firmware, there's no separate RetroPie kernel update.

@fernaretro yes, please do.

I have 44 systems running well over 3500 games across them... all on a Pi3b+ standard settings, no overclocking. I get pretty good results until the Amiga 1200/IBM PC/Atari St/Apple IIgs era of games. Then it's a little touch-and-go with the performance. I don't run any N64 and very few PS1 games. No PSP games at all.

I'm thinking it's time to move up to a Pi4, but I'm waiting till the next revision. From what I've read, it will be returning back to a standard HDMI slot which is what I want.

Good luck.

JamR

@hellothere

I boot my Pi4 from USB but I use a conventional 2,5" harddrive.
This is much more reliable and faster than using SD-cards.
My experience is that normal harddrives live much longer that SD-cards and SSD-drives.
SSD drives are based on the same technology than SD-cards, go figure.

I haven't used an SSD on my Pi4, but my overall experience with SD-cards and SSD drives is not that good.
Ok, SSD drives are fast and use less energy, but just like SD-cards their lifetime is limited versus that of physical hard-drives.
If you do a lot of writing then SD-cards and SSD-drives will not live that long. ( for example, compiling programs with a swap on will definitely age the SSD faster )
Three of my 128GB SD-cards didn't live longer that 7 months or so, go figure !

The backdraw of physical harddrives are mostly the energy consumption.
My PI4 can supply my 2,5" over the USB without an external powersupply but, besides the mouse and keyboard, you can't connect other hungry devices anymore.
Using harddrives with external power should fix this problem though.

And remember, you have to have a good PI4 power supply or you get trouble also !
The official PI4 power supply is 5.1 V and 3.0 A !!!

@barbudreadmon
Thanks for the info.

@mitu thanks for the hint. I've used the values from the docs as I'm hiding anything at boot time :-) I've reduced loglevel to 2 (perhaps I'll try 0). This case can be considered closed.

Thanks again.

@stonededge You already have a topic opened, to which you've received a reply - please post there.

@mahoneyt944 That worked, thank you very much for the help.

Thank you everyone for your feedback and suggestions! I think I figured out what is causing the conflicts I am experiencing, for which I'll reference the following screenshot of the mame input configuration for sf2.zip:

sf2-210802-174734.png

My rebindings are attempting to "relocate" buttons, assigning buttons 1->2, 2->3, 3->6, etc... (as noted before). The end result is that only the RetroPad bindings changed, not the keyboard key bindings. The OR clause in the mame mappings thus maps one key/button to two events and that ends up breaking things!

@dankcushions said in Unable to configure per-ROM input override for MAME:

point of order, but they do, but it relies on you using the correct physical location or your buttons:

B A R
Y X L

I had not considered this, but this seems very sensible given mame's default inputs (key or retropad event). I had have wired things using the IPAC switch numbers, which won't be hard to change.

1 2 3
4 5 6

EDIT
Here is a post descripting this same problem, which is due to the "simultaneous" core input setting in retroarch:

https://retropie.org.uk/forum/topic/29976/mame-button-mapping-conflicting-with-retroarch-button-mapping

Thanks for your replies, I'll look into this more carefully when I get the chance.

@jhocking said in how to set Turbo fire speed?:

And can that be modified from the RetroArch gui just like setting the turbo button, or do I need to edit the config file text?

The settings are accessible only when Show Advanced Options is enabled (menu_show_advanced_settings = "true"), they're found under Input -> Turbo Fire.

9385ab4e-8102-4a02-bbbb-517bfeafd6cc-image.png

Please add some more details about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

What game are you trying to run and what format is your ROM (.cue/ .iso ) ?

@jiryn we only get email notifications for your first version of the first version of your post, FYI.

When I tell Retroarch to reset defaults, I lose all controller access.

yeah don’t do this. retroarch defaults are not retropie defaults and will not work.

One of the perils when updating to the bleeding cutting edge firmware.

Unless it is really needed I advise to stick to a kernel and firmware that works well on your setup and make it permanent and use a more cautious update than full-upgrade.

Still looking for a solution on this issue if anyone has any advice.

@bdpyle Word of advice - don't use 'Reset Configuration' in RetroArch, the defaults it creates are not best suited for a Pi/RetroPie installation.

@bdpyle duplicate of https://retropie.org.uk/forum/topic/31061/psx-and-psp-games-won-t-start-after-adjusting-retroarch-settings ?