Scraped again and changed it to use the rom directory for images and gamelist. Now they most of the images and Metadata are there. Just an update for anybody else who has this issue.

@lookin4fun79 you should fill out your own thread in the help section. Be sure to include the information requested here: https://retropie.org.uk/forum/topic/3/read-this-first

@cyclair I have never created a theme, but it seems to me that this page describes how to setup sections for metadata. Have you tried removing the sections for both the labels and the data (ie: md_lbl_rating, md_rating sections)? I think you have to make backups and try this. It will be trial and error, especially to get your positions correct since you also said you wanted to raise the text. There are no simple answers here. You will need to get in there and make adjustments.

Also, I tried clicking your pastebin link and it looks like the XML is in a different language than your long post. Did you know you can go back and EDIT your long post? Folks might be more inclined to respond if you clean up that first post a bit.

I had a similar issue while building my 4.4 set up with my new Pi 3B+. For me it seemed to be just a timeout due to the website not providing the image fast enough for the scraper. When I tried it again after each failure it would work but would happen frequently. I recently tried again several days later as I had 100+ roms and didn't feel like sitting through them all and it worked fine without a hiccup. I'd still provide that info requested by mitu as that may not be your issue

Hey @momaw27
Have you tried overclocking your GPU ?
The reason why I'm asking is because I experienced the same issue.... but after 5+ hours of screensaver.
I tried a bunch of stuff... Regenerating and removing most of my gamelists, building Retropie from master, updating just about everything on my Pi, trying various settings in ES....
And then I noticed a video glitch in the ES interface when a video preview started, then all the interface froze except for the preview.
I changed my GPU overclock from 550 to 525 Mhz.... and no more freeze.
I hope it helps
Toitoinou

@mitu Yes, it is definitely connecting. As the Pi boots, the light blink, but then when it connects, it vibrates and goes solid.

Just keep the hardware you have, and create an image on a clean SD as @mitu suggests, and you will have a proper retropie system, which will as you point out, will probably be more fun and reliable. Make sure your power supply is good enough though. Lots of people have issues with poor or under-powered ones. If you start getting a lightening flash on screen, you definitely have a power supply issue.

@mitu Ok I guess I'm going to reset the pi. How will I go about doing that

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