Start + Hotkey Will Not Exit the Game

MyFartSoTart

I have been having this issue for a long time now. When I’m playing a game, on any system, the only way to exit back to retropie is to press escape on the keyboard. I am playing with joystick and buttons, and I have hotkey configured as my Coin/select button. I have tried updating the system/ setup script etc. Anyone know why I’d be having this issue or if there’s anything else I should try? In the retro arch input settings, “Exit Retroarch” is set to escape, it won’t allow me to use the buttons, only the keyboard. So I’m kind of at a loss…

doubleL5

@MyFartSoTart The only way is to ither reset your button mapping or rest your retropie the same thing happened to me and I rest and everything works.

MyFartSoTart

@doubleL5 I’ve tried resetting my button mapping and if I remember correctly, I think I’ve already reset retropie a few months ago as well.

windg

It looks that retroarch.cfg file is broken. This can happen if you use the save button inside the Retroarch. It is preferable to use the Configuration Editor or modify the retroarch.cfg directly from the terminal

In this path :

/opt/retropie/configs/all

you will find this file : retroarch.cfg.rp-dist . Rename it to retroarch.cfg and you will recover the damaged file.

MyFartSoTart

@windg I found the file but what do I press to rename it? If I press enter it just opens the file.

windg

@MyFartSoTart

Then will rename the file with move command:

mv /opt/retropie/configs/all/retroarch.cfg.rp-dist /opt/retropie/configs/all/retroarch.cfg

sleve_mcdichael

@windg said in Start + Hotkey Will Not Exit the Game:

@MyFartSoTart

First delete the old file :

This is not necessary, mv will simply overwrite the old file if it exists.

sudo mv

Do not use sudo here; neither the command itself nor the location in which it's performed require it, and you will end up with an admin-owned file floating around in what is supposed to be user-space.

windg

@sleve_mcdichael Thank you, I corrected the answer.

MyFartSoTart

@windg Sorry, I don’t mean to sound like a noob but am I still supposed to be in the configuration editor? I’ve found the file but but the keyboard doesn’t do anything.

windg

@MyFartSoTart Not in the Configuration editor. You have to run the commands from the terminal. To open the terminal press F4 button when you are in RetroPie. You can connect too through ssh from a second computer. Another option is to use the file manager from RetroPie menu.

MyFartSoTart

@windg I tried moving the file with the command you specified and I got this error message:
root@retropie:/opt/retropie/configs/all#/bin/sh/tmp/mc-root/mcusr07qIN1
mu: target
‘retroarch.cfg.rp-dist' is not a directory
Press any key to continue…

Is there no way to just change the name of it?
Also in the /opt/retropie/configs/all, there is already a file named retroarch.cfg.

windg

@MyFartSoTart

This error looks weird. I test the command two times on my systems and it was always successful. Please provide more info : https://retropie.org.uk/forum/topic/3/read-this-first

windg

This post is deleted!

yserra

@MyFartSoTart

"Also in the /opt/retropie/configs/all, there is already a file named retroarch.cfg." -> obviously. Windg told you that file is corrupted. He explained you should replace it with a non-corrupted copy.

"mu: target" -> the command is "mv" (with a v, like in "velocity", not with a "u" like "unknown").

"‘retroarch.cfg.rp-dist' is not a directory" -> that's because you forgot to type the space between the two names.

Here is in 3 steps something that could help you to make less typing errors (press return after each end of line):

cd /opt/retropie/configs/all
rm retroarch.cfg
cp retroarch.cfg.rp-dist retroarch.cfg

The commands are :
cd, like Change Directory
rm; like ReMove
cp, like CoPy

Mind the fact there is, in the last line, a space between "retroarch.cfg.rp-dist" and "retroarch.cfg". Don't type "retroarch.cfg.rp-distretroarch.cfg" as if it was only one long word.

(as sleve_mcdichael said, it's not required to remove the file in step 2, because the cp command in step 3 will delete the original-corrupted file anyway. But I think it could help you to best understand what you are doing).