@beahrdog Please don't revive year long posts, open a new topic instead. The Nespi cases are notorious for power problems, even if your power source is ok. If you have problems with the PI in the case, but the problems don't occur with the PI outside the case, then you know where the issue is.

@mitu worked great! Speakers are installed and volume sounds great! Thanks!

@dankcushions What I did now was putting all my arcade ROMS into the arcade ROM folder, instead of spreading them over the 2 different folders/emus I mentioned before.
Then, for those games requiring Mame4All I set that emulator for the individual ROM via the configurator (press any key on game start-up).
For the others I chose lr-mame2003 via the default emulator value.
Now all my arcade games are running fine out of one and the same (arcade) folder and most important, now for all games I have a (one and the same) configuration UI (press Tab) - perfect.

@administrators tried to edit this title's post and mark as solved, got this popup error in the editor:

"Post content was flagged as spam by Akismet.com"

Please mark this post as [SOLVED]

@Amplifuzz

You don't really need a ton of custom video modes, since the resolution stays the same, and you only have seven or so different refresh rates at maximum to deal with. Two config lines like "lcd_native_res=1920x1080" and "lcd_range=50-60" or whatever the monitor supports would cover it.

on groovymame, sure, but raspberry pi only understands discreet videomodes. you have to tell it when you want to use a new videomode. in retropie, using the runcommand, you would have to add each videomode to the list, and when selected they would have to call the api command i linked above (since these aren't videomodes in the raspberry pi's limited list of videomodes)

I'm afraid that the whole 'snap to the closest available refresh rate once the native ROM refresh is detected' part is best handled by the emulator itself, as well.

agreed, but for that to happen someone woudl have to update CRT switchres (or something similar) in retroarch such that it can communicate with the pi's custom videocore API calls (see the link above).

i'm told that you can get crt switch res to work with pi, but only under X. we don't use X in retropie. there's some info on this on the (huge) crt switch res thread over at libretro: https://forums.libretro.com/t/retroarch-native-crt-support

@trumad i think at this point it would be a good idea to just start a new thread (filling out the info requested in the sticky), and just put a reference link to this [dead] thread.

going into a bit more detail on your setup, what you're tried, etc. can also be helpful when troubleshooting something like this.

best of luck.

I was able to trick Skyscraper into recognizing there are subdirectories in my \RETROPIE\roms\mame-libretro folder by including at least one ROM file in the base emulator ROM folder.

Maybe this will work with your issue.

@Chewie said in No Scrapers Are Working:

I have no clue what this means

It means the ROM file has not been registered in the scraper's site so the site doesn't know which game it belongs to.

@dreaded_walrus Please use a meaningful title when opening a topic.

Thre is not root password in the RetroPie image for the PI. The pi user has sudo privileges, so no password is needed if you prefix your commands with sudo.
What is the command/action you're trying to acomplish ? Move a file, edit a file, run a comand, etc. ?

@MarkHighPeak Can you add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first ?

@markwkidd @mitu I have just made it a habit to update my Retropie system and packages from time to time. Of course, an update may break something, but I think the benefits outweigh the risks by far in general.

Deleting retroarch.cfg and renaming the other one didn't help. I reinstalled RetroPie with the same image. Installed plugin https://github.com/meleu/RetroPie-joystick-selection. In it I've set detect by name and set Logitech to player1 and Redragon to player2. It worked for player1 in lr-pcsx-rearmed. Not for player2. It is a problem with Redragon gamepad I think.

In plugin I've deleted 2nd gamepad and Logitech now works in all my cores and all my games and in RetroArch menu.

But when I've tried games the very first time, I had only one gamepad (Logitech) and keyboard plugged. And they didn't work in games.

I think it's the problem in RetroArch, that it decides on its own what controller to use for player. And you can't configure it easily.

That plugin is a good solution with detect by name option, it sets the corresponding device for the corresponding player as you want it, not as RetroArch wants it.

But to be sure I need to test it with normal gamepad for player2, not Redragon one.

@mitu thank you so much

@vsilvalopes I know the Dualshock4 new driver (well, it's the same driver for both DS3 and DS4) also adds a device for the touchpad present on the controller (which appears as a mouse), but I don't remember the DS3 controllers having the same touchpads.
Can you pair one DS3 controller, then run the following 2 commands

lsusb cat /proc/bus/input/devices

and post the output ?
Have you installed the customhidsonly driver from the RetroPie-Setup drivers section before pairing the controllers ?

Solved:
The reason was because somehow "Warp Mode" under Speed settings got activated.
After disabling it, the sound came back.

The problem was caused by the HD (where the roms are) being faulty, it keeps disconnecting. Bought a new disk.

@leosagashi Have you tried using the new experimental module for the Sony controllers, from the topic @psyke83 mentioned ?