lr-pcsx-rearmed won't run any games

mitu

@ivooc Do you have any overrides/configs for the game saved from RetroArch ? Run the game with verbose logging enabled (from the Runcommand launch menu) and paste the log file (/dev/shm/runcommand.log) to pastebin.com.

ivooc

@mitu said in lr-pcsx-rearmed won't run any games:

@ivooc Do you have any overrides/configs for the game saved from RetroArch ? Run the game with verbose logging enabled (from the Runcommand launch menu) and paste the log file (/dev/shm/runcommand.log) to pastebin.com.

I do, but the overrides still confuses me. But this is happening with all PSX games.
https://pastebin.com/TFCu45yi

mitu

@ivooc You have a custom config file for the game

[INFO] Config: appending config "/home/pi/.config/retroarch/config/PCSX-ReARMed/Crash Team Racing (U).cfg"

Try to remove it and see if that makes a difference. The 'Boot BIOS logo' option is automatically saved as core option, so you don't need to save anything, once is set from the RGUI.

ivooc

@mitu No dice, that file was actually blank. https://pastebin.com/wyLpfTv8

mitu

@ivooc Hm, I see this also with another game. The core option is not in effect unless the content is reset - probably cause by this recent commit.

ivooc

@mitu Seems like a new variable SlowBoot was introduced. Maybe it wasn't used correctly?

Efriim

My Gran Turismo 2 stopped working after the update, it gets past the first two SCEA licensing screens and then freezes, I am able to enter the Retroarch menu and exit though. The standalone pcsx-rearmed won't work for me either, I was told it is no longer supported, but the old version used to work, whenever I run it, the graphics and PI crash and it overheats until I unplug it.

hhromic

@ivooc @mitu I realised I was using a slightly outdated commit on my tests as I was debugging the core, and that's why the BIOS was showing for me. I updated to the most recent commit and indeed I don't see the BIOS on boot anymore. I also have a feeling that the recent commit you mention mitu is to blame. I will investigate more and check with the upstream guys.

@Efriim I will check the core in the latest commit to see what's going on with that game and report upstream if necessary. Thanks for bringing it up. Can you clarify which version of GT2 are you using (Arcade/Simulation)?

Efriim

@hhromic GT2 Simulation only.

I tried the new psx clock setting for the only other thing I could think of. For the slowdown in Metal Gear Solid during some boss fights and while in first person looking down the length of the map, it didn't seem to effect anything.
I also noted that this slowdown is exactly the same with a significant under clock as a hardy over clock. It is like too many reads simultaneously, or is it just creating one that is extra wide, I'm not sure. I did think it was interesting when Psycho Mantis actually crashed my emulator, I know, I didn't expect that. I got him the second time though.

hhromic

@Efriim thanks for the info. I will test and check.

@ivooc @mitu I bisected the core now and the BIOS show option stopped working at this commit, which seems to be a bad revert to a previous commit. I will investigate how to fix this and send the fix upstream.

hhromic

@ivooc @mitu a PR has been made upstream by the current maintainer to fix the boot logo display on boot. Once merged it should be working again.

BJRetro

@hhromic for what it’s worth I can confirm that on the lr-pscx-rearmed version where the ps logo option was still available and working Gran Turismo 2 both arcade and simulation have the error that @Efriim mentioned where it boots, goes to logo, goes to SCEA screen and then goes black screen. On the bottom of my screen on the retroarch GUI it says 1.7.6 - PCSX-Rearmed r22 if that helps.

hhromic

@BJRetro yes I confirmed on my end that GT Simulation is not working in recent commits. I'm currently bisecting the code to find in which commit it stopped working to fill an issue report. Will report back once I find it to keep people informed :)

hhromic

@Efriim @BJRetro I found out now that the issue with Gran Turismo is related to the same issue of the boot logo not showing during initial boot (same commit broke it). The PR waiting upstream does fix Gran Turismo booting too (just tested). So just wait for it to be merged and all should be back to normal (GT working and bootlogo showing on boot).

hhromic

Btw, the game currently does work with the "show boot logo" option set to disabled. The PR above will fix the option and the game when set to enabled. However, keep in mind that this option is still considered a hack and there are some games that simply don't work with it enabled. The maintainer upstream said:

PR sent, which fixes original one that still shows bootlogo on reset if option was disabled.
just reminding that some games will not load when using the bootlogo option(must be timing thing). i have at least 2 games here that i know wont boot with it enabled, or causes to game to freeze when issuing reset (i cant remember which ones though)

quicksilver

@hhromic thanks for looking into this. I for one like the authenticity of having the bios/boot logo display when first starting a game.

If anyone runs into any games where the boot logo causes compatibility issues please post them. Perhaps we can make a list of games that need it off so we can make config overrides for those games.

hhromic

Update
The show bootlogo fix is merged now upstream. This should fix @ivooc @Efriim @quicksilver and @BJRetro problems, i.e. not showing logo on boot and also Gran Turismo not booting when this option was enabled.

You can test this simply by building the core from source in the RetroPie package menu.

@BuZz maybe it would be good to re-build the binaries for this core to avoid more reports regarding this problem introduced upstream, specially if you are planning to release a new RP version soon.

BuZz

@hhromic new bins will be available shortly. [Edit] they are available now.

ivooc

@hhromic @mitu Thank you for taking a look at this. I'll update my packages soon!

mitu

@ivooc Just update from binary, it should be enough.
Don't forget about the incompatibilities caused by using this option, if you get any problems running a title, try to run it without it. Remember that you can save options per-game, so if you find any game having problems with the option, use the Save options for ... menu to save a different set of options to be applied to the game.