Yeah I wouldn't think so either, but it totally works with 6 button in Picodrive

I remember a similar post - after the 4.4 image was released - mentioning that DInput behaves differently and switching to XInput made it work.

Awesome. I will check out that link. Thank you.

Sorry for the delay in replying to this. Just wanted to update this post.

Ok so it looks like the joystick inputs, Start, Select and Buttons A and B cannot be skipped but once I get past those inputs I can skip away and save the config (by getting to the end).

So I just took some spare buttons I have and plugged them into the encoder and then once they were mapped I removed the psychical buttons I don't want leaving only one in my case.

Thanks to Mitu for the help

@saddlepiggy The script provides a generic power button. Just connect your latching button to pin 5 and 6 then you can power down and restart the Pie. The command switch is --generic

Or you can write your own script. I modified the python script for the NesPi+ to demonstrate usage
https://retropie.org.uk/forum/topic/17506

@mitu no

@ooskay I am away from my setup, and I don't even know where a config lives for GPIOnext. You might ask questions about GPIOnext on the github repo. The developer has been very friendly and helpful users in the past.

If you want to go the stripped down route, you can find examples of raw python scripts that setup GPIO pins for input all over the internet. In my opinion, the key to making a script successful is to define OS commands as a function that gets called when the GPIO pin is triggered using EDGE detection method. The script ends in a Pause loop or a while loop so it never terminates.

Then, you just need to launch the scrip at startup. Sorry to be so abstract about it, but it was definitely a learning process and everyone has a different config than you.

I would like to use combo inputs but I am not sure how since doing it in the emulation station menu only allows single buttons

I'm using a Pac-Drive from Ultimarc for my LED buttons. @savetheclocktowr made a controller software for some nice sequencing effects. It's not needed for permanent lighting, the Pac-Drive will do that out-of-the-box in Retropie.

OK. Thank you for your fast response.

@fantomas That depends on the theme used, each theme has it's own convention on where to store the image for the system. What theme are you using ?

Guys, give a try to the lr-scummvm libretro-based core for ScummVM I put for testing here: https://retropie.org.uk/forum/topic/19693/lr-scummvm-request-for-comments-and-testing/

You can do mappings via RetroArch and customise for each game too easily with RA. Also you can use any RA-supported shader. So far it has been working nice for me, would appreciate feedback from other ScummVM players.

@retroprogrammer
sudo apt-get update
not
sudo apt-get install update

I'm sorry about that. Was trying to find the right spot to ask this question. Will check out OpenELEC.

@cwacha this is something that has always been a confusion due to the various hardware types. It had originally been left bottom, left top but that was confusing too depending on people's vantage point. It's most telling on the Xbox controllers where physically the shoulders are flat buttons whereas as the triggers are actually shaped like triggers as opposed to PlayStation controllers where the top buttons don't have any physical distinction other than placement. Shoulders and triggers are also more common in most gaming communities

In short: bottom = shoulders, if there only two like the SNES then they are shoulders. Top = triggers

I included the diagrams so they reflect the controls and verbage in emulationstation and so there can be no ambiguity.

Here is how to set Long press and Short press function. I added on my reset ROM button a long press feature that resets the entire system:

Create a script that will be executed at long press
nano /home/pi/switch.sh

Paste the below code and save using CTRL + X, Y

#!/bin/bash sudo reboot

Make it executable:
chmod +x /home/pi/switch.sh

Edit the code in the first mentioned post resetbutton.py:

nano /home/pi/scripts/resetbutton.py

Replace all text with the below code, save using CTRL + X, Y: #!/usr/bin/python import RPi.GPIO as GPIO import time import os # we will use the pin numbering to match the pins on the Pi, instead of the # GPIO pin outs (makes it easier to keep track of things) GPIO.setmode(GPIO.BOARD) GPIO.setup(16, GPIO.IN) seq_cust = 0 tim_cust = 0 # check to see if button has been pushed try: while True: if GPIO.input(16)==0: tim_cust = 0 if seq_cust > 0: os.system("sudo /home/pi/exit.sh") # Short press action seq_cust = 0 time.sleep(1) else: seq_cust = 0 else: tim_cust = tim_cust + 1 time.sleep(.01) if tim_cust >= 200: # Time for long press >= x os.system("sudo /home/pi/switch.sh") # Long press action tim_cust = 0 time.sleep(1) else: seq_cust = 1 finally: GPIO.cleanup()

I used 0.01 seconds to eliminate delay in button press.
At 200 should result in ~2 seconds.

You can put your own script in switch.sh
Also the script supports more than 2 actions per button with a bit of tweak.

Enjoy ;)

Sorry for reviving an old topic, but installing these drivers https://github.com/atar-axis/xpadneo worked for me. One thing to keep of note is when configuring the controller to make sure it matches what it says here for a Logitech Controller https://retropie.org.uk/docs/Logitech-Controller/#l2r2-top-triggers that L2 and R2 need to be +. After that select, and every other button, worked fine for me.

@olleulv Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@journeyman when binding the 'start' button will be your p1 start, and the select button will be your coin button. i don't know any shootemups that use more than 4 buttons.