@massproduce201 you need to install the retroarch cia from their downloads page. You might even have to copy the retroarch directory structure to the root of your sd card. Not really a retropie question though, so I'd direct you to the libretro forums. They'll have the info you need.

Edit: read this
https://gbatemp.net/threads/retroarch-emulation-thread-nightly-builds-included.400913/

@mitu said in Pi overheating and scripts not working:

@MisterMints Most likely something hardware, try to return it and get another.

Wish it was that simple! My Pi3 is over a year old and was a gift - I treated myself to a new 3B+ and was going to donate the broken one (obviously before it was broken!) to a retro gaming present for my little brother.

At least now he gets the same present but with a brand new 3B+ instead

@mitu said in Scraper accuracy?:

@MisterMints This corresponds to 4.4.4 - you should have skyscraper as a module in the experimental packages section. Did you also update the packages ?

I did, but still "no game found"

This happens whether I go via the scraper option from pressing start and doing it on a system by system basis, or edit this games meta data on individual ROMs.

I have go sselph and skyscraper working now so it's no big issue and they both seem to be very accurate so far

@BurningSparkz72 There's no need to take it down. If other people are having the same question - as you did - it would be another way for them to find the answer. It seems that the notice in the forum rules about 3rd party images is not enough since it might not be clear for a newcomer what is a 3rd party image.

@teller You could try to adapt the script_play commands from here: https://retropie.org.uk/forum/topic/19844/advmess-for-dummies-a-basic-guide/61 so that the game(s) start automatically. I haven't tried it for the Jupiter Ace though.

was this ever solved?

@Norstein For the PBP scraping, I think there is already an issue opened (see https://github.com/sselph/scraper/issues/90). You could try using Skyscraper, it can search by name only and I think it works with PBP files.

@Fellowgamer87
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@hushkin Instead of re-flashing you could just reset the controller configuration and start over with it. You can reset them from the emulationstation package in the RetroPie-Setup script. After that, ES should prompt you to re-configure them again. Try starting with the problematic controller and see who it behaves.

For support on the RetroFlag switch, you should ask them on their support/project page.
I'd still recommend the script by @cyperghost, it's easy to use and has really detailed instruction both in the topic started and on the github page.

@barbudreadmon Sounds great. I'll look into it when I'm back - traveling for work this week.

Many thanks, and keep up the great work!

@SpudsMcToole Glad you finally got it working !

Editing the es_systems.cfgjust for one theme seems like a stupid idea IMO, because it will break probably all other themes that require the snes folder.
I just looked at the retrorama github and would suggest to rename the snes folder to snesntsc and the snespal folder to snes. That should work.

hi @pjft , I think I found it. When all items in the retropie system (i.e audio, bluetooth, wifi etc) are set to hidden, this causes the crash as described above. if you have at least 1 item set to not hidden, it then works fine.

Hope this helps.

@barbudreadmon

Thanx for information bro :)

On a second thought, even better would be to actually use runcommand, taking advantage of its goodies such as video mode settings and emulator selection:

# Launch FixItFelixJr /opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ megadrive "/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin"

Runcommand also prepares the console like hiding the cursor and even can display a splash screen art if configured. This is the way EmulationStation launches games and you also get the benefit of error messages being logged to /dev/shm/runcommand.log for debugging.

Done it! I succeeded to enable blargg's filters, thanks so much.

Nevermind i figured it out. The guide dosen't it make it noob clear that after you have built your own version you still have to actually move the binary to the appropriate folder but as i said in the end i figured it out :)

@Silent_Gunner (a.k.a @NoBullShit) - you just registered again just to add more insult to the injury and pretend to provide 'helpful feedback' to your own posts. Looks like you've made your choice.