PS1 games that have bugs in retropie
-
I am having the same issue with Driver (not being able to restart a mission). But you can of course just use a Retroarch save at the start of the mission and reload that save after failing. I yet have to come across a gamebreaking bug on any PS1 game. I will test my collection over the coming weeks and add my experiences in the spreadsheet.
Edit: I forgot about Pro Pinball Timeshock. That game has a lot of issues. I don't think I ever got the PS1 version to work on the Pi. The eboot on the PSP had no music and the ball left permanent traces all over the screen.
-
Thanks, all the help is appreciated. Propably some of these issues we simply can't do nothing about, only some custom game fixes would work.
PS: I'll add my own experiences back into the sheet, but I also keep yours in there. That helps us tracking the possible reasons and fixes for the issues.
-
@dd-indeed Yes, sorry about that. I immediately regretted deleting your note, but it seemed I couldn't reverse it.
-
No problem I fixed it already.
And to all who are applying information to the sheet, remember to put your nickname to the end of the notes, so that we can keep track who has done and what.
-
I've found that Tomb Raider 2 freezes in certain parts if you try to pull up the select menu. I've tried 3 different ROMs and all of them have done it.
-
What RPi are you using and which emulator, lr-version or non-lr-version ? Write them down to the sheet if you want. I can do that as well.
-
thanks for taking initiative and starting this document.
i've added 5 games that don't seem to have any issues on a pi 3:- Apocalypse
- Jeopardy! - 2nd Edition
- Pocket Fighter
- Ten Pin Alley
- Xena - Warrior Princess
-
There is some missing info on the notes, that who has tested, couple games on the list just have OK in them, but no other information.
-
I just tried Crash Bandicoot Warped and I have zero issues. Sound is great, no pop up or other visual artifacts. I play all games from a usb stick by the way. Maybe something is wrong with the compression of your eboot?
-
I don't use eboot, I use just the regular BIN-images. Compressing BIN-images to EBOOT doesn't make the quality of the sound better. It's something else I'm having issue with. The overall audio is a bit muffled, no matter what Interpolation options I used.
I didn't also have any popup, but I noticed couple small artifacts with the screen trasitions on multiple games, such as fade outs, etc, when loading another map, etc.
-
@dd-indeed I haven't changed anything in the settings..Warped worked great straight away. Maybe try a different image?
-
I could yea.
Now I figured out something: VSync is messing up the audio in some games, causing them to stutter all the time. I now disabled it problem was solved, C-12 at least runs smoothly now.
Edit: It helps, but apparrently doesn't fix it completely.
-
@dd-indeed RPi3, using the stock lr-pcsx-rearmed.
-
Allright, I included your notes there.
-
Btw, since you have zero issues with most games we both have been testing, could you write down the information about the system you use, possible overclocking values, VRAM value, emulation settings and the memory devices you use. I could then make some comparison and start to search why such issues happen on me, but not you.
Edit: I think that we could open up Discord channel for these tests, where we could share information, so we don't need to spam this whole topic with other troubleshooting and information.
-
@dd-indeed said in PS1 games that have bugs in retropie:
GT2 = Various graphical glitches when having fade out transition (Disabling interlacing from config helped a bit)
Die Hard Trilogy 2 = Slow menu, music plays at half speed, sluggish gameplay and sound issues. (edit: putting Sound Interpolation to Simple helps a bit)
both these settings (interlacing off and interpolation = simple) are the default in retropie (indeed, just with lr-pcsx_rearmed in general). i suspect your config is messed up, or at least non-default.
you can see the default settings here: https://github.com/libretro/pcsx_rearmed/blob/master/frontend/libretro.c#L437 - the first option in the pipe-delimited list is the default. eg:
{ "pcsx_rearmed_spu_interpolation", "Sound: Interpolation; simple|gaussian|cubic|off" },
default =
simple
-
Well could I just delete the config and will the Retroarch just create new one automatically after that ?
If that is not helping, then the issue lies within the data loading stream, that causes these sort of issues, where the game is unstable and the audio has all sorts of cuts and lag.
-
@dd-indeed said in PS1 games that have bugs in retropie:
Well could I just delete the config and will the Retroarch just create new one automatically after that ?
delete which config? there's several relevant ones.
/opt/retropie/configs/all/retroarch.cfg
/opt/retropie/configs/psx/retroarch.cfg
DO NOT delete these, as retroarch's defaults are not good for retropie. instead, reinstall retroarch AND lr-pcsx_rearmed via retropie-setup, and then look in those folders forretroarch.cfg.rp-dist
files, and delete the above, and rename EACHretroarch.cfg.rp-dist
toretroarch.cfg
/opt/retropie/configs/all/retroarch-core-options.cfg
you could delete this, but maybe you want to keep your emulator settings in other emulators. if you open this file and remove all pcsx lines, then that will reset pcsx back to the defaults, at least.now, if you've (knowingly? unknowingly?) created per-game configs or anything like that... all bets are off.
i would be tempted to just start again from a brand new image.
If that is not helping, then the issue lies within the data loading stream, that causes these sort of issues, where the game is unstable and the audio has all sorts of cuts and lag.
can you post your /boot/config.txt ?
-
Here's the config:
I can do some minor tweak to some stuff, but I won't start to go through the entire system again, as it otherwise works well.
-
arm_freq=1350 gpu_freq=525 core_freq=525 sdram_freq=500 over_voltage=6 v3d_freq=525 force_turbo=1 avoid_pwm_pll=1
this is a fairly aggressive overclock (and mostly pointless, IMO). one possible symptom of too much overclocking can be memory corruption which could lead to failed memory reads (stuttering, etc). the system will also downclock (perform worse) when temperature is too high.
whenever you're debugging anything, always remove all overclocking.
gpu_mem=400
this is either redundant or pointless. either way i would get rid of it. see https://retropie.org.uk/docs/Memory-Split/
I can do some minor tweak to some stuff, but I won't start to go through the entire system again, as it otherwise works well.
i can understand that, but that's one of the things that makes issues very difficult to debug or pointless to compare, when people have made such drastic changes to their systems.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.