From what is advertised the kit should work.
If the "Zero-Delay" encoders (can not judge if they are genuine or clones) put you off (e.g. being not so zero-delay) you can also run your setup with two MCP23017 (GPIO extender) and via GPIO.

If I would build your setup I would provide the left/right flipper a dedicated pin.
With the kit, as well as with MCP23017 you have 16 switches. Usually 4 are needed for the stick axes, and 9 for the most common push button functions: A, B, X, Y, TL, TR, Select, Start, Hotkey. So you have in any case three spare switches.

The third could be "Tilt" triggered by a gyroscopic sensor. (sometimes Space-key on keyboard based pinball games)

Mapping of the buttons can be done on a per game basis for many emulators -out-of-the-box- (retroarch-based and amiberry). And for any other emulator this can be done via runcommand-onstart.sh / runcommand-end.sh [1] in combination for example with xboxdrv.

Sorry, a lot to digest for a new joiner. But no worries, I assume you will master it by time.

TL;DR: Two separate pins/inputs for the flippers.

Happy making.

[1] https://retropie.org.uk/docs/Runcommand/#runcommand-scripts

@mitu since I copied the script contents into a working script file after clearing the previous contents, I have no non working scripts now. I have to recreate this issue to even be able to upload a script. I'll work on it this week and upload it the scripts.

@mitu Yep, that was it. If I leave the ES audio settings at "Default / HDMI", when I change the Audio in RetroArch to "Headphone", then I can get audio from the 3.5mm port.

Very counter-intuitive, but at least it is working now. Thanks for the assist!

@edillenback said in Skyscraper / Steven Selph's Scraper working on some builds and not others???:

@drdave79 Just wish I had better news for you. I'm still having issues with both command line scrapers on anything but my existing build. The built-in GUI scraper does work and isn't bad after I took @mitu 's advice of unchecking the 'user decides on conflict' but that won't help you with videos.

Has to be something about the build process on my end but I'm doing pure vanilla installs and still have no idea what it could be.

Have you tried Skyscraper?

Yes, I've tried both. Same result.

@barbudreadmon
Thanks for the info ;)

@retropieuser555
At last I have located this menu and I have managed to make the appropriate changes so that the mouse recognizes me.

If it were not for your help, I would not have achieved it. Thanks ;)

@90sgamer Please provide all of the information that's asked for in https://retropie.org.uk/forum/topic/3/read-this-first.

Works for me

@derekr resizing to 512x512 seems to have fixed a lot of the issues. Another one that I came across was that the ".PNG" extension of a couple of my files was capitalized. Make sure that your files use the lowercase ".png" extension.

@weissnix4711 said in HDMI CEC Remote support, seems there but not working:

Hey, sorry for bumping this old thread, but could I get an update on this?

There hasn't been any new code added for CEC support.

@mitu Gotcha. Thanks so much.

@retropieuser555 Hopefully you see this, but I was able to fix it by going into /home/pi/.config/AM2R/config.ini and changing:

[Screen] Fullscreen="1.000000"

to

Fullscreen="0.000000"`

@mitu I feel so dumb I am so sorry to bother you. It worked turns out it was wring problem like you said.

Thank you for everything though

I'm a bit confused. If you're using the Pi4 image provided on retropie.org.uk/download, there's no additional installation to be done - RetroPie is already installed and the system should boot to EmulationStation.

How are you installing RetroPie ? Is a Raspberry Pi OS image from raspberrypi.org working on the device ?

@punx45 , I'm about to go almost the same way myself, wiring up buttons from my genuine arcade machine. I'm planning to use the grounding instead of the plus feed (Raspberry's GPIO's should trigger fine on three state i.e. either open circuit going high to feed voltage OR going low to GND).

However, my thought was also a prevention from involentary multi triggering but not by H/W support, we do have plenty of computer power at hand; have a look at this article Physical computing with Raspberry Pi. Some simple sleep timers should do it.

@mitu They don't work at all. :(

I ran through the install instructions posted on the main page twice to be sure. Fresh RetroPie install on a 32GB card, updated everything RetroPie then right to the shutdown scripts. No go. So I did it again with a fresh install with no updates. Still no go. I also used Putty so I could copy and paste the commands with no chance of incorrectly typing them in.

The former dev said he hasn't touched them in over 16 months.

EDIT for added info

@redmarsbluemoon Cheers dude will keep trying thanks and I know the feeling of not having enough time...

@alegasalv Is the gpu_mem actually using the 512mb though? I found that enabling the 'hdmi_enable_4kp60' overrides the setting, as running 'free' in the terminal was showing less than 512 being used. It's only meant to boost the stock gpu memory by 50mb's...or so I've read.

I have mine set at:

force_turbo=1
over_voltage=8
arm_freq=2147
gpu_freq=750
gpu_mem=512

Needed to force_turbo in order to go above gpu_freq=550 though, tested by running 'vcgencmd measure_clock core' to confirm. Also, 'vcgencmd measure_clock arm' for the cpu.

edit: Forgot to mention...if raising the gpu_mem, then using the raspi-config gui to modify anything, it will automatically hash out the hdmi_enable_4kp60 on you...or at least it does for me. I guess it's anything over a certain value.

edit2: Sorry...also forgot to mention that in order to use the gpu_mem=512, you need to enable cma=512 as well. The kernel crashes on me otherwise.

dtoverlay=vc4-fkms-v3d,cma=512