This is now solved.

@nujm mentioned in in GitHub that he didn't update correctly before, but once he sorted it out, all worked fine:

well., I made this work. When I updated the retropie script, the console told me there were some modifications without committing, probably some updates made this changes because I didn´t do nothing at all. So basically I reverted those modifications and now it is working fine.

Thanks guys for your time and support, much appreciate it.

@Efriim said in Issue with psx and bios:

Sometimes the default directory systems directory isn't right.

Only if you move it, the RetroPie-Setup script will set it to /home/pi/RetroPie/BIOS on install - hence all the docs referencing this folder.
This usually gets unset if you use Reset Configuration from RetroArch.

That seems to have worked @mitu , thanks.

However, the script didn't want to update at first, I had to do a "git stash" beforehand as an error was thrown up over lots of updated files

Playing again now though, so happy!

@dankcushions Thank you for the reply. I figured it was something like that.

What is the best way to delete all core overrides at once? Using the retoarch menu or by deleting a specific config file?

Thanks for your help.

@DreadfulDreamZz You need to change the controller type in both the Quick Menu's Options and the Quick Menu's Controls, then restart for the Quick Menu's Options changes to apply.

I use DualShock and RetroPad w/Analog as the Core's default options and controls, while I change to Standard in the options and Retro Pad (alongside mapping the D-Pad to the left analog) on controls for games that are digital-only or don't have analog controls then save the changes for that game specifically.

The spreadsheet listed on the wiki is fairly accurate and quick way to see which controller each game used.

https://retropie.org.uk/docs/Playstation-1/#game-specific-control-information

Only covers USA games though. Go to the PlayStation DataCenter for information on everything else: it's what the spreadsheet above was based on.

http://psxdatacenter.com/sitenews.html

Might be some inconsistencies between the two as the sheet hasn't been updated much since creation, incorrect info was seen on the site yet not reported (because I was already putting so much time into the spreadsheet), and it's possible something was incorrect on the site when the spreadsheet was made and is now fixed on the site.

One of these days I need to make the time to update that PSX documentation since it has so many problems such as directing users to do manual edits when things could be done in RetroArch.

Thanks @hhromic .

I knew that it's not easy to migrate from Jessie to Stretch.

Maybe, I should wait for the next evolution of Raspberry Pi... For me, do this migration is a vast amount of time moving files out and in the system.

Thank you!

@Duxa

I know this is a necro, but I just discovered some quirky stuff that may help some folks out in this same situation.

I am working with the latest retropie on a 3b+ (usb mount roms), and in the process of building it out I noticed probably half of the psx titles I try wouldn't play at all (back to es after rgui), while the other half played perfectly. Similar to the OP's situation, these happened to be ringer titles for me... I wasn't going to give up on these without a good fight. I tried 4 different ROMs of the same game and none worked. I tried 3 different bios downloads, including mixing some of the files together, without success. So guess what randomly worked for me?

Converting the zipped cue/bin roms to chd v5 using the chdman.exe script, lol... so worth the shot in the dark!!!

I learned how to make such chd's in the process of getting reicast working, and noticed an excerpt in the retropie psx docs about chd compatibility. I already downloaded 4 slightly different copies of one of the games and none of them work. So what was there to lose by trying just one of those downloaded cue/bins as a chd. Sure enough it worked!!! So I converted the rest of the non-working psx titles to chd, and now they all work!!!

It's a 4xwin situation too... gets non-working roms to work + reduces file size + reduces file count + (this is a big one) the games load up like 100x faster using chd vs bin/cue!!!

@mitu Rebuilding from source fixed the issue. I have a feeling that when RetroPie 4.5 comes out I'm going to have to do a fresh install, my days of doing the updates and ignoring the "this isn't compatible with Jessie" warnings are numbered. Thanks again all.

@simpleethat I tried it a few times to try and get to the memory card manager, I didn't even realize that it was because of an .m3u. I always turn it off, like its a big no, or I'm in a hurry to boot my game. And now I'm kind of interested, with the same interest that we get when we first turn on our playstations. I'll leave it on and see what I find.

I half remember the playstation bios telling you what bios you're using but, I must have imagined it as all I ever see is PCSXtm.

On my Raspberry pi 2, the BIOS screen was difficult to get the sound perfect without any drops. I spent a while changing the audio freq, but then overclocking almost got it to perfect.

Random: If you leave Final Fantasy IX on for over 99.59.59 then the clock resets and changes color, mine was red, I don't know what impact this has on the game.

@mitu That's exactly the combination I'm using to "restart" the emulator. Basically, the main issue is with this way to restart.

I've also heard, there might be a different way (L1+L2+R1+R2+Select+Start, didn't work gor me).

Tested the srm save on my end as well and can confirm it works so it is definitely something wrong with the save states causing an issue in the game. Sucks losing the option to use save states but at least I can play through the game again.

Thank you all for your help.

edit: still happening after I open the retroarch menu to toggle cheats or something, have some ideas I will test and post my findings later

@Bryam_h_m make sure you have the psx bios installed. if you do, it may just be a bug in the emulator, which may have no fix.

@myname You don't need to use any config file or modify any file whatsoever. Just follow the documentation and map your controller from Emulationstation, skip the Hotkey button assignment and then choose yes to use Select as the Hotkey button. That's it.

@brimby said in pcsx-rearmed plays fine but lr-pcsx-rearmed has major sound distortion and slowdown:

@barbudreadmon By "read ahead", did you mean fast-forward?

No, read ahead is the thing to reduce input latency

The CTR issue was resolved in another thread. The dynarec in LR-PSCX Rearmed is cutting out some of the graphics. It is not AFAIK currently fixable since the game is unplayable and slow with the dynarec turned off. CTR runs perfectly in BEETLE HW and I think there has been talk (maybe just talk, insert salt as required) of it being possible to port it to the Pi 4.

@shavecat Never too late for good news ! Thanks, I haven't tried that new emulator yet, I guess I will have to !

Okay, I figured out the solution... even though all other ROMs i've tried are european they still work with the american BIOS... but only Bugs Bunny and Taz don't.

I'll only use USA roms from now on.. The screen doesn't jump with USA version of the game

GT2 fine as far as I can tell on my end. Don't have RE3