@rasp_renegade said in Scraper crashes ES:

. I had swapped gamelists and forgot, so disregard the part about old files. Anything else useful in that log?

I don't see any issues in the log.

Do you have an input override for this game ? If you open the RetroArch menu and go to Controls/Port 1, what kind of device type does it say it is ?

Please add some more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@Dandelion I agree with Folly. If you're sticking with Old Skool games, go with the Pi3b+. It's plenty to run those.

For any other lights, lighted buttons, or other stuff that might pull power from a USB on the Pi. Check if you can source power from something else. The Pi performance will degrade the more power you pull from it...even CPU fans.

Take your time designing and researching. It'll pay off

@bbvbandit2 You just download the install 'image' and write it to the sdcard - it's explained in the docs.

@Sisyphus Same problem here. Using a generic SNES controller that works on every single other game except for VVVVVV.

@mitu i will try that and update. Thanks!

@Darksavior Thanks Darksavior. Going to overclock it and try it out for a bit. I appreciate the insight!

@mitu Cool, thanks! That puts my mind at ease.

@StoqnS14 We don't support this configuration and OS. Use either RaspiOS or the RetroPie image from https://retropie.org.uk/download and you'll not have issues.

Just to close the loop on this. I was unable to try the above solution as the controller had paired, but no security settings or configuration was allowed. When I tried to unpair the controller I couldn't. I assume I had messed up the settings trying fixes for this. I uninstalled retropie and reinstalled and it worked fine. Thanks for the help.

Although strange, I have only declared one controller in ES.
By this way, I have no more strange behaviour on some buttons. So it's better now.
Still have the controller 1 or 2 swapping in some emulators...
Try to manage with joystick-selection, but not sure it could handle this 100%, as name and reference are always the same.

@sleve_mcdichael

Hey. Figured it out. The answer was more or less staring me in the face.
In the "es_temporaryinput.cfg" there was a line for the hotkey, which I more or less copied.

<input name="hotkeyenable" type="button" id="8" value="1" /> <input name="x" type="button" id="0" value="1"/>

This is my solution. From what I've tested this hasn't messed up anything else even though it does share the
id="0" with one of the axis entries.

Thanks for the input. You can consider this topic "solved".

Yes, it has the wrong title, thank you for reporting. We'll fix this.

@sleve_mcdichael thanks. I mean maybe it's overkill but if I made a page detailing what systems are included in which themes have would there be much interest in that? Could just run an excel vba macro or something to read the folders.

Although it gets confusing as with the open nature of the themes I've found a version of showcase that retro arena used, they added in a few extra images to the theme to include Atomisware and Naomi. So I just added those images into the stock RetroPie version of showcase.

@mitu I did a small test. well I’m all confused. I swear you couldn’t change resolution in the raspi config anymore. Guess from the time I used the Kms driver from my last build. Well I went there and it allowed me to set a resolution and set the config.txt. Rebooted, but here’s the kicker. The hdmi port I was on, that booted to 1080p, now booted to a black screen acting as a second screen. And when I switched hdmi ports, to the one that ran at 4K 30hz, it was now displaying at 1080p. Still wondering why I was getting 1080p on the other port before. Guess at this point it doesn’t matter.

@llivingst I ran into a similar issue when I updated a year old build on my pi 4. It would get to emulation station, but went to a blank screen when going into a game. It think it was crashing cause I could not exit back to emulation station or my video feed was gone. I know a lot of kernel changes were made, so maybe you have a custom configuration that interferes with the new kernel. But Step one would be to try switching hdmi ports. I remember that being in the wrong port did that before. If not, you might have to reimage a new build. I changed all my custom configs from overclocks to KMS drivers switched back to and still no go.

@kevgal try updating from source the lr-vice package, the bug should be fixed.