Runs fine on mine, I am running Retropie v3.0 Beta on the pi 2 fully overclocked, pi2 setting.

as with all the libretro versions of emulators, you’ll find that they’re branches of the main emulator developments. I doubt that the libretro hooks add in much overhead, but the chances are high that because it doesn’t include the most current version of emulator, it runs worse as a result.

that said, for this emulator I get almost perfect emulation with the libretro version (some very small hiccups in tekken 3). what’s happening for you? what games? perhaps your overclock is too aggressive.

hmm, there are a few options that will reduce performance. perhaps one of these is mistakenly set in retropie 3.0 final? because i’m running an updated 3.0 beta 3 with retroarch 1.2.2 with lr-pcscx-rearmed r22 and my performance is fine.

here’s a few things that might sort it

hotkey (usually select) + triangle/Y to get to the RGUI

quick menu > core options
frameskip should be 0
dynamic recompilier should be enabled
interlacing should be disabled
enhanced resolution should be disabled
enhanced resolution should be disabled

quick menu > shader options
shader passes should be 0 (you can get away with some shaders with minimal performance impact, so if you know what you’re doing, go ahead!)

settings > video
HW Bilinear Filtering should be OFF (this turns off smoothing of the screen – has a performance impact)

settings > driver
input = udev
joypad = udev
video = gl
audio = alsathread
audio resampler = sinc

if any of this works, post it here so we can get the relevant scripts updated :)

Just gave it a go on vanilla RetroPie 3, all seems good, no choppy audio on WipeOut.

Do you have a 5v 2a power supply – that can cause issues sometimes if its less than that.

Also, if you load the game, go into RGUI and select save new config, it will create a “libretro.cfg” in your /opt/retropie/configs/psx/ directory.
If you post that as an attachment or on pastebin I can compare it to the one I have to make sure it is the same.

good news!

floob, i said i think video_threaded should be true – my understanding that it puts the video process to a seperate thread, which is good for multicore systems like the pi2.

i was curious so i just checked and i have it set in fba/mame and psx already. i don’t believe i ever changed it, so i’m thinking it must have changed in 3.0 final.

https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/emulators/retroarch.sh
iniSet “video_threaded” “false”

you can see that jools set it to false in this change: https://github.com/RetroPie/RetroPie-Setup/commit/f86c4b233efe1660ef5d9f0408d9f455607c4f32

reasons are given – i’m not sure i’ve had any out of sync stuff (only in mupen64plus, which isn’t libretro anyway), but i can’t also be sure that it boosts performance noticably. it’s difficult to test given that none of the frame rate counters seem to work in libretro!

my guess is that the rewind_enable setting killed their performance more than anything else – I think that basically buffers the last few moments of gameplay (by memory dumps?) so you can reverse. I imagine it kills the poor pi(2)

I noticed the rewind_enable = “false” is actually configured as such in the general retroarch.cfg (RetroPie 3.0 final) so configuring it specific for PSX or N64 is obsolete right ?

doesn’t that conflict with the OP’s situation, though? there’s was set to enable rewind in the psx config (perhaps by accident but even so), and by reverting it they corrected the issue. so the individual core configs override the /all/retroarch.cfg?

if that’s the case I’m not entirely sure of the purpose of the all/ one!

video_threaded is set to false in all/retroarch.cfg (as of 3.0 final), so you could override that if my assumptions about overrides are correct. I’ve got an older version so it’s set to true. all my emulators work fine as far as I can tell.