@mitu said in lr-ppsspp crashes on hotkey reset:

Is there a similar issue reported for PPSSPP ?

I didn't see one, but the repo is pretty active and there's a lot to sift through so it's possible I may have missed something.

The closest one I found was this one, also for the libretro core; I'm not sure if it's the same issue since I didn't test any of those other actions and I'm not sure if Sync Audio is enabled or not -- I can test some more next week.

If i would use Ipac2 in keyboard mode is this better for the Retropie experience?

Not necessarily.

I choosed the gamepad mode for the configuration under Emulationstation for two players . Because in keyboard mode is only one player input configuration is possible (but Keyboard mode functioning under PPSSPP awesome). I know under Retroarch I have a possibility to configure a second player input too.

Yes, you can configure a 2nd player for a keyboard device, but that can't be done from EmulationStation and you'll need to edit the configuration files (retroarch.cfg). RetroArch expects mostly a gamepad since it started as a console oriented front-end emulator.

I don't really understood configuring inputs under Emulationstation , is this for the standalone emulators or just for the controlling / steering the Emulationstation. Retroarch is for the Libretro emulators input configuration ( I hope this is right ?)

Configuring the inputs in EmulationStation will auto-configure them also for RetroArch and a few other standalone emulators (Mupen64Plus/Daphne/OpenMSX). Any libretro based core should have a configuration ready once you've done it in EmulationStation.

This is getting off-topic here, if you have some more input related questions, I suggest starting a separate topic and reference your posts from here.

@mitu they are!!!
Thank you so much, perfect advise - as usual!

got an answer in the dev-forum of ppsspp: this issues is caused by new saving-routines, also the paths have changed/shortend (from /roms/psp/psp/system/ -> /roms/psp/), so you will find saves on the memorystick there since 31.01.2022.
The issue is well known and should be fixed with the next update in a couple of days.
FYI, even if i seem to be the only one here using / updating the lr-ppsspp-core :D

Got it, someone from the official ppsspp-forum had the final hint.
I share this here for everyone running in the same issue (which should happen if you updated recently):

"RE: graphical issues since last update
Turn off the vertex cache setting.

It used to be accidentally disabled in code, but we re-enabled it recently. It seems to be malfunctioning on some devices now, though. It was accidentally broken for several stable versions."

@ffaddic thanks for info.
I am aware that you can force retroarch to get updated even without being supported by the retropie setup-script.
I prefer to wait until retroarch gets verified and 1.9.x (even .13 maybe?) will be part of the official setup-script to avoid running in other issues :)

Thanks for the advise concerning *.cso.
I just had a look, i only have *.iso on the pi while in fact having lots of *.cso on my real CFW-PSP1001 ;)

@mitu Thanks for the reply! I’m not at my Pi at the moment but when I get situated, I’ll give that a shot and report back!

Hello , i have more problems GTA games , Vice City , Burnout dominator and some other i think the most recent PSP games boots fine and menus are ok.
But in the game the graphics are broken and unplayable. Cars and people falling trough the road and grass etc.
Same roms / dvd content are fine on ppsspp win10 desktop machine.

Tried vulkan on the PI4 but more and the same problems, also tried booting retropie standalone image and on twister os same result.

PI4 / 8GB
32 bit or 64bit kernal on twister os same problem.
ppsspp without retropie same problem.
Al on the latest updates of may 2021

Can anyone give some advise.

@stumcbill
The only two things I can think of are

Drive is full File permissions issue

#1 is easy enough to check, #2 shouldn't be an issue as long as your USB drive is using the FAT32 file system.

When you say you manually save, if you mean through the game's normal save feature, you could try using a save state as an alternative. If a save state worked then it likely would mean that none of the above applies and it is something else.

@mitu i'm back if you're still here for some reason...
i tried again for the log.
here it is: https://pastebin.com/U96FjKBt

@dankcushions
Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..) Pi4
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.7.1
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used): Premade SD image
USB Devices connected: none
Controller used: SN30 Pro
Error messages received: N/A
Verbose log (if relevant): https://paste.ubuntu.com/p/BYN4x55wf3/
Emulator: (Name of emulator - if applicable): lr-ppsspp
Attachment of config files:

# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line input_remapping_directory = "/opt/retropie/configs/psp/" #include "/opt/retropie/configs/all/retroarch.cfg"

retroarch.cfg: https://paste.ubuntu.com/p/xbCSQbJvhB/

Using Retropie on a Raspberry Pi

PSP games in .pbp format will work fine in ppsspp and lr-ppsspp

PSX games in .pbp format will work fine using lr-pcsx_rearmed

What do you think about my findings friends?

@windg thanks man, i will check it later...I assume that the issue has to do something with the raspberry pi GPU, cos having the latest source, latest PPSSPP version, overclocked...could it be a GPU malfunction?

@quicksilver
In buffered I get this, but I don't know how to change it in lr-ppsspp, but in ppsspp it gives me a black screen.

@grocket12 The repository used by RasPI OS automatically redirects apt based on your location to the closest Rasbian repository mirror. If that mirror doesn't work for you, you can manually change the URL in /etc/apt/sources.list to one of official Raspbian mirror servers - https://www.raspbian.org/RaspbianMirrors.

@akamming I confirm the same problem and the same error. It seems to be related to some parameter in the config files (maybe retroarch or core options).