@chmaruni in case anybody else has this problem: I upgraded everything, including upgrading the distro from Jessie to Stretch, then upgraded all the retropie modules, and then (and that was important) I deleted the sdl-vicerc config file. After that, sound and joysticks are working again. Deleting the config without the distro upgrade didn't work for me. Anyhow, seems to be working again.

I actually got it working! I don't know how, but I switched from basic to detailed to video and all of a sudden it started working. Thx again for the help

@AJ2425 said in Some buttons not responding during PS controller configuration:

Correct me if I’m wrong, but I believe this points to it being a controller issue.

Well, if the controller works with your PS2, then it's an adapter issue - you might want to get that checked - or try it also on a PC.

@mitu It works just fine within EmulationStation, but once I start RetroArch everything freezes until I connect the USB controller.

you are right that I pointed out the scrapers not being as easy to use as I'd like. But I also communicated that I am really looking forward to see the inbuilt scraper work again, because it makes manual scraping much easier than editing XML files by hand for many exclusive roms that are in no database.

@Nerumu

https://retropie.org.uk/forum/topic/3/read-this-first - how can anyone help you if you do not provide the information requested? and that you agreed to when you signed up.

i ended up working around this by using a different version of mame (lr 2000 instead of lr 2010). So this might mean it was a MAME config, like i messed with the inputs in the MAME menu? I know i tried to go through those folders and nuke the default.cfg files, but perhaps there was another spot, or its just something else. Also magically i got the XMB menu after a reboot, so its a lot easier to see which user an input setting belongs to, phew!

Instead of writing "mods delete if not allowed", how about reading the sticky topics you agreed to read when registering BEFORE posting.

You can ignore that. As far as I know, it is only a reference from the scraper where it got the data from.

Thanks that worked?!

So the controller is/was connected to the internal GPIO port of the Pi? Any chance that some of the wires have been detached while travelling?

If that is not the case, please provide the information that is asked for in https://retropie.org.uk/forum/topic/3/read-this-first

did you find anything? I have the same problem.

@mitu said in Questions about controller buttons, logins, and Steven Scraper:

but when we're talking about custom tags,

Thanks for the quick response. I'll try the autostart and login.

I don't have any custom tags...I just want to make sure that the redone videos aren't overwritten by the original videos. I'm not too worried about the favorite/playcount/etc stuff right now. I just want to get this all up and running. I ordered a replacement SANWA JLF-TP-8YT-SK joystick to swap into my controller. The stock stick is not very accurate, but I got it super-cheap and couldn't pass it up.

ive hit this as well and was confused. i see auto stuff and explicit buttons, so its confusing. I checked the input bindings and saw some map to auto and some map to explicit buttons, so i'm assuming this means it depends on the input settings--this mostly works but ive found a few situations where it isn't working, so im not sure.

@wmarcio Actually, the issue was caused by a similar thing! Instead, it was the usb that I had connected into the pi. All my freezing and stuttering has finally stopped. Thank you for the help!

@che_don_john Skyscraper can use TheGamesDB since it doesn't rely on the legacy API. I don't know if SScraper has that.
I don't think there are any issues - in Skyscraper at least - with Screenscraper.fr or OpenVGDB.
If you have specific examples - ROM names and checksums - where the entries are in the scraping site, but not found by Skyscraper, then please report them also in the Skyscraper topic.

I was having the same problem so I started a segaCD games in verbose mode and noticed that it was looking for the BIOS in the segaCD roms folder instead of the BIOS folder. This was on a new machine I was setting up on Ubuntu 18.04. Not sure what has changed that made it look to ROMS instead of BIOS folder.