Hey! Thanks to you guys and the other linked posts, I found and fixed the same issue. I had some old overrides saved and sure enough, my Multitaps were "auto". Changed to "disabled" and all is well again in PSX land!

Thank you for your post. Having two SF30 pro and got the same issue.
After configuring as per you post above, the mapping is strange. For example, the hotkey is used to jump under tomb raider.
In other words, the controller map is not as per lib-retro "standard" for psx. Any idea how to be back on standard lib retro mapping ?
My config : retropie 4.7.3 / pi 4

@kikus said in lr-pcsx-rearmed loads but freezes at "Paused." black screen:

Built From: Started from Nachos 64GB image but updated all package from source recently

We don't support 3rd party images. Ask the author(s) of the image for support or use the image from retropie.org.uk/download.

@mitu i installed the latest precompiled binary from retropie setup script. but at least everything works now again and i do not even know what to do with this multitap thing.. not a funktion that i am missing now :)

Having looked into this, I edited /opt/retropie/configs/all/retroarch-joypads/Wireless\ Controller.cfg to set input_l2_axis and input_r2_axis and now it works :)

@raspberrycoulis i think almost every game exhibits some kind of visual bug with the speed hack on, hence the note in: https://retropie.org.uk/docs/Playstation-1/#video-double-internal-resolution - actually even without the speedhack some games can break with double resolution (doom is an example)

a blacklist for the games that are unplayable with it on is not a bad idea - could be implemented in a similar way to mupen64plus.sh

It has worked!

In a bit more detail:

I didn't add entries for P3 and P4 on retroarch.cfg because, what would I set them to if I only have two controllers? 4 and 5, assuming that I could be plugging in additional ones?

Anyway, I tried to re-add the two physical Logitech controllers to EmulationStation; it detect 4 controllers, but it would keep detecting the button presses as coming from the emulated Xbox controllers.

I then reset the controller settings for EmulationStation on the Retropie menu and again, it would detect 4 controllers, but it also would keep detecting the button presses as coming from the emulated Xbox controllers.

I had to disable xboxdrv and then it would only detect 2 controllers and the button presses a coming from the physical Logitech controllers. The conclusion here is for EmulationStation the physical and emulated controllers don't clash; the emulated ones take priority and the button presses are understood to be coming from them.

I then checked that on the Retroarch menu the emulated controllers were assigned to P1 and P2 and removed the physical controllers that were assigned to P3 and P4. And then everything was fine. The crux here appears to be that I had a clash, as both the emulated and physical controllers were assigned to players and probably registering button presses. Something that support this hypothesis is that on games where you have a grid to select your character (e.g. Mario Kart) it was fairly obvious that when I was pressing once to move one cell to the right, for instance, the selection box was moving two cells.

Thanks again for all your time helping me figure this out.

@chupachups Damn, that's a shame that never got sorted out. Thank you.

How exactly isn't it working? Are there any messages? Did you enter the command correctly letter-by-letter?

Can you uncompress a single ecm file with ecm-uncompress followed by the file's name?

@cnoto said in Playstation roms:

@cnoto Actually I got it.

… while I was typing my reply. 😉

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

The system won't take the BIOSes also when I put in games it only accepts the .cue files.

Yes, EmulationStation doesn't list the .bin file, though the game needs them. So if you copied just the .cue files, that's not going to work. A CD image has both a .cue and - at least - a .bin file.

What are the names of the BIOS files and where did you copy them ?

Does PCSX no longer work? Can anyone help me? I'm new to this so please explain to me in easy ways

pcsx-rearmed is not compatible with the Pi4. I suggest to start with the Gettig started page from the [Docs][https://retropie.org.uk/docs/] to familiarize yourself with RetroPie, then take a look at the PS1 page from the same docs, to check if your BIOS files are named correctly.

@sleve_mcdichael I tried your suggestion for Dreamcast and Playstation and it worked perfectly. Thanks!

ISSUE SOLVED

I was an idiot & using the wrong content in the config. Can't remove the post since it's after 3 minutes from upload.

There some games that doesn't work with the ir-pcsx-rearmed core. I think Psybadek is one of them.
I was test it in a Pi 3 and it crash too.

@uncledisgusting said in lr-pcsx rearmed not responding to psx controllers and can't get into menu to configure them - please help! - retropie4.6 pi 4:

system_directory = "~/RetroPie/BIOS"

That should be present in the /opt/retropie/configs/all/retroarch.cfg file, which is included in the psx config - so you should check that file and maybe reset it to the default set by RetroPie.

@quicksilver
please file this under bad behaviour on my part. Updating the setup-script and getting from source again fixed it..
Thanks... sorry for the run around.

@fordpickup said in Sound Error and Final Fanstasy Origins Failure (PSX):

(It didn't solve the weird sound error notification, but hey if it works it works!)

I think that sound/alsa error comes from EmulationStation, not fro the emulator. Use the EmulationStation menu and play with the Sound settings - Audio Card/Device are the ones that produce this error. Most likely you can change the Audio Card from Default to something else and the error will go away.

Avoid doing a basic install or update retropie after your fresh install. For some odd reason updating or doing this causes rearmed core to stop working.

@dankcushions that worked perfectly! thank you for the assistance.

@mitu Thanks! That was the bit I needed to change. I replaced "standard" with "dualshock" and now analog controls work :)