Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07574 DIP/Input Trivial Always Feb 24, 2020, 21:48 Feb 29, 2020, 12:42
Tester 280696516 View Status Public Platform MAME (Official Binary)
Assigned To Resolution No change required OS Windows 10 (64-bit)
Status [?] Closed Driver
Version 0.214 Fixed in Version Build 32-bit
Fixed in Git Commit Github Pull Request #
Summary MESS-specific 07574: psu and clones: Suggestion for default input layout
Description default input is R1 Z, L1 X,R2 C,L2 V.
this is not natural according to ps controller.
My suggestion is L1 Z,L2 X,R1 C,R2 V
Steps To Reproduce
Additional Information
Github Commit
Regression Version
Affected Sets / Systems psu and clones
Attached Files
png file icon 屏幕截图(69).png (520,777 bytes) Feb 24, 2020, 21:48 Uploaded by 280696516
There are no relationship linked to this issue.
User avatar
Feb 25, 2020, 19:27
Outside of the slight change in default suggested, you need to check your default.cfg file(s). There is something broken or mis-configured and is showing a differently than a default setup, particularly in items which show "or (space)" and seem to be missing a proper assignment. I'll acknowledge this, but I honestly don't feel it is anything that will get put to mainline sources as local configuration isn't guaranteed to be optimal but best case for all machines.
User avatar
Feb 29, 2020, 11:47
There's nothing wrong with his config, it's a bug introduced by Bletch. I fixed it a few months ago.

Regression happened here: and it was fixed here:

They just need to update.
User avatar
Feb 29, 2020, 12:42
Versions after 0.216 have this "or (space)" display corrected and isn't actually a configuration issue but a real MAME bug.

As far as input ordering, I pulled out my PS1 controller w/USB adapter and each of the inputs correctly corresponds to the button is it default assigned to.
In the PS1 and other later console cases, we have to keep consistent with all other machines in MAME and the unique presence of 8+ action buttons for each player makes the default keyboard mapping not exactly optimal or in some cases it comes default as "none" requiring you to map them yourself for function.

I'd say there isn't anything we can do here. We can't customize the keyboard inputs to meet everyone's needs and fit non-standard control options - some user tweaking is needed (and encouraged) to make something that you find comfortable on your machine with your setup.

Closing this one out as No Change Required.