@darkus I have the RPI system 24/7, but I don't have this problem. The TV turns off the screen after about 1h (2h maybe). I have the screensaver/power options active in EmulationStation, if that makes a difference.
One thing to try is to move the HDMI PI cable to a different TV port - if you have more than 1. Mine is set HDMI2, which is labeled PC, and has the Game mode active.

@jenslyn87

Very nice!

@mrbear2899 either bind the hotkey to the same button as fastforward, or disable hotkeys entirely.

@dankcushions ok thank you thats what i thought just didn't know if there was a way to load my pi zero image tru a terminal command or something. Ill just set up another one then.

@afunnyname Did you enable SSH on your Raspbian image ?

@benjaminjay I thought you were asking, and I quote:

What is the best way to fix these ROMs using a Windows PC?

But you fail to mention what kind of ROMs, so I assumed arcade, and the answer is that you need to obtain the right ROM version for the right emulator. They are not interchangeable.

Your second question is quite a bit different than that. I suspect Windows is only going to be able to read the boot partition of an SD card setup with the official image. You will need to load a certain kind of driver to let you read/mount linux drive partitions, or use Linux to read them.

<EDIT> @mitu above has a better suggestion that might work for you. Load the image on the system that is going to run it, then connect to the ROM folders over a network with your windows sysetem to add/remove/replace ROMs.

Ok, I think I know what my problem is now. It's because I'm using the XboxDrv software to override the inputs when I load certain systems. When I first started using it, it was my understanding that I could use configure settings to load on-demand as needed whenever I wanted to use a different controller. For instance, when I play a Sega Genesis game, it detects I'm loading that system and runs an additional driver to let me use my 6-button Pad and the MayFlash adapter. It does this as part of the runcommand-onstart.sh. When the gaming session ends, it unloads the driver. Apparently the problem comes from it ALWAYS loading the driver, rather than only when I connect a controller to it. I discovered this by testing the various controllers after moving the Xbox Dongle to the Pi's USB Port 0. I can replicate it every time, with the controllers I have configured.

The NES system is configured to use an NES controller. So when I try to launch and NES game, RunCommand is looking for input from that controller only. When I connect a controller to that port, I can now access the RunCommand window. The same is true with Sega games. I can only access the RunCommand windows by triggering it from a controller connected to that port.

In both scenarios, the Xbox Controller works fine in game and in RetroArch. But I can't navigate RunCommand with it. In fact, I can't navigate RunCommand with anything other than the keyboard on any systems I have configured with XboxDrv. I don't have a configuration for SNES, so when I'm using my Xbox controller, everything works like it should. I can trigger RunCommand and navigate with the Xbox controller jut fine.

I think I need to go back through and examine my runcommand-onstart.sh settings. I might be able to get it working by adding an Xbox controller configuration to the settings.

runcommand-onstart.sh

That's my current settings.

sudo dpkg-reconfigure x11-common, nevermind, i'm stupid

Yeah, I installed Recalbox, now my PS4 controller isn't pairing. I guess the grass isn't greener on the other side. lol

I have today the same question and i'm interesting in create specific configuration file for each game.
What would be the best for me is that this specific configuration file only overide the core_region option with one line :
core_region = ntsc-u for us game for example.
So when i change other parameters in retroach it applies to the default config file.

Is it possible?

@madmodder123 I changed the vector images of buttons to symbolic (playstation). I converted them from a raster to a vector in an inscape.
In this thread, @jacobfk20 helped me with the compilation, and everything worked.

@francegue said in Kodi won't start when launched from Ports:

/etc/emulationstation/es_systems.cfg

@Rascas : indeed, installing kodi from the command line instead of from retropie-config solved the problem. Thanks!

I see I still have the file /etc/emulationstation/es_systems.cfg totally empty, do you think it can be an issue if I reboot?

Phiuuu.... I had the same problem @CeZza_Gant .

First i updated BlueZ to version 5.37 from this link

https://learn.adafruit.com/install-bluez-on-the-raspberry-pi/installation

There's a newer version (5.47 or something) but when i installed that one it didn't work.

Anyway... after following the instuctions for 5.37 suddenly it worked. Not sure what happened but it worked.

Turn On my Adafruit Feather 32u4 Bluefruit LE I entered to configuration ->bluetooth->Register and connect Retropie detects my BLE device and then connects Something happens there, the UI freezes so i have another keyboard connected to my RPi, Ctrl+C to go back to Emulation Station And that's it. The feather's blue LED is turned on and connected to the RPi You go to configure input and the feather is detected as a keyboard.

It all was a trial and error, so, if my instructions doesn;t work, keep trying.

Regards from Mexico!

@addison milkdrop is not supported on the Pi. Shadertoy is really the best you can get atm. This needs to be installed via the command line. See 6.1 http://kodi.wiki/view/Ubuntu_binary_add-ons.
So run sudo apt-get install kodi-visualization-shadertoy Waveform and Spectrum also run on the Pi

@buzz

Thanks - I finally got it figured out. I had been overlooking the files in sources.list.d/ and noticed that both collabora.list and raspi.list had wheezy listed. Changed them to jessie, re-ran the update/upgrade process and things started working - except sound. I also had to add dtparam=audio=on to my config.txt file for some reason, even though that had been fine previously without it.

Anyway, thanks again for the help working through this problem. <3 RetroPie.

took your advise, made just one partition. thanks a lot

programing pinn or noobs needed more work

(https://github.com/procount/pinn/wiki/How-to-Create-a-Multi-Boot-SD-card-out-of-2-existing-OSes-using-PINN)

Followed this fella on you tube who tells you how to boot from the sd card without a boot program, just rewriting a file, and the image is now working, now i'am enabling the unallocated space that's left in the drive to add more roms and media.

(

)
thanks mitu !

@Trailjacker I fixed it I just switched emulators by entering the config setting of the n64 emulator

@challenger2010 Apologies for bringing this back from the dead, I wondered if you'd managed to resolve this calibration of analog joysticks in advmame?

I am trying to configure some pots for a Warlords mame cab, and I have a nasty deadspot at 0,0 that I want to remove!

http://www.advancemame.it/doc-advj

Thx in advance (mame)

R