Hi, you can configure a standard keyboard to make EmulationStation not ask you for a controller on start-up, even if the keyboard not present. You can accomplish this in two ways (any of which only needed once):

Connect a standard USB keyboard and configure it in ES like any other controller.

If you are proficient with accesing the config files (SSH, Samba) and don't have a keyboard at hand, you can add the following snippet to /opt/retropie/configs/all/emulationstation/es_input.cfg to add a keyboard with standard mappings:

<inputConfig type="keyboard" deviceName="Keyboard" deviceGUID="-1"> <input name="pageup" type="key" id="113" value="1"/> <input name="start" type="key" id="13" value="1"/> <input name="down" type="key" id="1073741905" value="1"/> <input name="pagedown" type="key" id="119" value="1"/> <input name="right" type="key" id="1073741903" value="1"/> <input name="select" type="key" id="1073742053" value="1"/> <input name="left" type="key" id="1073741904" value="1"/> <input name="up" type="key" id="1073741906" value="1"/> <input name="a" type="key" id="115" value="1"/> <input name="b" type="key" id="120" value="1"/> <input name="x" type="key" id="97" value="1"/> <input name="y" type="key" id="122" value="1"/> </inputConfig>

This snippet has to be added between existing <inputList> and </inputList> tags.

An added benefit of configuring a keyboard is that if you don't have any controllers handy you can always plug a keyboard and control ES with it. Good luck!

Oh thanks guys, I putted my bios on the BIOS folder and not in the BIOS-dc folder, now everythink work grate

@mitu said in Date/Time synchronization:

epending on the timesyncd service

Good idea, I'm going to try that. Thanks.

@frodriguez puedes usar google translate para traducir tus preguntas y también las respuestas.

También quiero eliminar el inicio de sesión con contraseña. No puedo probar ahora porque tuve que desarmar la caja que estoy construyendo, pero hice esta nota cuando alguien más hizo la misma pregunta antes:

Autologin:

at command prompt, type sudo raspi-config select option 3 in menu (Boot Options) select option B1 (Desktopp/CLI) select option B2 (Console Autologin)
Then Ok, exit all the way and restart.

pruébalo y dime si funciona.

@thelostsoul

I don't know the full extent of the problem, but it seems like you could create a script that would first launch RetroArch and then after a wait, send a network command to load the game. You could then create a launch command in /opt/retropie/configs/emulators.cfg that would launch the script and apply it to the ROM. Granted, this is a very involved solution and there might be a better way. Out of curiosity, why are you opposed to simply launching the games with a core that will run them?

NIce one, that fixed it!

I have already tried all of what you tell me.
Anyway thanks for trying helping me.
If someone has the same problem, the solution for me is to download retropie 4.3... - -‘

@Nextus
Make sure you've purchased the NESPi Case +, the latest revision from RetroFlag.
There were issues reported with the previous case and the higher power requirements of the Pi 3+.

@angry_bucket
I don't think that's correct, but curious to know more about your experience.

RetoFlag's safe shut-down script advises to set this to On before installing the scripts. I followed this and everything works fine (as long as EmulationStation is running).

https://github.com/RetroFlag/retroflag-picase

[Edit] I purchased one of these a month ago - love it.

someone asked about this on reddit a few weeks back, and i told them to add it to:
/opt/retropie/configs/all/autostart.sh

expressvpn connect &
emulationstation

it seemed to work for them. here's the thread for reference.

@topsys https://retropie.org.uk/forum/topic/16307/retropie-4-3-15-stretch-images-for-testing

@herb_fargus I already did install it, made the whole thread from my Raspberry. Also I don't know why but the custom install i did for MPV and its codecs only works on tops of full raspbian, not raspbian lite. At least thats what the guy from the thread said.

@mitu
Thank you Mitu!

@sli4 It looks like the tvservice program arguments are not correct or an update to it changed them. You'll have to find the line where the program is called and make sure it uses the correct parameters. Run that command from your terminal to check that you get no error.

@darknior @pjft
Oh... one thing that could go wrong with the symbolic link method.
If you insert two USB devices at the same time then the naming could get wrong. Means that /mount/usb0 is not always Device 1
and /mount/usb1 is not always Device 2. They can change, so working with fstab and giving the devices their unique numbering is better. But the symlink is imho the fastest way ...
need to say: it is not supported by official intructions!!

The bash myscript.sh is working for ES because it is setted in es_systems.cfg since RetroPie 4.0

For anyone else that is having this issue i have discovered the solution.
install retropie 4.0 rather than 4.3 and simply update the setup software from on the pi rather than when mounting the micro sd card.

PINN allows you to install Retropie directly to an USB stick. https://www.raspberrypi.org/forums/viewtopic.php?t=142574

Thanks both.

Have added a 5 second delay, and it works now.

Will look at adding a powered hub.

This is really strange, I haven't used samba for a long time. Maybe it has to do with some RP update? It completely ruined my sanity last night :P

@dereksanderson Firstly, the Raspberry Pi is an ARM based single board computer as opposed to a x86 intel based pc. You cannot therefore expect a linux based "image" that has been configured for a Raspberry Pi to boot on a pc. You will need to follow the documentation to achieve what you want...

https://github.com/RetroPie/RetroPie-Setup/wiki/Debian

Second thing to note regarding "a great image from MLPIXEL (a 32GB) which boots on Rasperry Pi ". If this has roms then it is illegal. You should check out point 5 of https://retropie.org.uk/forum/topic/3/read-this-first as indicated from @buzz as I was typing this very line.

I have found a solution. simply install 4.0 rather than 4.3 and update the setup software on the pi after first boot