Probably SDL2 doesn't support the controller correctly. But for EmulationStation that shouldn't be an issue - the buttons you have should be enough to navigate and operate EmulationStation.

@rilight I was actually looking for that thread before posting this, I could not find it for some reason. I am disappointed that this is happening. I will also look for the screen tearing. I will probably hold off on swapping my Pi3B+ out of my arcade cabinet for this Pi4 until things are smoothed out.

I am using Carbon with no modifications to any settings, fresh image installed from this website.

@mitu Thanks, I check those areas as I can't remember.

I couldn't find any contact info for them.
I am very sorry, I was just looking for any help.

My pleasure. See the AM Wiki for example filters.

If you go this path in the end, maybe you could share your steps to a working AM/Retropie setup in a little How-To? 🙂

Sory for bumping old topic but i've encountered the same problem. For people that may have the same problem in the future i think starting script is bust.

To repair it i've created a new script: /home/pi/.scummvm/start.sh
with content:

#!/bin/bash game="$1" while read id; do echo "$id" done < "/home/pi/RetroPie/roms/scummvm/$game.svm" /opt/retropie/emulators/scummvm/bin/scummvm --fullscreen --joystick=0 --extrapath="/opt/retropie/emulators/scummvm/extra/" --path="/home/pi/RetroPie/roms/scummvm/$game/" $id

and changed content of /opt/retropie/configs/scummvm/emulators.cfg
to:

scummvm = "bash /home/pi/RetroPie/roms/scummvm/+Start\ ScummVM.sh %BASENAME%" scummvm-game = "bash /home/pi/.scummvm/start.sh %BASENAME%" default = "scummvm-game"

.svm files cannot have "newline" character at the end of game name.

Hope this will help people in the future.

Unfortunately, yes, it is

@quicksilver, Thank you for your reply

@skrilmps said in can't access MAME 2003+ (libretro) in-game menu:

cy

no problems at all always use then menu to set options code can change any time.

@Bluebotlabs If it's not in the documentation, then it's not supported.

@barbudreadmon thanks.

@mitu I've only been tinkering with it so far, but this doesn't seem to be the case. When I create such a file, I still have to drill down through the subfolders to play the game, despite the xml file pointing directly at the rom. I do believe i had that option checked, but maybe I'm misremembering. I will test this again.

[update] I just checked. I do have that option enabled. I am still have to drill down through subfolders. I also know it's working because other games are now missing though the files are present in the directory (but not in the xml). I'm assuming this is an intentional functionality (gameslist doesn't flatten directories).

If editing files around is not something you're familiar, then my suggestion is to find a system with a bit more performance and has the righ GPU. Even if you'd manage to get EmulationStation working, other programs/emulators might have similar requirements and you'd be struggling to make it work.

@ProjectFirestart said in Demo mode (random starting of games) for ES/Retropie-menu:

Also we should learn how to point script to evade xml files because those are not needed to run and breaks the demo mode, the script is complex and i have no idea how to set an exception for xml files, hope author can help us here!

Check GitHub ...

So I went back and looked it up. It was in the autostart.sh. I deleted a line and it works and I still get to keep my background music. Thanks for your time :).

@ElrasM said in False controller inputs:

But nevertheless any suggestions for my problem?

First, xboxdrv should not be installed unless you really know how to use it. It's not a real device driver, but emulates an Xbox compatible controller. The xpad is usually used for X360/Xbox controllers. If that doesn't work, then it means you're encountering the same issue.

Is there any chance that there is a seperate file for controller input detection in ES?

The configuration for EmulationStation's input is in \\retropie\configs\all\emulationstation\es_input.cfg. You can verify there that your input is mapped correctly and there are no button overlaps.

You can also start EmulationStation with the --debug flag and it will log the inputs pressed.