@BuZz Thanks

@daubsi Yes. The .rp-dist files are created when an emulator is installed or updated and the default config has been changed (as it won't overwrite your custom config).

@mitu thanks for the reply. I turned off my shader preset to see what would happen, and it does improve performance to "mostly" 60fps. The global shader I use is just "sharp-bilinear-2x-prescale" which afaik isn't supposed to be demanding at all, so I'm surprised performance tanks so badly with it on.

Unfortunately I've screwed up the video settings for all the snes cores by attempting to remove the global shader preset from bsnes, while keeping it in place for snes9x. Shaders don't work at all for snes anymore, and different resolutions in the runcommand menu aren't even working... I don't know why that happened.

Bsnes is causing me too much trouble, so i'm just gonna uninstall it once I restore my backup...

It didnt work it just booted up like usual.

I got retropie image from the raspi imager presets should I go to the image from that website?

No, it's the same image - it doesn't matter how it's installed.

Unfortunately I don't know much about the various 3.5' models for Waveshare's displays - the above config was taken from one of their images, but it looks like there's more than 1 model with this resolution (and supported with different drivers).

I suggest looking at their Wiki page and try one of their images to see which one works (and then replicating the config.txt from the image onto the RetroPie installation) or trying their install script from https://github.com/waveshare/LCD-show/.

I decided to change the title to make it more relevant. I wasn't sure where to post the following yet as I was keen to share it in case this helps others.

We ran into a very painful issue while testing a recent build of DOSBox Staging. The sound was crackling like hell in almost every games tested and only pi4 platform was affected (pi3 was ok). Builds for macOS, x86, etc didn't have the issue either. After a long and rather difficult debugging session the culprit has been found (thanks to @kcgen!) > SpeexDSP's floating-point API is unreliable on current (32-bit) Buster. After compiling our own version everything went back to normal.

@dookieshooter said in compiling mame on ubuntu 22.04 fails:

So I hacked around and THINK I got the mame 245 binary installed properly. I basically hacked up the mame.sh script in retropie setup to skip the compile step and only take the precompiled stuff from stickfreaks.

Ok, It probably can work if you did it correct.

This is how I do it when mame has been already configured earlier :
Extract the .7z in /opt/retropie/emulators/mame .

This is how I do it when mame has NOT been configured earlier :
Extract the .7z in /opt/retropie/emulators/mame .

Commands for installing the dependencies and configuring :

cd RetroPie-Setup/ sudo ./retropie_packages.sh mame depends sudo ./retropie_packages.sh mame configure

@Yaszuthemage said in HELP! Emulation station broke on rpi display!:

@mitu how would I use either the fkms or kms overlay? how would I load Gpu drivers? I tried using the built in spi panel overlays but it didnt work

The default RetroPie (or Raspberry Pi OS) images have the fkms /kms overlay already enabled, so you don't need to add anything for this part. What you need is to add the configuration for your display to config.txt, which can be different depending on your display model and capabilities.

@sleve_mcdichael ok, I was just making sure there wasn't somewhere obvious I was missing on handing fr HDMI to headphones. Or if there was a general location where this would typically be saved, such as in a config file somewhere. It may be easier for me to just install another separately from the beginning

@mitu thank you but it seems complicated for me....

@Folly said in Only Cartridge Files Loading on Amstrad CPC6128+ (MESS/MAME):

~/RetroPie-Setup/ext/RetroPie-Share/scriptmodules/supplementary

@Folly

I did not find a second version in ~/RetroPie-Setup/ext/RetroPie-Share/scriptmodules/supplementary, but I deleted any other versions of the file on my system - in the trash folder, download folder, etc...and that did the trick.

I will try the ParaDOS options again later and report back.

The ParaDOS options are visible and they do load ParaDOS.

@mitu @Refazeshot1 yes, works, thanks.

@stevethefish76 what you're describing there doesn't sound like a crash to me, but without the full error message and all the other stuff in https://retropie.org.uk/forum/topic/3/read-this-first i can't really diagnose.

but if it works now i'm not sure there's much utility in doing any of that :)

@gamester
In the Retropie setup script

Manage packages > Manage core packages > emulationstation > Configurations/Options > Swap A/B Buttons in ES

I have one and it's working fine with the latest RetroPie version.
What's the issue exactly ?

@uplime said in Dolphin Emulator on Raspberry Pi 4 Model B ARMv7:

Thanks! Just to clarify, I can install a 64bit on my Raspberry Pi 4 Model B instead of having to buy a new one with a 64bit chip?

Yes, the Pi4 B is already 64bit capable. That being said, don't expect dolphin to be full speed - even with a modest video resolution - on a Pi4.

Yes, why not ? You can set EmulationStation to autostart when the desktop is started from the configuration - https://retropie.org.uk/docs/Debian/#configure-retropie.

@zantetusken10 I think the problem is joycond. I uninstalled it (manually deleting the files it installed + disabling the service) and now it works. The only quirk are the leds of the controller. For example, if I connect it with bluetooth the first time the first light will be on, if I disconnect and reconnect via bluetooth, the first + second light will be on like if it were player 2, but the controller will work fine nonetheless.

Now, to get it to pair properly with Steamlink :D

@dankcushions got the both to work used different files and now work cheers

@mitu Removing the overclock didn't help unfortunately. Here's the rest of the info to the best of my ability

Pi Model or other hardware: Pi 4B
Power Supply used: CanaKit 3.5A Raspberry Pi 4 Power Supply (USB-C)
RetroPie Version Used: 4.8
Built From: Pre made SD image from raspberry pi imager v1.6.2
USB Devices connected: None
Controller used: 8bitdo Pro 2 (connected with bluetooth
Error messages received: N/A
Verbose log (if relevant): N/A
Guide used: N/A
File: N/A
Emulator: N/A
Attachment of config files: https://pastebin.com/BKrPS3Z5
How to replicate the problem: Connect RPi4 to CRT, test output using 2nd color bleed check in 240p test suite Mega Drive ROM (press A once on color bleed check).

If someone could replicate the test on their own device I would really appreciate that. I have a feeling it might be like this on all Pis and has just gone unnoticed by most people.