@mitu Off course this will work. However each time I want to change another item have to create the retroarchcfg file again. When I use a simple copy script all other settings can't be changed anymore. So each time I go to the retroarch menu and change something the retroarch.cfg gets overwritten. So using two files (one with and one without the disabled hotkey) just isn't a working solution. I really want to be able to make it independent of other changes in the file I sometimes do using the retroarch menu. A script that edits that single line is the best solution, however I'm just not clever enough to make the script.

Looks like an error starting it, can you post the /dev/shm/runcomand.log file contents ? Also, please add more info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu Thanks! That was the bit I needed to change. I replaced "standard" with "dualshock" and now analog controls work :)

Do you have an arcade panel configured or are you just testing out with a controller ? The X button is mapped to the input_menu_toggle_btn action, so you can remove the line containing the mapping from the controller configuration file. The file is generated by Emulationstation in /opt/retropie/configs/all/retroarch-joypads, named after your controller. To be honest, I'd be more concerned about the Hotkey + B (reset content) combo, since it will reset the game, while Hotkey + X merely pauses it. If you're using a keyboard, I think F1 toggles the menu.

lol fixed it. So apparently I didn't have to edit the retroarch.cfg file I thought I had to, which was the one under config/retroarch/config. The one I had to edit was under "all", some sort of root directory not accesible through the File Manager. I had to use the Configuration Editor to make the change. Initially I had tried using the editor within File Manager (nano).

Ooops, sorry. Wrong thread.

@mikeylikesit33 said in RetroArch GUI on my Hotkey?: No idea what was wrong, as the CFG's were still all the same as before I upgraded my Retropie per Ultraedit File Compares... but there was something funky somewhere. As glad as I am for you that your problem is solved, the nuclear way of solving it made sure that neither you nor we may learn what caused it.

@thelostsoul I just looked up which emulators are supported and the most common Mega Drive emulators does. So, thats not the problem here I guess. https://docs.libretro.com/guides/retroachievements/ I enabled RetroAchievements 2 weeks ago too on my Pi3 and not all systems did work, when they should. I can't say why. Maybe this have something to do with the RetroAchievement site itself? So, try again later. Here are the systems I tried to enable by changing the configuration files. I need to retest them too. Working cheevos: nes, snes, gb, gbc, gba, md, ms, gg Not working cheevos: ngpc, a2600, pce Maybe add the information from this thread first: https://retropie.org.uk/forum/topic/3/read-this-first

I may have broken this myself in the beginning when i was messing around alot with RetroArch and the controllers.

@dankcushions Thanks! I should be able to map my buttons now. Still I'm mainly concerned on how to make this little screen work with "ir-mupen64plus" beacause I love Retroarch menu options. Any help for that is still welcome.

Okay, finally after hours of tinkering under the hood I'm finally able to make Shining in the Darkness work with cheats without crashing RetroArch. I tried changing the core emulator from pico to a different one and that didn't fix it. I tried renaming *.cht files and copying templates directly and that didn't fix it. I tried a different version of the rom with all three Genesis/Megadrive cores and that didn't fix it. I couldn't seem to figure out how to use my USB keyboard to input cheat codes manually so I painstakingly physically drew by hand a character map using my controller and a pencil. Eventually, I managed to figure out exactly where all the necessary keystrokes I needed were located and input a couple of codes and they WORKED! I was able to save this data as its own file using RetroArch and (crossing fingers) reloaded the game from scratch and successfully reloaded the newly made cheat file and it indeed works just fine. I then input all the rest of the codes and the older ones and created a new file to load with the game. Whew! That was an adventure.

set your controller again with emulation station

Thank you so much. I have a friend I'm setting up a disk image for and he really wanted to have the cheats work.

@barbudreadmon Thanks very much, will do as advised

@mitu Perfect! Now RGUI it's back. menu_driver = "xmb" was in snes/retroarch.cfg, deleting that line fixed it. Thank you very much :)

For updated info purposes. When you search in google "how to disable retroarch menu hotkey", this thread is the first thing that comes up. As for 19 Jun 2019 All of the above didn't work for me. But this is the solution now: sudo nano /opt/retropie/configs/all/retroarch.cfg search for menu_driver The default value should be "rgui". Change that to "null" Null, with two L. Save and restart emulationstation.

To solve this problem You can specify these settings for each controller in /opt/retropie/configs/all/retroarch-joypads/<gamepad's name>.cfg: input_left_axis = "-0" input_right_axis = "+0" input_up_axis = "-1" input_down_axis = "+1"

@blitzgreig You need to start by posting the information requested in this post: https://retropie.org.uk/forum/topic/3/read-this-first No idea what hardware you are running, what software etc.....

@danielrosero said in Retroarch issue: ShanWan PC/PS3/Android (8380/21760) Nevermind, minutes ago found the solution. Looks like the Configure Input option in ES wasn't saving the appropriate cfg filename in /opt/retropie/configs/all/retroarch-joypads The file ShanWan PCPS3Android.cfg SHOULD BE: ShanWan PC_PS3_Android.cfg And copy the corrected file to the /opt/retropie/configs/all/retroarch/autoconfig/ folder. And it should work!