@edmaul69 That could well be awesome:) I won't say no yet, but I may well have a go myself (eep) I didn't think I was using a hackfile, but i need to compare my two systems to see if one had been loaded via the Donkey Kong rom I put on there.
Not going to burn any bridges, your offer is genuinely nice:) I'll see what I can tonight. Thank you!

RetroPie 4.3 Raspberry "pi model 3 B" Kodi 17.4" not the plus version. I've already deleted and reinstalled. I'm also surprised by kodi saving my favorites and addons are still intact, weird. Not running anything HD content 480p. Internet speed is fine . PS I think I know why cause of sudo commands, but thats still strange to me.

I just received my new pi and all is working now. Time to start the rebuild and customization. I tried backing my old build on my pc before i started having issues, 64gb card, but it would always fail at 39gb when writing the image to my 2tb hard drive. Even with multiple readers.

I’ve run retropie on a 3Ghz Pentium 4 with 4G of RAM and it all works. You don’t need too much to get it all going.

With modern equipment, I have an AMD A6-9500 with 4G RAM and built in graphics and that is more than enough

I’ve used lubuntu 16.04LTS on really old builds.
There is a lubuntu 18.04 in 32-bit if you want it. Note that 18.04 needs to be set to using Wayland at time of writing because Xorg gives libretro a hard time.

Ultimately, it doesn't matter too much. You can just leave it in the folder structure that your preferred scraper creates, or change it entirely. As long as gamelist.xml points to the correct location, use whatever strikes your fancy.

The exception to this is that runcommand prefers there to be an images folder inside each system if it is going to use individual rom launching pictures. I don't know if there is a way to change that default location.

@ruthless4u For an end user, it's just a matter of fiddling around with the app and figuring out what features and settings get you the gaming experience that you're looking for.

Fire up a game in nestopia and compare it to fceumm. Try a different color pallet. Compare the audio. Change your settings and see how it affects your game. Once you get a hang of things, you can read up on what each feature does and why they exist, like threaded video, audio filters, etc. Why should you use one emulator over the other? Why should you care about performance versus accuracy? And even if something goes wrong, nothing is permanently broken; just start from scratch, look it up online, and figure out what works and what doesn't.

Hi mastblast09,
I'm experiencing the very same problem.
Have you figured out how to solve it?
If yes, please tell me.

Thank you in advance

@dankcushions said in Can´t change emulators - Tried a command and now its weird.:

@lesk said in Can´t change emulators - Tried a command and now its weird.:

@mitu
Don't think I´ve fiddled with any permissions.

but then

On the last post there is a link to another thread with a command that I first tried:

sudo chown -R pi:pi /opt/retropie/configs

that's "fiddling with permissions" :)

anyway, one thing you can try: https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#reset-ownershippermissions-of-homepiretropie-roms

Hahaha, that just shows how much of a noob I am ^^
Thanks, I will try this when I'm back home.

@pyjamarama Advmame has the config files in /opt/retropie/configs/mame-advmame - see https://retropie.org.uk/docs/MAME/ for each version. For Vice - see the corresponding emulator page at https://retropie.org.uk/docs/Commodore-64-VIC-20-PET/.

@edmaul69 I fixed the problem but thank you for your response

I'd probably rewrite it like

#!/usr/bin/env bash ROMDIR=/home/pi/RetroPie/roms/snes MSUROMDIR=/home/pi/RetroPie/roms/msu rom=$1 if [[ $rom == *"act2_msu1.sfc" ]]; then rom="${MSUROMDIR}/Act Raiser 2 MSU v1 Kurrono, Conn 2018-03-25/act2_msu1.sfc" fi if [[ $rom =~ *"actraiser_msu1.sfc" ]]; then rom="${MSUROMDIR}/Actraiser - Abyss Rebirth OST, MSU v1 Darkshock/actraiser_msu1.sfc" fi # and all other roms... /opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ snes "$rom"

Figured it out, there was a custom runcommand script that was being ran during launch of each emulator. Once that was disabled, it fixed the problem entirely.

Yup, I’ve just reinstalled previous emulator. Now it doesn’t work. The emu itself is up, but games won’t boot.

I also noticed that I’ve been using uae4all this whole time. I was convinced it had been uae4arm. Anyway, all worked in most cases, arm and berry don’t. But now all doesn’t as well.

Please excuse my mistakes. I’m aware they’re silly, but I’m a bit lost.

@mitu OK,, Than I'm in the wrong forum..LOL Sorry

@tuki_cat The only problem was that 33% of times it failed to boot a game. I can’t understand why it’s impossible now to run any game at decent speed. Everything is 2x too slow.

@dankcushions Thanks man

@chubsta If you are having problems, why not try finding those games on on other platforms? I also wanted to play Chuckie Egg, but I grew up playing it on a BBC Micro, and as yet Retropie doesn't support those, however there is an Atari ST version, which presumably would have better graphics than the Speccy one. Reading your post triggered that thought, and I found it today, and am hopefully going to find out how it works sometime this week.

@mediamogul
Thank you! I will give it a try.

@mitu I made it! I have deleted whole scummvm folder, rebooted and the ES finallt works!

Thank you everyone. The problem is officially solved.