You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Save State selected RA freezes/crashes. Tried several games, all same result. Note: all games tested are playing fine, just can't save. Assests from git are in place in RA/system/ppsspp.
What should happen?
Save State correctly
What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.
Not sure if related, but assets from git contain ppge_atlas.zim which has an md5 of (f46570c34bcf6a01cf20b93add725c3b) which does NOT match what the RA reports in core info (a93fc411c1ce7d001a2a812643c70085) as the correct md5.
The text was updated successfully, but these errors were encountered:
Same is happening to me on the Shield. It wasn't happening back in February though. Was that a different version? Can we revert to that version somehow?
There was a change made in #11990 which was supposed to make this work better on libretro. It's a hack though.
As I recall the problem is that libretro assumes all emulators will be single core, but PPSSPP is multicore. PPSSPP needs to create a save state when everyone has put their pencils down, or crashes may occur. libretro's assumption probably makes sense for NES and Gameboy emulators, but doesn't really work for a PSP emulator.
What happens?
When Save State selected RA freezes/crashes. Tried several games, all same result. Note: all games tested are playing fine, just can't save. Assests from git are in place in RA/system/ppsspp.
What should happen?
Save State correctly
What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.
Samsung Note 8+
Android 9
lr-ppsspp (PPSSPP 07a5adc)
Not sure if related, but assets from git contain ppge_atlas.zim which has an md5 of (f46570c34bcf6a01cf20b93add725c3b) which does NOT match what the RA reports in core info (a93fc411c1ce7d001a2a812643c70085) as the correct md5.
The text was updated successfully, but these errors were encountered: