Take a look in the config directory to truly verify if it is saving or not. It likely is, but it is pulling up a different config when you start the emulator.

wait, sorry i needed to restart retropie, it seems to be up now. thank you

Okay, installed everything from a fresh RetroPie 4.1 image and also clean install of AM from source. I'm on version 2.2.0 of AM and everything is working as expected. The ghosted keys are no longer an issue, and as a result I don't need to futz with different key settings for exiting a game in retroarch. I'd like to figure out why that was an issue for me, but for now what I have is working. In windows I programmed the "exit" buttons for my minipacs with the WinIPac program to be macros of "start+select" and it works perfectly.

As a side note, it seems the issue was with sfml-pi. This explains why my 2.2.0 AM was still giving me issues. I had not gone back all the way in the steps to the sfml-pi portion.

Thanks all.

@BuZz Thanks!

...

The default source (thegamesdb) had great coverage of boxart so that was the default. If you want to do something else you can use something like -console_img="s,b" to use a screen shot if it exists then fall back to box art, etc.

Or you can do as @columboscoat mentioned and you have access to a windows machine you can try UXS. It uses ScreenScraper which is available in my script (-use_gdb=false -use_ss) but it also has some other neat image options.

thanks a lot mate :)

@mike27277 said in Scraper Issues:

trying to mark as solved cant find the button

The options are located at the bottom right of your first post in a pull-down menu labeled 'Topic Tools'.

@legendofthestorm yeah, fs errors are rarely good. Not sure how your corruption happened but never pull the plug on a working Pi. Glad you got it sorted.

@cqb30 so why are you asking for support here? Go ask Lady Ada...

@protoman

I just edited /opt/retropie/configs/all/retroarch-joypads/Xbox360WirelessReceiver(XBOX).cfg and changed:

input_enable_hotkey_btn = 10 #Guide

If that doesn't work then make sure to put " (quotes) around the number 10 or if you already have the quotes then remove them.

@hankchad You aren't alone. I am trying to figure out that same thing. I went to Retroarch and found where it mentioned the esc key. I bound a arcade button to that same command which is Exit Retroarch. Of course, that didn't work. It will close Retroarch but will not exit from a game.

I sat down and played a couple PSX games today. CTR seemed to go okay, along with a short Gran Turismo stint. After about half a race in Colin McRae 2.0 though the Pi3 froze. So it looks like I am running hot with the enhanced resolution enabled.

Turned on my old PSU fan setup and everything was at 50 or under and no more freezing. I guess I wasn't testing PSX for long enough before when I thought it wasn't getting too hot.

@montanafury No worries. I'm no expert. Just trying to help. It can be a steep learning curve... but worth it.

@Mhykael said in Hello RetroPie World!:

New question, How do you change which emulator is the default emulator for each system? I saw on the N64 page that sometimes changing the emulator to a different one for different games can help with some problems. Also, that sounds like something that knowing would be useful for other game systems as well.

https://github.com/retropie/retropie-setup/wiki/runcommand

thank you. that file did the trick.

i wasn't using an old version of retropie though. in fact it was a fresh install of 4.1. i even updated all installed packages via the retropie setup.

maybe they changed it back?

anyway thanks again!

Well if anyone is interested, I figured out what was wrong.

Somehow, something caused a file to be created in the configs/all folder called "videoresolutions.cfg" (or something to that effect, I forget the exact name) and it was telling Mame2003 to force a resolution of 320x240. I deleted the file and everything is fine again.

@cashnewman the bios zip goes in the ROM folder. Stick it in BIOS too if it makes you feel better.

I found a solution in case anyone else has this problem in the future:

I did cat /proc/bus/input/devices to list input devices, which does not give the full ID. But I saw a "Wireless Controller" listed there, so I knew that was my bluetooth controller. I saw it had an H: Handlers set as event0 and I recalled being ale to substitute this for the full ID. So, instead of doing --evdev /dev/input/by-id/*** where the ID is still unknown at this time, I was able to do --evdev /dev/input/event0 instead.

Now whether or not the button mappings I did are accurate is a whole different problem. Time to go test it out.