Runcommand Images Preventing Runcommand Menu

mediamogul

I recently installed the Carbon themed Runcommand images to their respective folders at /opt/retropie/configs/SYSTEM_NAME/ and now I cannot invoke the Runcommand menu unless the images are removed. I've tried to trigger the menu with a controller, as well as a keyboard and the menu will not activate as long as the images are installed.

Pi Model or other hardware: RPi3 Model B
Power Supply used: 5.1V 2.5A
RetroPie Version Used: 4.1.9
Built From: Pre made SD Image on RetroPie website
USB Devices connected: 2 Logitech RumblePad 2 Controllers, Keyboard/Mouse
Controller used:Logitech RumblePad 2
Error messages received: None
Log found in /dev/shm/runcommand.log (if relevant): Empty
Guide used: None
File: Not Applicable
Emulator: All
Attachment of config files: Not Applicable
How to replicate the problem: Installing a 'launching.png' image to /opt/retropie/configs/SYSTEM_NAME/ and launching a game.

dudleydes

Does this post help?

meleu

@mediamogul the link @dudleydes mentioned is right.

For a short time we could invoke runcommand while the image is being shown (running fbi in background). But it was disabled in this commit due to some input issue, unfortunately.

mediamogul

@dudleydes said in Runcommand Images Preventing Runcommand Menu:

Does this post help?

It does indeed, sir. Thank you. Since the timing for this is now a bit counter-intuitive to the request being made on screen (I assume this is a necessary byproduct to allow the image to display) I'll make a note of it on the Wiki.

mediamogul

Hey, @meleu. I'm sorry I ignored you. Your post didn't show up for some reason when I was responding to @dudleydes and I'm just now noticing it. That sounds like a nice solution, but is the input issue still a problem?

meleu

@mediamogul To be honest I don't know what exactly is the issue.

In the commit @BuZz says

fbi/Retroarch has stdin attached to /dev/tty/. When fbi exits it causes issues keyboard input/stdin.

Maybe the problem happens for those who use the keyboard to play games in RetroArch, but I'm not sure.

Concat

Yeah, I find I have to mash the button during the image to get the runcommand menu to show.

mediamogul

@meleu

Maybe the problem happens for those who use the keyboard to play games in RetroArch, but I'm not sure.

Interesting. I guess until something changes in that department, the notation I made on the change in timing will help. Most users will have to read that section anyway when they install the images.

@Concat

Yeah, I find I have to mash the button during the image to get the runcommand menu to show.

As it turns out, a normal button press will still do the job. It just has to be pressed slightly after the image disappears.

Concat

@mediamogul said in Runcommand Images Preventing Runcommand Menu:

@Concat

Yeah, I find I have to mash the button during the image to get the runcommand menu to show.

As it turns out, a normal button press will still do the job. It just has to be pressed slightly after the image disappears.

Heh, I was confident there was a window of opportunity, but that window is pretty damn short. Tests your reflexes a bit. I'm better off just mashing :)

mediamogul

@Concat said in Runcommand Images Preventing Runcommand Menu:

I'm better off just mashing :)

I hear you. I've made the same comment about a few fighting games in the past. 'Primal Rage' comes to mind.