-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] PSX Scratchpad memory is messed up #420
Comments
Bug: I am on the latest current version of RALibretro + the latest version of RAIntegration. |
There's nothing I can do about that. This is not an RALibretro bug. The fact that the addresses are showing up in the list indicate that the rcheevos changes are in place to look for the additional memory, but until the cores tell us where to find it, we can't populate it. Beetle PSX HW:
PSX-ReARMed:
SwanStation:
Similarly, if the cores don't expose the memory, players won't be able to use them to earn achievements. |
Having trouble understanding the exact implications of this. Can you help word the issue as to exactly what's happening and what needs to be done? Maybe I can put in a request on their Github pages then. |
libretro cores are responsible for exposing memory. All RALibretro is doing is checking if memory exists at offset 0x1F800000 on the ""real"" memory map. The core reports no memory at such an offset, so no memory can be exposed for cheevo purposes. The only emulator that currently exposes scratchpad is (edit: apparently DuckStation and) BizHawk (in its dev builds, builds which you get on its README) (which you can use RAIntegration and dev with, just put |
I opened an issue on the repositories of all three cores, let's hope this gets implemented. |
PCSX-Rearmed now has this, I will post when the other cores follow suit. |
Mostly requesting this for the accessible Scratchpad memory for PSX so that I can polish the Rockman 2 set into a better state. Duckstation already did this some days ago, I can confirm that it works fine there.
The text was updated successfully, but these errors were encountered: