Filed it nevertheless as it is useful if one does not have additional "safe shutdown hardware" or don't want to fiddle with triggerhappy.

@Crush

I hold the Start button, which I set somewhere doing the initial setup, but now I'll be darned if I can find where that was. Now that I'm thinking of it, it could be that I set that in RetroArch without really paying attention, which would explain why this is happening. heheh

I recall seeing something in EmulationStation, but not being happy with the options. I'll take a look again.

i solved this in a simpler way.

I made a python script which generates a "AltF4" keyboard event:

#!/usr/bin/python import keyboard keyboard.send('Alt+f4')

(it requires the pyhon keyboard library. If you don't have it on your system, then give the command "pip install keyboard" to install it.

and added a line to call this script in /opt/retropie/configs/all/autostart.sh:

emulationstation #auto sudo python /opt/altf4/altf4.py

for me it's solved. I still think functionality like this should be included in the normal retropie build. This prevents a security issue (someone can press alt-f4 in emulation station and will have access to the system with sudo rights with entering any password)

@lacaca Please add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Well it seems to be working OK so I have no complaints. :-) Naturally, if you have a better way of doing this now we'd all love to see it! ;-)

Thanks for the help. :-)

@dankcushions

Well I guess I wont be playing that game. Thanks for the info

John

Solution:

Copied emulationstation from /usr/bin to /usr/local/bin and things worked as normal.

@piuser1234

However, for Zelda in nes, I can control the game just fine and do everything normally, except quit. I can't get out of it without pulling the plug.

when you did https://retropie.org.uk/docs/First-Installation/#configure-controllers, what did you configure as 'start' and what did you configure as 'hotkey'? to quit it's hotkey + start.

@mvgilpatrick It's likely to do this issue: https://github.com/RetroPie/RetroPie-Setup/issues/1985.

@SkittleBrau79 said in Emulation Station does not quit to command prompt:

I've solved this. Still not sure what the cause was... but doing a full update of all installed packages corrected it.

I had this in the beginning. How many roms have you got installed? Take a look at this:
https://github.com/retropie/retropie-setup/wiki/FAQ#why-does-shut-down-and-reboot-take-ages
Could be related?

@synack

autostart.sh says the following

emulationstation #autostart

Tried adding it after that I must be typing something wrong lmao

UPDATE - figured it out.. Found this from @meleu

"/opt/retropie/supplementary/emulationstation/emulationstation.sh" --no-exit "$@"

thanks guys :) much appreciated for everything

I wasn't able to map the hotkeys on the keyboard which is configured as a controller, but since I will use pyAutoGUI and scripting for GPIO inputs, I that's not a big deal.

The keycodes found in mupen64plus.cfg relate to ascii characters, and so I remapped the functions I plan to access later via GPIO to keys I won't need.

Here is simple overview I used to figure out key-values: Ascii Table
You have to look for the decimal values.

@dankcushions thanks!

...fresh ROM for AstronBelt has it working better. Enemy craft shooting again, collision detect working. Only bad thing is that when the "disc" is changing scene I often get a flash of an explosion out of context for what's happening in the game. I tried deleting the DAT file and re-parsing the files but no joy. If anyone has any experience of this and fixing it, I'd appreciate any pointers.

Strangely Galaxy Ranger seems spot on.