So sorry that I was not able to reply to you sooner, I can see that you've got another solution to do that.
The solution through two cycles is not the best in my opinion, but it works. I am not sure if this is universal solution (I doubt), but I made a clean RetroPie install a week ago, paste all three scripts in config folder and it works without any problem. Anyway, If somebody is still interresting what I did, I tweaked those three scripts little bit to look like this:
runcommand-onstart.sh:
I also use xdotool in RetroPie to move mouse pointer to the right bottom corner. For bigger resolution screens those numbers should be higher I suppose. If you are using xdotool, too or want to use it, simply install it and unmark that line, if not, leave it as it is (I also use it at boot in my start script when splash is playing, so my pointer is still at bottom, but for some people it is not necessary). The file is completely identical as the old one without xdotool line.
#!/bin/bash
#if ps2 was selected, then start gamepad_wrapper script to catch buttons combo to kill PCSX2 process
if [[ $1 = 'ps2' ]]; then
#xdotool mousemove 2000 2000
/usr/bin/python3 /opt/retropie/configs/all/gamepad_wrapper.py &
fi
gamepad_wrapper.py:
I had to tweak this file little bit to match my controllers and purpose. Anyway I had few problems that I had to solve:
-first of them was that only one of my controllers worked with this script (when gamepad object is created), now the button combo (SELECT+START) works with first controller connected, so it is little bit more universal for my purpose. This is because of cmd_output object I created.
-second problem was button code variables. I did not know what my codes for SELECT and START are, so I simply started ./gamepad_wrapper.py from terminal and pressed buttons, so I could see what numbers it prints (to do so, unmark print(event0.code) and if you want also print(event1.code))
-third problem was that if I use SELECT btn in my game and then START btn I quit the emulator. That's exactly what I want, but I do not want to do it everytime. Script waits for user button inputs at start and if correct button is pressed, it continues to next loop where it is waiting for second combo btn, if a wrong button was pressed, the combination is canceled and script waits for the first button again. As I said, it is not ideal, but it works. You can simply edit combo if you want for example to add third btn, etc. but I like it as it is.
I use 8bitdo SF30 pro controllers, so my wrapper looks like this:
#!/usr/bin/env python3
#imports necessary parts
from evdev import InputDevice, categorize, ecodes
import psutil
from subprocess import Popen
#creates object 'gamepad' to store the data
import os
cmd_output = os.popen('cat /proc/bus/input/devices | grep Handlers=event | grep js')
gamepad = InputDevice("/dev/input/"+cmd_output.read()[12:19])
#button code variables (change to suit your device)
button0 = 314
button1 = 315
#process to look for to kill when BOTH keys were pressed
procName = '/usr/games/PCSX2'
#!/usr/bin/env python3
#imports necessary parts
from evdev import InputDevice, categorize, ecodes
import psutil
from subprocess import Popen
#creates object 'gamepad' to store the data
import os
cmd_output = os.popen('cat /proc/bus/input/devices | grep Handlers=event | grep js')
gamepad = InputDevice("/dev/input/"+cmd_output.read()[12:19])
#button code variables (change to suit your device)
button0 = 314
button1 = 315
#process to look for to kill when BOTH keys were pressed
procName = '/usr/games/PCSX2'
#loop through pressed buttons in event0
for event0 in gamepad.read_loop():
if event0.type == ecodes.EV_KEY:
if event0.value == 1:
#print(event0.code);
#Button 1 pressed
if event0.code == button0:
#loop through pressed buttons in event1
for event1 in gamepad.read_loop():
if event1.type == ecodes.EV_KEY:
if event1.value == 1:
#print(event1.code);
#Button 2 pressed
if event1.code == button1:
for process in psutil.process_iter():
if procName in process.cmdline():
process.terminate()
exit()
break;
#Button 2 not pressed
break;
Last script runcommand-onend.sh is identical:
#!/bin/bash
#if ps2 was selected and buttons combo was pressed cleanup the Python wrapper process
if [[ $1 = 'ps2' ]]; then
PROCS=$(ps aux | grep gamepad_wrapper.py | awk '{ print $2 }')
for PROC in ${PROCS[@]}
do
kill "$PROC"
done
fi
I hope my explanation is sufficient.
