Joy2key causing controller issues

BiZzAr721

I do not have a runcommand-onstart.sh or runcommand-onend.sh file in /opt/retropie/configs/all/
Should I? I haven't checked the image I was doing our experimenting of OpenBOR with to compare.
Here is the contents of runcommand.cfg if that is helpful:

use_art = "0"
disable_joystick = "0"
governor = ""
disable_menu = "0"
image_delay = "2"

cyperghost

@bizzar721 Some call with the es_systems.cfg in ports section? Does this accour on a fresh install, too?

BiZzAr721

@cyperghost I don't see anything different in es_systems.cfg between the working and messed up images. I've been trying to find out more about joy2key in retropie but info seems to be very vague. I was hoping to see how, where, and when joy2key is used.

mitu

@bizzar721 You can look directly at the source for runcommand.sh to see how it's used - https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/runcommand.sh.

BiZzAr721

@mitu Thanks, this helped give some more insight. Still a little blurry, but much easier to read than runcommand.sh file on my pi

I changed permissions, renamed joy2key.pyc & joy2key.py and restarted system. Of course problem went away, but then I'd lose controls on runcommand menus. I renamed then back to normal, then ran OpenBor. It worked fine. I did this a couple of times and still worked. Then back at ES, I switched controller USB port. The problem came back. After exiting OpenBor using the Left on D-pad, I entered runcommand. Up & down, Left & Right functioned properly, but select button (B) moved selection down as well, and another button (Y) moved up. Left Trigger was now select.
(Actual keyboard Enter worked normal)

cyperghost

@bizzar721 I've a solution but it's really a dirty hack and a workaround!

You edit runcommand-onstart.sh
Be aware the last & is mandotary!

[[ "$1" == "openbor" ]] && /path/to/script/delaykill_joy2key.sh OpenBOR &

No you create script delaykill_joy2key.sh and make it executable with chmod +x delaykill_joy2key.sh

#!/bin/bash

while true; do
    if [[ -n $(pgrep -f $1) ]]; then
       pkill -f joy2key.py
       break
    else
       sleep 1
    fi
done

BiZzAr721

Thank you for writing up those commands for me. I will give them a go so I can get some BOR play in while family is out - In the meantime, I am going to backup my OpenBor testing image (in case I need to grab some working files for more troubleshooting), then restore an earlier backup over it - and I hope I can remember all the minor tweaks I've done such as renaming roms, and switching out video snaps then re-introduce OpenBOR. Ultimately, I can get back to a working image(hopefully the issue doesn't re-appear, but now I'll be tracking my steps), but I still will be trying to figure out what's going on with this issue. (To help others who may have a similar problem, possibly squash a bug)

Thinking about it now, when I was setting everything up and remapping controllers, there was a point I had the wireless xbox 360 receiver plugged in along with the SNES clone (and I always have the wireless bluetooth receiver plugged in)
USB PORTS:
[======EMPTY======] [==xbox360=]
[=Wireless Keyboard=] [==SNES===]

Controllers were always switched while in ES menu

Is there a way to "reset usb"? I can't imagine controller config would cause this , but maybe I'll install Eazy Hax to run his Factory Reset Controller to see if it does anything.

BiZzAr721

I just had the joy2key issue reappear. I had the backup image I restored to a sandisk 128gb (119gb after format) working fine. I wanted to get it back onto the original PNY 128gb (117gb) SD card, so I created a backup using win32img, then ran pishrink. I restored the image that was working when I created the image to the PNY SD, and upon boot, immediately went to ports and tried OpenBOR.

A couple of nights ago I installed PS3 BT driver, but that was done AFTER I already had an image made, so those changes were not on the image backed up. However, I did still have a SNES clone plugged into a different USB port upon boot.

I don't know if this is the cause, but I will try to burn the image again, this time booting with the controller in the regular usb port I've been using.

Maybe some people can try running ps - a to see f they have joy2key running without even knowing it. It seems the only system/port effected by the exit left bug seems to be openbor. Others there is no noticeable difference with joy2key running at the same time.

cyperghost

@bizzar721

Others there is no noticeable difference with joy2key running at the same time.

Well yes there can be an issue. If you start ports again it may happen a second instance of joy2key is running. So you have suddenly leaps if you want to select something in dialog.

BiZzAr721

So, I have just restored my backup again (the exact same backup I just used that had issues on start). This time I plugged the controller into the usual port. Started up no problem! So I'm certain that had something to do with it. After some messing around , copying back the SNES default controller configs, I went to access run command but pushed the button a tad bit late and BAM! Joy2key issue was back!

I was able to recover this time. The ONLY way I was able to was to be in ES menu - open terminal and type ps -a
Find the entry for joy2key and then kill 1234 (1234 being process ID #)

I randomly does it if I happen to tap A or B at the wrong time, but does NOT do it no matter how much I tap the L & R shoulder buttons. I assume they are not mapped with joy2key.

cyperghost

@bizzar721 I just used SNES clone controller, but joy2key is terminated after runcommand call (as it should).... strange strange...

Did you try the little hacky script? This seems the only "quick" solution I discovered so far :(

Btw: pgrep joy2key.py will directly show PID
pkill joy2key.py will directly terminate process ;)

ps -ais good for diagnosis ;)

BiZzAr721

@cyperghost Thanks for the explanation of pkill. I have not gotten to try the joy2key disable script yet. Even though it may be a bit hackey, at least it's not taking up any resources.

From what I read, this particular Joy2key is only used for runcommand and even if I wished to use Joy2key inside an emulator (which I don't), I would want a different Joy2key.

I still have not been able to find in runcommand how exactly Joy2key is called to shut down. I can't image what is stopping it from terminating (or possibly starting back up)

EDIT
I went through various systems and used ps - a and Joy2key was running in the background of many, such as SNES, & Gameboy running retroarch. With Joy2key not running in ES, booting a gameboy game without hitting any buttons, Joy2key will be running in the background.

For ports (any), hitting A or B anytine during loading screen, not going into runcommand, will cause Joy2key to run in the background.

BiZzAr721

@cyperghost The script did not work. Here is from runcommand log:

/opt/retropie/configs/all/runcommand-onstart.sh: /opt/retropie/configs/all/delaykill_joy2key.sh: /bin/bash^M: bad interpreter: No such file or directory
Parameters: 
Executing: pushd /opt/retropie/ports/openbor; /opt/retropie/ports/openbor/OpenBOR "/home/pi/RetroPie/roms/ports/openbor/Aliens Vs Predator Aftermath (Demo).bor"; popd
/opt/retropie/ports/openbor ~

I looked up the error and it had to do with the file being created on windows, so I then ran a dos2unix utility.
After that, the error was gone, as well as any mention of it in the runcommand log. Unfortunately it does not close joy2key.

EDIT
Going into runcommand settings and changing launch menu to disable removes joy2key from ever being started. All the keypresses during loading screen on any emulators would not invoke joy2key. Of course I lose an important feature of Emulation Station/RetroPie. I'm hoping this will help in pinpointing the issue.
At this point, I would be interested in using a global KillJoy2Key script! This is making my head spin!

cyperghost

@bizzar721 said in Joy2key causing controller issues:

The script did not work. Here is from runcommand log:

It works for sure. You are using wrong formated text file format, Winows is using CR LF as newline, Unix system just using LF. You can avoid this if you are calling the bash script with command bash from runcommand-onstart.sh. It will look like this

[[ "$1" == "openbor" ]] && bash /path/to/script/delaykill_joy2key.sh OpenBOR &

A global joy2key kill script is also considerable. But I don't understand why the python script is still running in background in your case.

I still have not been able to find in runcommand how exactly Joy2key is called to shut down

It's a function call inside runcommand.sh very similar to the one I've used in the BoR-start menu script. But the call used by runcommand is done more professional and I did not have the time to dig deeper what exactly there happens. Simply the script detects joypads and set /dev/input/js# to joy2key. The PID of joy2key is savesdinto a variable. And if runcommand is going to finish the PID will be SIGTERMED, the PID of the python subshell is detected by bash with ?!

BiZzAr721

@cyperghost
I really appreciate your time helping me with this. Thank you.

After using dos2unix utility I didn't get any mention if it did or did not run in the log - but I also did not get the ^M error so I assumed it ran. I just realized I didn't change permissions to 0755 (but I did command to make it executable) so maybe that's why it didn't terminate Joy2key.

I'm really debating if I just wipe the SD card, and start from scratch - restoring games & configs from the backup.
It's just a lot of work getting everything just right, and I don't know what will reintroduce this bug if I start copying all the settings back over.

cyperghost

@bizzar721 I changed the script a bit pkill -f joy2key.py- is working better, because so it will also find python joy2key.pycalls ;) You can try to make a blank install. For first setups it will not take to much time to see if the issue will pop up again.

BiZzAr721

Unfortunately, it did not work. First couple of tries it did not work, so I pkilled joy2key. After that it didn't come for about 25 times. (pressing all kinds of buttons on the controller). Even loading runcommand menu, joy2key was properly closing. Then, pressing A & B repeatedly, joy2key was back.

Running the Unix delaykill_joy2key.sh from terminal sudo ./delaykill_joy2key.sh, I recieved and endless loop of:

pgrep: no matching criteria specified
Try `pgrep --help' for more information.

Running the .sh not converted to unix using sudo bash ./delaykill_joy2key.sh

./delaykill_joy2key.sh: line 2: $'\r': command not found
./delaykill_joy2key.sh: line 10: syntax error near unexpected token `done'
./delaykill_joy2key.sh: line 10: `done'

EDIT
I get it, it won't run from terminal because variables are defined in runcommand-onstart.sh

I thought that maybe your script was closing joy2key after run command, just like it should, and maybe something else was causing it to run again just after. I apologize if those commands were not input correctly in terminal.

Dumping the files from my backup as we speak, hopefully I can get the new SD card up and running sometime tomorrow.

This is going to make me jump out of a plane! (seriously, I'll be going skydiving tomorrow)

cyperghost

@bizzar721 said in Joy2key causing controller issues:

seriously, I'll be going skydiving tomorrow

Make your head clean and use the force!

I get it, it won't run from terminal because variables are defined in runcommand-onstart.sh

Yes runcommand-onstart sets parameter to obtain PID of a binary or script.
I think a general script is easily possible to do.

You set a delay timer of maybe 5 seconds before the while-loop
You search for pgrep -f dialog
IF NOT any dialog PID is found, then try to terminate joy2key

But for now try it just for openBOR, because that makes trouble and the script defintly works in this case. It's not simple to write general solutions without test area.

BiZzAr721

I just tried out the "fresh" image and am still getting joy2key still running in background. I used a fresh retropie image downloaded from Retropie, then added folders back using Samba. I added the roms folder, bios folder and then config folder. I omitted es_settings.cfg, runcommand-launch-dialog.cfg and
runcommand.cfg

I did not touch anything that required SSH, nor did I even install anything from retropie setup. Can anyone check to see if they have joy2key running using retroarch?

Edit
I was digging into runcommand files again and compared /opt/retropie/supplementary/runcommandjoy2key.pyc from the new image with runcommandjoy2key.pyc from my backup and they were not identical.

I replaced the file on the image I backed up (still had it on an SD card). I still got the error to reappear, ~~but I really had to try to get it to happen so far. (only once)~~ . Running Turbo grafx 16 opens joy2key, and once it's open, the only way to close it is to pkill it.

I also wanted to add in that when I renamed runcommandjoy2key.pyc to [OLD]runcommandjoy2key.pyc, but did not replace the file, joy2key was still working in runcommand, still staying open as well.

I

cyperghost

@bizzar721 Thejoy2key.py file should be just a small text file and it wasn't updated the last 5 months. You can see it here on Github

Annother question? What is runcommandjoy2key.pyc? And why it looks so strange encoded in your screenshot? Did you compiled it?

I also wanted to add in that when I renamed runcommandjoy2key.pyc to [OLD]runcommandjoy2key.pyc, but did not replace the file, joy2key was still working in runcommand, still staying open as well.

That's feasible because you seem to edit the wrong file. The script filename is joy2key.py it's located in same directory as runcommand.sh