@Floob yeah - it was after the 1.3.6 release - when the next retroarch release is out I will do some testing etc. (well may test before, but it won't be enabled in retropie until after the point release).

@meleu It's not something anyone else can help with really - It requires ssh access to the server as well as a custom patch for the generation tool due to a bug. It's intentionally a manual process so changes can be reviewed etc.

So an update here after some playing around I am noticing that the runcommand is not saving the any video resolutions I change. I thought it was only changing resolution thus the aspect ratio wasn't changing but apparently it should also be changing aspect ration since its in the options. When I press select on my DS3 to change an option it doesn't see to show the option change in the parenthesis. So I think this is actually a runcommand issue?

Thank you for the help, roms launch now after following directions.

@tfpHumorBlog yes I have actually, it's because the joy2key script is configured to use input of js0 by default but my controller was js1
So make sure your joystick is js0 input

@speendo Hi,

My system is built from a Raspbian Jessie image, with RetroPie (3.8) manually installed, and Kodi installed via RetroPie.

I added a text-mode menu which displays on boot, or after exiting RetroPie, Kodi, or Raspbian Lxde desktop.

I wrote a guide which may help you:

Multipurpose Raspberry Pi – Part 2: Adding a Menu to Access RetroPie, Kodi, and the Raspbian Desktop

This is a very old topic, but I wanted to throw my script in so you can edit it to your liking. I don't have an Adafruit display, so I had to do some tinkering but you've all done the heavy lifting. Here are the minor edits for using a 3.5" display with fbi. Make sure you have the system.jpg images in the correct system rom folders.:

# /opt/retropie/configs/all/runcommand-onstart.sh # get the full path filename of the ROM rom=$3 # rom_bn receives $rom excluding everything from the first char to the last slash '/' rom_bn="${rom##*/}" # rom_bn receives $rom_bn excluding everything from the last char to the first dot '.' rom_bn="${rom_bn%.*}" # get the system name system=$1 # set the image file to the first result matching the ROM name - accounts for various possible file extensions img="$(find "/opt/retropie/configs/all/emulationstation/downloaded_images/${system}" -type f -name "${rom_bn}-image.*" | head -1)" # check to see if there was a file found (length of the file name not zero), if not, use an image based on system if [[ -z "${img}" ]]; then img="/opt/retropie/configs/all/emulationstation/downloaded_images/$system/$system.jpg" fi # run the python script to display the image sudo fbi -T 2 -d /dev/fb1 -noverbose -a "$img"

@BuZz @edmaul69

Hey guys - I finally got around to making this change it worked like a charm. I exited ES, then made the change from terminal, wrote the changes, and launched ES from terminal.

When I got back and ran my first ROM, the cursor was still there, but every ROM I launched subsequent to that opened and exited without the cursor. I thought that detail my be worth noting for future reference. I'm finally done configuring and learning about Retropie and on to enjoying it thoroughly.

Thank you for all the incredible work, documentation, and support!!!

Thank you for writing back @meleu I think my "method" is somewhere inbetween. The fact is my non-merged full 0.37b5 romset (2241 roms) matches perfectly the 0.37b5 snaps (2241 snaps, a lot of work saved!) so what I do basically is:
1.- add
screenshot_directory = "/home/pi/RetroPie/roms/mame-mame4all/images/"
to
/opt/retropie/configs/mame-mame4all/retroarch.cfg
2.- move roms to Retropie/roms/mame-mame4all
2.- move snaps to Retropie/roms/mame-mame4all/images
3.- run
/opt/retropie/supplementary/scraper/scraper -add_not_found=true -append=true -download_images=false -image_dir="images" -image_path="images" -image_suffix="" -img_format="png" -img_workers=0 -no_thumb=true -thumb_only=false -thumb_suffix="" -use_ss=true -use_gdb=true -use_ovgdb=true -workers=4

Then gameslist.xml is created. I think those steps might be useful to users who already have a preference for snapshot packages.

However, I wonder what would be the best approach in the following scenario where there it no a rom <--> snap match:

1.- add
screenshot_directory = "/home/pi/RetroPie/roms/snes/images/"
to
/opt/retropie/configs/snes/retroarch.cfg
Move all 3438 No Intro SNES roms (Nintendo - Super Nintendo Entertainment System (20161130-222348_CM).dat) to
Retropie/roms/snes
Move all 3352 .png snapshots (No-Intro 20061119 Super Nintendo Entertainment System Screenshots.7z) to
Retropie/roms/snes/images

One more problem, snapshots name do not match rom names but it is relatively easy to sort it out.
Eg. Actraiser (U).png versus ActRaiser (USA).zip
So I have run a number or find and replace to swap U for USA, J for Japan and so on. Once .png files match their counterparts in the roms folder, the same scraper command is run to generate gamelist.xml
In any case, it is clear that there are less snapshots than rom files so there will be roms without snap. Any ideas on how to find out (list) what are those roms?

PS. I am going to have a good look at that link. Thank you for it.

@Rookervik said in Loading a custom image on the Run Command:

Aaaanyway, I can get it to work by editing line 2 of the show_launch function to set image="" to the image I want. Then I just have to spam smashing the X button to get to the run command menu.

Hey dude! Today I tried what you were doing here and I found a simple way where you don't have to spam smashing the button to access the runcommand menu. Just put a & at the end of the fbi command. Like this:

fbi -1 -t 2 -noverbose -a "/home/pi/retropie-tron.jpg" </dev/tty &>/dev/null &

It would be really cool if you artist guys make a fancy "loading" image, uh? :-)
(With the "press a button to configure" message, of course.)

I know this is an old thread, but I'm replying here because it's the first "open" result on a related Google search.
I wrote a quick script that I'd like to share for quickly parsing the above into a user-readable format

Sample output:

Status: 0x50005 Undervolted: Now: YES Run: YES Throttled: Now: YES Run: YES Frequency Capped: Now: NO Run: NO

Script:

#!/bin/bash #Flag Bits UNDERVOLTED=0x1 CAPPED=0x2 THROTTLED=0x4 HAS_UNDERVOLTED=0x10000 HAS_CAPPED=0x20000 HAS_THROTTLED=0x40000 #Text Colors GREEN=`tput setaf 2` RED=`tput setaf 1` NC=`tput sgr0` #Output Strings GOOD="${GREEN}NO${NC}" BAD="${RED}YES${NC}" #Get Status, extract hex STATUS=$(vcgencmd get_throttled) STATUS=${STATUS#*=} echo -n "Status: " (($STATUS!=0)) && echo "${RED}${STATUS}${NC}" || echo "${GREEN}${STATUS}${NC}" echo "Undervolted:" echo -n " Now: " ((($STATUS&UNDERVOLTED)!=0)) && echo "${BAD}" || echo "${GOOD}" echo -n " Run: " ((($STATUS&HAS_UNDERVOLTED)!=0)) && echo "${BAD}" || echo "${GOOD}" echo "Throttled:" echo -n " Now: " ((($STATUS&THROTTLED)!=0)) && echo "${BAD}" || echo "${GOOD}" echo -n " Run: " ((($STATUS&HAS_THROTTLED)!=0)) && echo "${BAD}" || echo "${GOOD}" echo "Frequency Capped:" echo -n " Now: " ((($STATUS&CAPPED)!=0)) && echo "${BAD}" || echo "${GOOD}" echo -n " Run: " ((($STATUS&HAS_CAPPED)!=0)) && echo "${BAD}" || echo "${GOOD}"

@meleu I don't. Runcommand will continue even if there is an error. Please try to not constantly send me questions and requests.