runcommand.sh and "Press a button to configure"

[dahz]

Hi All,

I installed Retropie on my unbuntu 14 media server. I can launch emulationstation through Retropie and navigate through the games menu. However, I am still unable to launch any game. The screen changes as if the game was going to be launched however after 2 sec, it returns to the emulationstation menu. Of course, I checked the roms path.

So I tried to isolate the problem and to launch the game from the command line using the runcommand sh script.
Once launched, this script display a "press a button to configure" menu. If I do so, and then from this menu, select the x option (launch game), then the game is launched and runs fine. However, if I do not enter this menu, and simply wait the timeout for the menu (2 sec), then the script returns and no game is launched. So I suspect the same happens when I try launching games from emulation station.

Any idea/advice would be welcome

[CrazySpence]

i had this same issue in steamOS but instead of investigating it I just used something else since steamOS isn't supported

[meleu]

@dahz take a look at /dev/shm/runcommand.log after a failed attempt to load a game. And paste its content here if it have useful info (use ghostbin.com if the file is too long).

This file is overwritten during every runcommand execution, so you have to look it right after the failed attempt to load a game.

You could paste its content after a successful launching too (using the method you described).

[dahz]

Thanks for the advices.
Actually, by debugging the runcommand sh script, I figured out a workaround to this issue:
The function check_menu() returns the variable $dont_launch. If the menu is not entered by pressing a button, then this variable remains unset, which causes the script to end (line 829). So I just added "dont_launch=0" (without quote) to set this variable at the beginning of the function check_menu(). Now the system runs fine.

This is only a workaround, I do not have a complete picture of the retropie system for a proper fix, however, this does the job.

btw, the log file /dev/shm/runcommand.log is not created on my system, only the file /dev/shm/runcommand.info

[BuZz]

I'll fix that up - something must have changed the logic in bash as it's fine on my ubuntu desktop and on raspbian. Maybe a specific version of bash has some different behaviour, but the variable should be initialised so I will do that.