@abj it was pretty bad before turning off 4k. Now it's at least playable.

Please post the contents of the .cue file - you can open it as text, since it's just text. Did you also checked the BIOS files that @abj mentioned - are they present in the BIOS folder ?

@sleve_mcdichael I like the idea, for what I'm doing I think I want to kill any previously running processes vs letting them continue. Only the newest process will be the relevant process

I might make the script kill any previous processes
then wait
then either be killed by a newer process or update the marquee

I'll give this a try tonight and see how it works. I just home emulationstation doesn't hang waiting for sleep to finish.

process=$(pgrep -f $(basename $0)) for i in $process do if i!=$$ then sudo kill $i fi done sleep .5 ...do stuff

A standard keyboard is ok

Quasi88 (standalone or Libretro core) should be able to emulate it. Probably MAME also.

I've taken a look at this and it seems the issue is the Bluez updates due to CVE-2023-45866 (as I said initially).
This will likely affect any (old) gamepad which doesn't encrypt the comunication with the host. The workaround is suggested in the linked Ubuntu bug report:

Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
Run sudo systemctl restart bluetooth or reboot

Possibly other gamepads affected - the Wii U Pro Controller (haven't tested it yet).

NB: this issue is not restricted to Raspberry Pi, it affects any platform where Bluez was patched for CVE-2023-45866.

@Robinson You don't need a bios for 2600, see : https://retropie.org.uk/docs/Atari-2600/

Apologies for bumping an old topic, but partial support for this has been added into Retroarch 1.17:-

https://www.libretro.com/index.php/retroarch-1-17-new-netplay-features/

This will only work with a handful of games that supported the GBA Wireless Adapter, so for example no Mario Kart Super Circuit.

However, apparently it works well with Mario Golf and Pokemon Emerald/Fire Red/Leaf Green (https://www.davidgf.net/2024/01/13/gba-wireless-adapter/)

@notthesame I can't believe that worked, you are a godsend. I'd also like to add a few details:

After pressing Start and Y, the LEDs start to rotate from left to right. After that, you hold pair for 2 seconds, the LEDs go off for a second, and then they start to rotate again.

At this point you need to go through the Bluetooth pairing process again (and if your controller is already paired, you should un-pair it before you re-pair it) but you do NOT need to set up the udev rule. All you need to do is reboot and configure the input like normal.

I think this should be added to the documentation.

@mitu Well ... looks like you are right. :D

Edit:
Fixed! ;)

@mitu I'm .. sure I'm not using it or setting it up appropriately.

I'm not using the runcommand.sh file that is for launching game in retropie. i'm sort of bypassing that, because I couldnt figure out the process or syntax

first, when you are just on the command line area (No Desktop) to initiate xinit, you must use sudo, but that doenst mean that retropie itself doesnt take care of that in some ... manner.

anyway, heres my commands.

the game's .sh file reads:

xinit /usr/local/bin/wine /home/pi/.wine/drive_c/game_path/game.exe

Next: es_systems.cfg file reads:

<command>sudo %ROM%</command>

thats it and it works.
I tried for hours to get the normal:
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS pc</command> to work, but it wouldn't load, but also requires a config file.

so in the /opt/retropie/configs/pc
i created emulators.cfg file, but what do i put in there?
pc = wine ?
default = pc
and if so, what do I change the game.sh file to? it already has the wine command in it.

my main reason for creating this thread, was to figure out the syntax for 3 files.
/home/pi/RetroPie/rom/pc/game.sh
/etc/emulationstation/es_system.cfg
/opt/retropie/configs/pc/emulators.cfg

I've been working with the retropie software since 2015 when i got my first raspberry pi 2, but I've never tried this type of launch and its not easy to find the details about this type of functionality.

thanks for listening. :)

@mitu
I just reinstalled alsamixer and now everything is working. still no idea what caused this issue. made a backup image of my sd card now. thx for ur replies bud, learned a little more about alsa✌🏽

@mitu Thank you for the information. I am sorry for posting in the wrong area.

@luiz_angeloni said in Retopie update deleted the roms:

I have a retrorange retropi 4.4.2 ...

That's not an official RetroPie port - it's a fork that is not supported by RetroPie, but by the authors of that fork.

You should ask for help in the retrorangepi forums (or other support channels they might have), since we don't know how this fork (based on a quite old RetroPie version) is configured or works.

@retepam There is a section about choosing the correct arcade core for your needs in the libretro documentation, you should read it, mame4all/mame2000 is basically the worst choice you can make here.

I'm not aware of any issues with 22.04. There may have been, at the time it was launched, 2 years ago, but there shouldn't be today. Again, 18.04 is not supported upstream and support for it from various emulators is dwindling.

@windg Hi again.

I took your advice and uninstalled RetroPie completely, then reinstalled everything again.

Everything works as intended, and now I can also play N64 games (mupen64plus-next wouldn't load previously).

Thanks for helping.

@barbudreadmon OK think I've solved it. Mame2003plus does show the correct colours so I've used that rather than FBNeo, then I can access the MAME menu from the Tab and set the 2-Player Start. Thanks for your help

@Ashpool

So that's the reason why many use the 0.139 (2010) with Retropoie? At least that's my feeling. I also have a full RomSet of 0.139, but it bothers me that there are so many duplicate entries in the game list in Retropie and also games that cannot be played due to a lack of controllers. But I haven't found a halfway good way to sort the roms, at least not without investing a lot of time into learning how to do it. But from what I hear now, it sounds like I should ignore it because the newer romsets aren't as well supported and I can be happy with the 0.139 where all games run at good speed.