Controller not working in some psx games

CapNinja

Pi Model or other hardware: Pi 4 4gb
Power Supply used: the original one
RetroPie Version: 4.7.2 buster
Built From: Pre made SD Image on RetroPie website
Controller used: 1 PlayStation 4 v2, 1 8bitdo sn30
Emulator used: lr-pcsx-rearmed

After a few months I've tried some psx games and to my surprise the controller isn't responding on screen. I can use the shortcuts to open menu and exit the game but nothing else.
Tried to change in

Quick menu > controls > port 1 controls > device type

Tried almost every option to no success.

The games who I've tried and isn't working:
Bust a Move (groove) 2
Parasite Eve 2
Bushido blade 2
Driver 2

(Maybe the problem is the 2, hahaha)

The game I've played normally today:
Tony hawk series

Link to a similar problem:
https://forum.batocera.org/d/3604-pi-4-controller-works-for-everything-but-psx

mahoneyt944

@capninja I just had this happen too using pcsx-rearmed. I think it was because the configs are different with the updated core. I fixed it by uninstalling the core, then deleting:

All psx option files(.opt)
All psx remap files (.rmp)
All files in the configs/psx directory

Check configs/all/retroarch directory for some of these.

Then reinstall the core.

mitu

Seems you've bumped into a similar issue as the one reported in https://retropie.org.uk/forum/topic/28825, see if the solution in that topic works for you.

CapNinja

@mahoneyt944
Thanks a lot for your attention

@mitu
It worked. Can you please explain why it didn't worked and why it works now?
I know I can't really grasp the meanings in a programming ways, but I love puzzles.
Thanks again.

mitu

@capninja said in Controller not working in some psx games:

It worked. Can you please explain why it didn't worked and why it works now?

Due to the core changes, the previous default Multitap options ('auto') will produce this kind of issue with games that don't support Multitap.

If you start the core for the first time - after these modifications have been added - the new defaults will be set to 'disabled', but for users that have an existing set of options (where it defaulted to 'auto'), this causes issues.

CapNinja

@mitu thank you very much