Use the default retroarch.cfg - leave aside all the hard sync settings (I don't think they're relevant for the Pi's GPU) and the audio settings. Also, a GPU mem of 256 is more than enough for most emulators, so I don't see any point in upping it to 512.

Try gpsp's non-retroarch version. With this version, you'll probably have less lag on GBA games, since it consumes less resources than the default retroarch version. I've tested this version on a Raspberry Pi 1 B+, and I remember playing some GBA games without lag. It was on 2015, and back then, if my memory serves, there was no lr-gpsp yet. I don't know if it'll work on your Pi Zero, but assuming Pi Zero and Pi 1 has approximately the same hardware, there's the chance that it can work.

@washburngopro That might be run-ahead instances. I think the setting is found under "latency". Could set it to zero, I never use it but it is okay with some Nintendo games. The bios is good, you should keep it. Rarely (Arc the Lad Monster Tournament) do I ever have to use no bios. If your pi doesn't have any heatsink, airflow, cooling fan, radiator. It will overheat and the SoC/CPU will throttle undermining performance in some games. While it is possible to underclock and increase the soft/temp limit to get adequate performance for PSX, good ventilation is still needed when playing 4+ hours.

@lesk Deopending on the emulator and version I think, as it is a relative recent feature. You may need to update RetroPie. There are entries in the emulator menu for this feature: SETTINGS > LATENCY. I looked up in Snes9x 1.56.2, Nestopia 1.50-WIP and MAME 2003 (0.78). The Raspberry Pi 3 is too weak and it would be extremly slow and painful (as far as I know). Which emulator and version do you want use this for? Try the "lr-" versions.

Thanks, I'll try it!

@KnightZ87 Have a look at this article about hdparm! There are many settings you can tweak! Tune Your Hard Disk with hdparm: http://www.linux-magazine.com/Online/Features/Tune-Your-Hard-Disk-with-hdparm You could also set the sleep/standby timer to a longer time! Change hard drive's sleep/standby mode timer to reduce power consumption: https://linuxconfig.org/change-hard-drive-s-sleep-standby-mode-timer-to-reduce-power-consumption Spin Down and Manage Hard Drive Power on Raspberry Pi https://www.htpcguides.com/spin-down-and-manage-hard-drive-power-on-raspberry-pi/

you edit the config.txt file with some of these settings: https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

@IanDaemon i found that when I'm in game and I bring up the retroarch menu, I can't move anything in the UI. The cursor will not move with keyboard or controller. I'm stuck there until I hard reset the pi because I have no input. I thought about a reinstall but I spent a lot of time scraping and setting up and I'd hate to have to do it all again.

@chubsta It's definitely the images causing an issue, especially if you have a lot of games. All of my Pi Zeros have this issue and I no longer use the videos. If you try another theme or change the UI theme settings to BASIC (I believe) you should see it become very responsive. The Zero is a minimalist board when it comes to resources but it functions extremely well for all of the systems I run on it.

@sebretro said in Periodic stuttering/freezing with RetroPi4.4 on a Raspberry 3B+ in every game (1-2seconds): Does anyone have know about this problem? Thank you for your help. Looks like an insufficient power problem - the RPI underclocks itself not having enough power. Take the PI out of the case and do some testing to see if you get the same problems. The NesPI cases are notorious for this kind of problems.

@thelostsoul The supported tweaks also yield the best results by far. Setting a television to game mode alone feels like the difference between night and day. Setting even all of the possible unsupported tweaks feels more like the difference between night and a bit later that night.

Whoever could solve the problem with sound on SNES emulator PI3B, PI3B+ The solutions described "https://retropie.org.uk/docs/Sound-Issues/" do not work. Very disappointed in Raspberry. Sound sometimes slows down and collapses. a few days later .... after reading a lot of unnecessary information The problem was in throttling. avoid_warnings=2 means don't show the warning squares and don't disable turbo mode on under-voltage condition. We still throttle on over-temperature.

@jackknife18846 From what I hear, the Pi Zero W has trouble running NES games without certain optimizations. I hate to say, but I doubt you're going to get N64 running well at all.

Well, in Tekken 3 with Enable interlacing mode(s) enabled there are pretty obvious combing issues, but I'm not experiencing any slowdown at all. With interlacing mode off I can't see any obvious quality difference, and it seems to run perfectly, even with enhanced resolution enabled.

@tonytoon I forgot to mention that the displays I have found are typically VGA, but many of them also have DVI ports. I found a cheap HDMI-to-DVI adapter which is the way to go. DVI cables are bulky, so this little adapter basically upgrades the display to HDMI. Also, I un-shell them and discard the plastic bezel. This sometimes requires me to relocate adjustment buttons which has not been a problem. You end up with a screw-mountable steel bracket reinforced screen with the driver board/power intact, just not all of the branded plastic.

@mitu said in All ROMs running in slow-mo: Sounds like a slow video driver problem. Are you using the default driver (amdgpu) or the AMD (fglrx) driver ? I've tried to install the AMD driver but it gives me the following error: One or more tools required for installation cannot be found on the system. Install the required tools before installing the fglrx driver. Optionially, run the installer with --force option to install without the tools. Forcing install will disable AMD hardware acceleration and may make your system unstable. Not recommended. See /usr/shar/ati/fglrx-install.log for more details. Here's the log: Check if system has the tools required for installation. fglrx installation requires that the system have kernel headers. /lib/modules/4.13.0-32-generic/build/include/linux/version.h cannot be found on this system. One or more tools required for installation cannot be found on the system. Install the required tools before installing the fglrx driver. Optionally, run the installer with --force option to install without the tools. Forcing install will disable AMD hardware acceleration and may make your system unstable. Not recommended.

Just to update, I opted to instead go with Sanwa sticks as they are the perfect size with the same screw holes and apparently the top of the line based on the recommendation of those in the know. https://www.amazon.com/gp/product/B01CRQMWEQ