Run-ahead crash on boot with PSX

RetroArch General
#1

It seems like everytime I update RetroArch I can’t load any playstation games on any core Then I begin troubleshooting, as I apparently forget what the problem was, a fresh retroarch.cfg solves the problem but I don’t really wanna spend the time and set everything up from scratch.

Finally (again) I figured that run-ahead dosen’t play well with playstation games, and after disabling and restarting it loads fine. In the menu now it says run-ahead isn’t compatible

Shouldn’t retroarch automatically disable run-ahead when it clearly knows they don’t play well together?

Didn’t know where exactly to post nevertheless, thanks

#2

Depending on how old your core info files are, they should disable runahead automatically for both Beetle-psx-hw and Swanstation, though they both allow rewind to be enabled.

This functionality was added 6 months ago or so(?)

#3

Yep, Beetle-PSX has “deterministic” savestates in info, and HW has “serialized”. If I enable runahead in config, non-HW allows it, and HW disables it gracefully and logs

[WARN] [Run-Ahead]: Run-Ahead unavailable because this core lacks deterministic save state support.
1 Like
#4

I usually update everything including core info files when installing retroarch. With retroarch I just dump the new zip on top of the old folder Should I delete some old info files, don’t really know anything about in particular about info files and their functionality

#5

Dunno. I would go to your core info directory and open mednafen_psx_hw and look under ‘libretro features’ and see if the ‘savestate_features’ says “serialized” as it should.

#6

It says savestate_features = “deterministic” even though I’ve updated the files today

Guessing it should be safe to just delete the whole info folder, right?

#7

But duckstation has serialized and that core crashed on boot too

#8

It seems it was the “use second instance” for run-ahead that was the culprit So that’s good to know

But the problem with retroarch not automatically turning off such a feature (even with a fresh info folder) persists

#9

Weird. It still disables it gracefully here with second instance, and it even was designed for that in mind…

1 Like