@danneskjold in terms of your special characters you can either ssh through putty or change the keyboard configuration:

@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

@GirlUSoCrazy working now, sdcard was indeed bad, thanks again!

@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.)

And it worked, thank you for the suggestion.

@jtu128 Emulations Station skins don't affect Kodi. Older skins can be incompatible with Kodi 16.1.

You can remove/install Kodi again in the RetroPie-Setup scripts. If you want to remove Kodi from the command line, it is like in most of linux distributions:

sudo apt-get remove kodi kodi-bin sudo apt-get install kodi kodi-bin

@doing-my-head-in Think I had to change it to an iso and then generate the cue from it, then it would load. If it displays 2 versions of the game in the list, you may need to edit the list of accepted file types to not include the iso and then it'll just show the cue.

+1 for the overscan issue. I have one television that I need to adjust the overscan manually in the /boot/config.txt file, but another television that I don't need to adjust the overscan at all. In the same config.txt file you can adjust the amount of overscan.

Hi,

So I ran the commands from SSH. Booted up the Pi and only one controller recognised. I typed in LSUSB and could see that the Pi could only see one controller. After multiple tests I did some testing and it looks like the USB cable is faulty. This would explain why the second controller is not recognised however it did work up until (and after the problems).

I will borrow a controller from a friend and see if I can get this working but to be honest I might just try and get a second controller running with Bluetooth.

@GetKeyOpenDoor yes, sussed that in the early hours of this morning! Haha! Thanks for your help :)

@Ethan64 you could have saved yourself a few more hours by reading the documentation in the first place: https://github.com/retropie/retropie-setup/wiki/First-Installation#emulationstation

@Retropie-Love i lost the one in etc after updating something. The one you need should be in /opt/retropie/configs/all/emulationstation/es_systems.cfg

Just wanted to add that this has happened to me as well. I am using a Model A Gen1 Pi. Went through the setup without a problem and then after a reboot I get the same msg, controller not configured.

tried setting up Xbox one controller and works fine thanks for the help mate!

Well I solved this with a work around. I had splashscreens disabled. I created a black screen png. I re-enabled splashscreens and chose my custom one. Now the autologin text does not show.

thx for the help, finally got it compiled, but it mostly just crashes back to retroarch 10 seconds into startup on the games I wanted it for. ahh, well, that's why it's called experimental.

@BuZz Thank you! That fixed the rest of it. I had to change the filesystem to exfat-fuse instead of vfat but otherwise it worked perfectly. :)