@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.

Thank you both.

Your comments lead me to explore the emulator settings more and I found that it was set the keyboard for control. As soon as I set it to controller all the settings mapped correctly.

@mitu

Thank you all for this information, it is most appriciated.

@Limegreengamer9 I don't 'have' any other drivers.

You may try to see if the gamepad works with a more recent Linux kernel, with the drivers included there. Boot with a recent Raspberry Pi OS Lite and try to run jstest there to see if all inputs are properly detected. You may need to install the joystick package for the jstest command.

You still need this? It took me a while but I did build it using the instructions below

(Windows) git clone https://github.com/ppy/osu cd osu dotnet workload install android maui-android dotnet publish -c Debug --runtime linux-arm64 (or Release) (Saved location)\osu\osu.Desktop\bin\Release\net6.0 Copy over linux-arm64 folder to the pi (Raspberry Pi) sudo apt install 7zip sudo apt install libsdl2-dev https://www.un4seen.com/download.php?bass24-linux go into \bass24-linux.zip\libs\aarch64 and copy the libbass.so to /usr/lib https://www.un4seen.com/download.php?z/0/bass_fx24-linux go into bass_fx24-linux.zip\libs\aarch64 and copy the libbass_fx.so to /usr/lib https://www.un4seen.com/download.php?bassmix24-linux go into bassmix24-linux.zip\libs\aarch64 and copy the libbassmix.so to /usr/lib /home/pi git clone --recursive https://github.com/veldrid/veldrid-spirv/ cd ext ./sync-shaderc.sh mv src shaderc cd .. ./build-native.sh -release linux-x64 cd build/Release/linux-x64 mv libveldrid-spirv.so liblibveldrid-spirv sudo cp liblibveldrid-spirv /lib/aarch64-linux-gnu /home/pi mkdir libs cd libs wget https://chromium.googlesource.com/android_tools/+archive/20ee6d20/ndk/platforms/android-21/arch-arm64/usr/lib.tar.gz 7z x lib.tar.gz 7z x lib.tar sudo cp libandroid.so /lib/aarch64-linux-gnu sudo cp libdl.so /lib/aarch64-linux-gnu/ sudo cp liblog.so /lib/aarch64-linux-gnu/ sudo apt-get install libstb-dev add kernel=kernel8.img to /boot/firmware/config.txt sudo reboot cd (wherever you have osu) chmod +x osu\! LIBGL_ALWAYS_SOFTWARE=true ./osu\! stop the game from loading after the fonts load (ctrl + c) nano ~/.local/share/osu-development/framework.ini change "WindowedSize" to 640x480 chnage "FrameSync" to Unlimited change "WindowMode" to Windowed save the file LIBGL_ALWAYS_SOFTWARE=true ./osu\! osu should load in at 640x480 windowed

ceb13383-7674-4078-bb0b-b40ace6a4b48-image.png

theres a couple of things with your provided information.

#1 there isnt an official release of the RetroPie software for the Raspberry Pi 5

#2 more importantly, the Pi5 can emulate (barely) original Xbox games and not very well.

the Raspberry Pi 5 will never, and I mean NEVER play Xbox 360 games, so using your kinect for 360 games in not a possibility. the kinect might work in some other way with other emulators and motion games, but i dont know and doubt it, because no one is working on any software to make the 360 kinect sensor work. also a very important note: the Xbox 360 used special GPU instructions called AVX and not only will ARM processors never work with this, but many Intel chips wont use it either.

I dont say never very often, because there are some amazing programmers out there that make magic happen sometimes, but this isnt one of them.
Xbox 360 emulation will never work on a Raspberry Pi 5, sorry :-/

@Folly Thanks, I got everything running now!

I never had issues with snes games with Rpi3 or Rpi4. I always had 60fps with the default settings and resolution 720p. N64 is another story, even with RPi5, emulation have issues with some games.

@Lolonois Thank you!

@windg

yes it work ty.

OK, the crash should be fixed in https://github.com/RetroPie/RetroPie-Setup/pull/3861.

It doesn't matter how many un-configured devices are detected, one is enough to trigger the bug whenever its input is procesed by joy2key (a button needs to be pressed to trigger the bug).

@Lumbeechief081 did you ever get this file? i'm hoping for something near the start of crystal cavern (or close enough)