Ps1 games will not load

[zombiegasm]

Hey guys, noob here. I'm desperate as I have tried many fixes for this issue but I cant seem to figure out what the issue is.

While using lr-psx-rearmed (installed witg either binary or source) and having double checked to make sure the BIOS is in the file, I get very irregular results when trying to play ps1 games. Same problem as commonly reported: loading screen pops up and then goes back to the romlist. The most success I've had so far was when about 20 of the roms would work (the first 20 in alphabetical order) but no others would. Other times none of them work.

I have tried to play them with and without the optional packages (ppsspp and redream are thr ones Ive downloaded), installed lr-psx-rearmed from both binary and source, tried uploading a few roms at a time, but I cannot get stable results.

I have a pi4 and manually installed the disk image. Ive tried uptating the script, updating the packages, removing all packages that I wont be using... pretty much anything my noob brain can think of. What am i doing wrong or overlooking?

Thanks!!!

[sleve_mcdichael]

@zombiegasm said in Ps1 games will not load:

having double checked to make sure the BIOS is in the file,

What BIOS is where? I've been having good results with psxonpsp660.bin using lr-pcsx_rearmed. It goes in /home/pi/RetroPie/BIOS on the RetroPie device, or in the bios folder on the network share.

What format are your ROMs in?

[zombiegasm]

@sleve_mcdichael I haven't tried that particular BIOS yet, but I'll give it a whirl tomorrow. The files are in bin/cue format. Is there a better format? Im willing to put the time in to change the file types as I've already put way too much time into this, considering I consolidated all bin files per rom into 1 and am also using the m3u format for multi disc games.

Thank you!

[sleve_mcdichael]

@zombiegasm said in Ps1 games will not load:

@sleve_mcdichael I haven't tried that particular BIOS yet, but I'll give it a whirl tomorrow. The files are in bin/cue format. Is there a better format?

They're not still .ziped, are they? .bin/.cue should work but they have to be unzipped. I don't know anything about consolidating the .bin files, but I presume it's expected to work well and not something bleeding-edge experimental you're doing? I went a different route for keeping my folders clean with the .chd format, converting my bin/cue sets with the chdman tool; one file per disc, works with .m3u playlists, and lossless compression up to 50% can save quite a lot of space, considering CD games make up only about 10% of my titles but over 90% of my storage: https://retropie.org.uk/docs/CHD-files/#creating-chds-from-cd-roms

When you fire it up tomorrow, launch a game with verbose logging enabled: https://retropie.org.uk/docs/Runcommand/#launch-with-verbose-logging

Copy the log, post it here either in a code block (between triple backticks on new lines

```
like this)
```

or post it to pastebin.com and share the link here.

The log file will be at /dev/shm/runcommand.log. You can't access this over the network share. If you need help accessing the file, plug in a keyboard and press F4, or connect via SSH (windows has a built-in SSH client. From command prompt, just do ssh pi@retropie.local or ssh pi@<your.pi's.ip.address> and log in with password raspberry if you haven't changed it previously) and copy the file to your roms folder where it will be easier to grab, with:

cp /dev/shm/runcommand.log /home/pi/RetroPie/roms

Now there's a copy of the file in your roms folder, which you can easily access over the network share.

[dankcushions]

@zombiegasm please fill out https://retropie.org.uk/forum/topic/3/read-this-first, including verbose log.

[zombiegasm]

@dankcushions

Pi Model or other hardware: 4
Power Supply used: Stock?
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.7.1
Built From: retropie-buster-4.7.1-rpi4_400
USB Devices connected: Controller, sometimes keyboard and external HD
Controller used: Knockoff 360/PC
Error messages received: cannot created tmp directory, no space left on device (SD card is NOT full)
Verbose log (if relevant):
Guide used: Multiple, most included BIOS files and installing from source. Tried both
File: (File with issue - with FULL path)
Emulator: lr-psx-rearmed, ppsspp
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)
How to replicate the problem: Try to open psx rom or psp rom. The first few will work (in alphabetical order) but the rest will not load (or in the case of PSP will say it’s an invalid ISO)

I tried using the stock lr-psx-rearmed with the PSX2PSP bios (PSXONPSP660.BIN) and still nothing is loading

HALP

[zombiegasm]

Emulators Config: lr-pcsx-rearmed = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx-rearmed/pcsx_rearmed_libretro.so --config /opt/retropie/configs/psx/retroarch.cfg %ROM%"
default = "lr-pcsx-rearmed"

Retroarch Config: # Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

input_remapping_directory = "/opt/retropie/configs/psx/"

#include "/opt/retropie/configs/all/retroarch.cfg"

[mitu]

@zombiegasm said in Ps1 games will not load:

Error messages received: cannot created tmp directory, no space left on device (SD card is NOT full)

That's not good. Your SD card may not be full, but if you have less than 5% of its capacity free, you may not be able to create new files/folders. Linux reserves some space for the system/root user, just for cases like these, when an user may accidentally fill-up the partition.

Post the verbose log from a non-working game. You can toggle verbose logging from the runcommand launch menu - see https://retropie.org.uk/docs/Runcommand/#launch-with-verbose-logging.

[zombiegasm]

Not sure how I can upload the log but i think the problem is that it says Unsupported/invalid CD image, then shows the file path to the rom (click tower.cue)

Could it be that I consolidated all of the BIN files to 1 using CDMage?

[sleve_mcdichael]

@zombiegasm said in Ps1 games will not load:

Not sure how I can upload the log

Upload it to pastebin.com, then post the link here.

but i think the problem is that it says Unsupported/invalid CD image, then shows the file path to the rom (click tower.cue)

Could it be that I consolidated all of the BIN files to 1 using CDMage?

Could be, I'm not familiar with that app. Do you still have access to the original files? Does it work if you use them, instead?

[dankcushions]

@zombiegasm i don't know what you mean by that. you combined multiple CD audio track .bin files into one .bin file? lets see your .cue file contents, filename and path, and the .bin filename(s) and path(s).

[sleve_mcdichael]

@dank-cushions CDMage looks like some sort of disc extraction/manipulation tool. There shouldn't be anything inherently wrong with consolidating the .bins, but maybe it was done incorrectly. That's why we should see if the original files work before we start pointing fingers at the conversion.

But a single .bin or multiples shouldn't matter as long as the .cue is correct; as I understand it, they both represent the same raw binary data stream to recreate the original optical disc. I ended up with one when trying to apply the English patch to Rondo of Blood for the TG-CD, that worked fine (as far as I can tell. I've only played through the first level but it works at least that far.)

Before I knew that chdman would work on .iso/.wav./.cue sets, I thought you had to have .bin/.cue. So, starting with the multiple .bin/.cue set I:

1. Burned the multiple .bin/.cue set to a disc.
2. Re-ripped the resulting disc to .iso/.wav/.cue using TurboRip (the included binchunk tool that was originally meant to do this conversion gave a divide-by-zero error on Win10, and in compatibility modes for Win7 and XP.)
3. Patched the resulting .iso/.wav/.cue set with the included instructions.
4. Burned the patched .iso/.wav/.cue set back to another disc.
5. Ripped that disc to .bin/.cue using ImgBurn.

This gave me a single .bin file. At first I was worried I had messed it up, but I put the .cue through chdman, dropped the resulting .chd in my tg16 (pcengine) folder, fired it up, and was pleasantly surprised when it worked just fine.