Slowdown after update to 4.2
-
Pi Model or other hardware: Raspberry Pi 3 B
Power Supply used: 2.5a Canakit
RetroPie Version Used: RPI 4.2
Built From: Installed Official RPI 4.1 from official image, updated to 4.2 via source.
USB Devices connected: Xbox360 wireless receiver
Controller used: Xbox 360 wireless
Error messages received: None
Emulator: lr-pcsx-rearmed, othersI'm pretty new to the Retropie scene so bear with me. I started out 3 weeks ago with a fresh install of Retropie 4.1 using the disc image off the official website. Everything was working very well after initial setup. A week or so goes by and 4.2 comes out, neat, time to update! I use the option to install from source through the Retropie options menu and it all goes without a hitch. No hiccups to speak of.
As a result, my lr-pcsx-rearmed emu is now choppy and slow whereas before it was perfect. I enabled FPS and even though a game stays at or above 55fps, there is still a noticeable slow down in both video and audio. Playing Road Rash drops the FPS as low as the mid 40's from time to time and the game becomes unplayable. Other systems like snes don't seem quite as slow but they're not as fast as they once were.
What's going on here and how do I fix this? I'd hate to have to start from scratch and revert back to 4.1 but that's what I'm going to have to do if I can't find a solution for this. FWIW, my setup is not overclocked and the only mod I made to any config files is to enable higher res textures on psx games.
-
@IronAvocado I'm not sure why you updated from source, but try updating from the binary. It'll be fast, and well, since things are already sub-optimal, what's it going to hurt, right?
-
UPDATE
Last night I took a spare SD card, reformatted it completely and installed a fresh copy of 4.1.
I then did two tests:
1.) Ran Road Rash with the fresh 4.1 install, default settings. This played at 100% speed.
2.)Modified the config file to enhance the PSX graphics, otherwise all settings were default, still on 4.1. While playing the same map on Road Rash there was one very minor hiccup during my game play but the game remained playable.
3.)Reinstalled my SD card that had the 4.2 image and fired up the same map yet again on Road Rash. While even sitting at the starting line the game was notably choppy. Audio crackling right from the start. After leaving the starting line the game ran noticeably slow, so much so that playing at all because very frustrating.Conclusion: There's something that went along with the 4.2 update that killed PSX emulation with the lr-pcsx-rearmed emu. Use with caution. I'll be going back to 4.1 until this is sorted out.
-
FWIW, my setup is not overclocked and the only mod I made to any config files is to enable higher res textures on psx games.
assuming you mean the enhanced resolution option, did you enable the speed hack also? without that it will crawl.
-
This post is deleted! -
@dankcushions
No, I can't say that I did, must not have seen that one on the wiki page. But why would I suddenly need the speed hack when running 4.2 while 4.1 runs perfectly 99% of the time without it? -
@IronAvocado said in Slowdown after update to 4.2:
@dankcushions
No, I can't say that I did, must not have seen that one on the wiki page. But why would I suddenly need the speed hack when running 4.2 while 4.1 runs perfectly 99% of the time without it?you would have enabled it on your 4.1 install. there's no way a pi3 handles it without the speed hack.. it just doesn't have the power.
-
I'll have to fire up the pi to see for sure. Literally the only thing I did to the pie after installing 4.1 was to add the controller, Road Rash, the bios and manually modify these lines:
pcsx_rearmed_neon_enhancement_enable = "enabled"
pcsx_rearmed_neon_enhancement_no_main = "enabled"Nothing else was changed, maybe it was installed by default?
Thank you for the help btw.
-
@IronAvocado the latter setting is the speed hack.
-
@dankcushions
Huh, did not know that, thanks. I just confirmed that both versions of my install 4.1 and 4.2 have bothpcsx_rearmed_neon_enhancement_enable = "enabled"
pcsx_rearmed_neon_enhancement_no_main = "enabled"Yet only 4.2 is experiencing slow down.
-
Being a newbie, I didn't know any better until after the install from source was underway. :(
-
@IronAvocado No worries there. On my x86 instance everything has to install from source and it takes around two hours to update everything. On my Pi 3 it only takes a few minutes.
-
To be blatant, everything after 4.1.5 (or there about) has been much slower. I notice this the most because I'm mainly messing around with Pi Zero's where every little change in the programming is noticed 4 times as much (since it's ~25% of the Pi 3's power). I've also noticed this, albeit to a much less degree, on how smooth things play on my Pi 3's as well.
There's several topics which mention this from different people if you want to look around - I'm sadly one who always complains (and then am told I'm the only one and if it happened to more people - since the RetroPie image has been downloaded over 500,000 times - that more people would be complaining....OR that it's an upstream problem that has nothing to do with RetroPie)....so I don't know what to tell you besides to stay with 4.1 for the foreseeable future.
-
@IronAvocado 4.1 (afair) had a bug that the dynamic recompilation was disabled by default. It was fixed with a a binary update. It's worth testing with the core settings on 4.2 switching this setting on / off. I don't see any other upstream changes that should affect performance but I will test.
-
@Dochartaigh said in Slowdown after update to 4.2:
To be blatant, everything after 4.1.5 (or there about) has been much slower. I notice this the most because I'm mainly messing around with Pi Zero's where every little change in the programming is noticed 4 times as much (since it's ~25% of the Pi 3's power). I've also noticed this, albeit to a much less degree, on how smooth things play on my Pi 3's as well.
No it hasn't. Everything has not been slower. There may be some issues on some emulators, but not everything (and I need real test cases, not generalisations).
There's several topics which mention this from different people if you want to look around - I'm sadly one who always complains (and then am told I'm the only one and if it happened to more people - since the RetroPie image has been downloaded over 500,000 times - that more people would be complaining....OR that it's an upstream problem that has nothing to do with RetroPie)....so I don't know what to tell you besides to stay with 4.1 for the foreseeable future.
I'm getting a little tired of you repeating this -when there are reproducible performance issues they are looked into. You were the only one reporting slowdowns with that particular emulator (fceumm as I remember), and I was unable to see any significant/noticable performance decrease when I did some testing. The quicknes emulator is a better fit for the zero anyway. There was some alignment code changed in fceumm, but I tested with and without it, and it seemed the same.
Other issues that multiple people have reported have been fixed. CoolCV which was due to an SDL2 bug. a previous lr-pcsx-rearmed performance issue due to an error in an upstream commit (which I fixed).
-
@BuZz
BuZz, you know I appreciate what you and your team do, right? - and how I've said that numerous times before because I mean it. Take that as the truth please. And that's why I'm still on here posting (hopefully helpful) things when I can.My only complaint is how I follow the scientific method with repeatability to the extreme (you've read the type of tests I do on multiple hardware, multiple computers, multiple setups all the way around) - and can reproduce every single one of my problems on like 6+ systems (which I've literally done), yet still get told it can't be reproduced...then read about other peoples same issues on the like 10 different forums I'm on...
But anyway, I'm giving up on this pursuit, ok? You have my word. Not another word has to be said about it– as I still want to be welcomed on this forum and not be shunned and not get help when I need it. Fair enough?
/end rant/end thread crapping
-
It doesn't come across as though you appreciate it.
Regarding performance issues - You tested on multiple machines, but you left out plenty of configuration details, and I was unable to reproduce - perhaps you can provide me with two minimal images illustrating the problem (on another thread - of course, don't include any roms).
I've certainly not seen many people on here reporting the same issue as you, and often issues are totally urelated- I need to be able to reproduce an issue to fix it (or report it upstream).
-
@IronAvocado Please can you provide me the output of this command typed into a terminal over ssh
grep "^pcsx_rearmed" /opt/retropie/configs/all/retroarch-core-options.cfg -
pi@retropie:~ $ grep "^pcsx_rearmed" /opt/retropie/configs/all/retroarch-core-op tions.cfg pcsx_rearmed_frameskip = "0" pcsx_rearmed_region = "Auto" pcsx_rearmed_pad1type = "default" pcsx_rearmed_pad2type = "default" pcsx_rearmed_pad3type = "default" pcsx_rearmed_pad4type = "default" pcsx_rearmed_pad5type = "default" pcsx_rearmed_pad6type = "default" pcsx_rearmed_pad7type = "default" pcsx_rearmed_pad8type = "default" pcsx_rearmed_multitap1 = "auto" pcsx_rearmed_multitap2 = "auto" pcsx_rearmed_drc = "enabled" pcsx_rearmed_neon_interlace_enable = "disabled" pcsx_rearmed_neon_enhancement_enable = "enabled" pcsx_rearmed_neon_enhancement_no_main = "enabled" pcsx_rearmed_duping_enable = "enabled" pcsx_rearmed_spu_reverb = "enabled" pcsx_rearmed_spu_interpolation = "simple" pcsx_rearmed_pe2_fix = "disabled" pcsx_rearmed_inuyasha_fix = "disabled" pcsx_rearmed_show_bios_bootlogo = "disabled"This is what I get when I SSH in.
-
@IronAvocado please can you post your
/opt/retropie/configs/all/retroarch.cfgand/opt/retropie/configs/psx/retroarch.cfg(use a code block - http://commonmark.org/help/ - or external pastebin site)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.