Can't enter runcommand by pressing a button.

BuZz

I appreciate you have tried lots of combinations, but the fact is, this is a problem others are not having (bear in mind the last image of retropie has had over 450,000 downloads). If there was a major issue, many more people would be reporting it.

So something with your set-up is the cause. Start from a fresh 4.1 image, on a specific machine, and try and reproduce it - then list the steps you took and exact specifications of that set-up.

meleu

@Dochartaigh said in Can't enter runcommand by pressing a button.:

I'll look at the specific controller configs for these 3-4 (maybe 5?) controllers I tried (...). That's stored in "/opt/retropie/configs/all/retroarch-joypads/", right?

No. You have to use the jstest tool that I suggested above.

Dochartaigh

@BuZz said in Can't enter runcommand by pressing a button.:

this is a problem others are not having (bear in mind the last image of retropie has had over 450,000 downloads). If there was a major issue, many more people would be reporting it.

I know BuZz, you tell me this all the time ;)

Here's exactly what I do taken from my notes. I use 95% of the same notes for the Pi Zero's vs. Pi 3's (but only included my workflow for the Zero below). Right now I have TWO different Pi Zero's built from these exact directions with the same problem. One was built last night, the other maybe 3 weeks ago (so RetroPie 4.1.2? and 4.1.11).

Download Pi 1/0 image from RetroPie site
Unzip img.gz file
Format SD card with ApplePi-Baker (I always do this 2x times just in case)
Put image on SD card
Plug in USB hub w/ USB wifi adapter, keyboard 2.4ghz adapter, 1x controller
Bootup Pi Zero 1st time - which resizes partition automatically

Setup keyboard for A,B,X,Y,Select,Start etc.
Setup USB controller for same
Setup Wifi (or plug in ethernet hub)
Config keyboard from 105 to 101 key with “dpkg-reconfigure keyboard-configuration” so it works properly
uncomment “disable_overscan=1” and “hdmi_drive=2” in Config.txt,
reboot

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
reboot
Update all core packages from binary (from RetroPie setup GUI)
reboot
install from optional packages: lr-prboom, lr-quickness, lr-tyrquake, kodi, Wolf4SDL, AND SSelph scraper from tools
reboot

Plug in USB drive with “retropie/roms” folders and while it’s copying all the ROMs over (about 13GB):

(make a consolidated save game directory and change permissions so my FTP program is allowed to copy over the config files more easily than using sudo nano to edit them in the hard-to-use linux text editor)
sudo -s
cd RetroPie
mkdir saves
sudo chmod 777 -R /home/pi/RetroPie/saves
sudo chmod 777 -R /etc/emulationstation

“/etc/emulationstation”
Change megadrive to “genesis”, change PC Engine to “tg16” (so correct logos for USA are used), reorder so NES, SNES, and Genesis are the first three systems listed.

“/opt/retropie/configs/all/retroarch.cfg”
Add: input_player1_analog_dpad_mode = "1" (and the same code for players 1-8 to use analog stick)
Change: savefile_directory = "/home/pi/RetroPie/saves"
Change: savestate_directory = "/home/pi/RetroPie/saves”

Run df -Bm until I see that everything is done copying over, then reboot.

Exit from emulationstation and run SSelph’s scraper (usually overnight) to get art for all ROMs.

THEN, I test everything which is where there’s commonly some of the issues I’ve described popping up.

For the last build I used stock overclock settings:

arm_freq=1000
gpu_freq=500
core_freq=500
sdram_freq=500
sdram_schmoo=0x02000020
over_voltage=2
sdram_over_voltage=2

And changed the default NES emulator to be lr-quicknes…that’s my entire process I’ve done about 100 times (not even joking) so far.

BuZz

@Dochartaigh said in Can't enter runcommand by pressing a button.:

this is a problem others are not having (bear in mind the last image of retropie has had over 450,000 downloads). If there was a major issue, many more people would be reporting it.

I know BuZz, you tell me this all the time ;)

I believe I possibly mentioned it to you once in your other topic. I will keep repeating it if you keep saying there is a problem with the software whilst being the only one with the issue so far :) (tbh I can't remember everything I have said to everyone - I have made a lot of posts to a lot of people).

Can you reproduce this on a rpi1/2/3 without the Hub and the same controller? What controllers are you using? What PSU ? Do you have any other controllers ?

For the sake of testing this I would avoid any overclocking.

Dochartaigh

BuZz, I thought I was special because I'm just the right amount of annoying (yet cheeky and fun) to stand out on this forum? WTH? lol

I don't own a Raspberry Pi 1 or 2 - just several Pi Zero's and I'm down to one Pi 3 Model B at the moment. I do have multiple hubs, and even those little flat micro USB to USB adapters I could plug a controller directly into the Zero if you wanted.

The controllers I've been testing with most frequently are iNNEXT brand (cheap chinese ones, but the best of the ~7 cheap brands I tested). Also have both the types of iBuffalo SNES and Famicon-style, Hyperkin Sega Genesis 6-button, a random NES 2-button, and about 15 different USB adapters for real controllers. Over the last couple nights I've tried the iNNext, red Buffalo Famicon-style, and the Hyperkin (Genesis 6-button). Honestly don't know if I was pressing 0 or 1 on all of them - usually just try at least 2 random buttons at a time, get mad it isn't going into runcommand, then switch in another controller (sometimes rebooting in-between if plugging in another controller crashes the system like it's been doing lately on occasion like I mentioned I my other topic).

Power supply is usually an Anker 4-port 10amp? USB charging hub (2.4 amp per channel). When I was testing two on Zero's last night at the same time I stole the Canakit 2.5amp from the Pi 3. Multiple USB cables - mostly Amazon Basic and some Cables Direct.

Also, I posted in more detail on my other topic, but I found a random SD card and popped it in. It has RetroPie 4.1.5 on it. All my test NES/SNES games play perfect on it (no lag) AND runcommand seems to work whenever I try to enter it with the same INNext brand controller (and same everything else like power/HDMI/hub)...just thought I'd put it out there that 4.1.5 seems perfect but 4.1.11 is giving me issues (but it IS only one example...just something to note).

mvgilpatrick

I am not sure if you found out the solution, but for me, oddly enough, it was about moving the left joystick on my PS3 controller that I use for RetroPie. During the run command splash menu, I move the left stick around to enter runcommand launch menu.

Ncrx

@dochartaigh I have the same problem cannot access launch options unless I use a keyboard it works every time with the keyboard and the o key is mapped to select on my controller but with the controller it never works if you have found a fix for it would be nice to know. thx.

meleu

@ncrx please open another topic and give as much info about your setup as you can (like those suggested in the read-me-first post).