Not Recognizing *Start* Input - Super Mario 1 NES

KN4THX

Here we go :

Pi 3
PiHut 2.5a power supply
64gb Samsung evo
Ps3 controllers/ibuffalo
lr-fce nes emulator
Official 4.3.8 Retropie & updated

I've had my Pis for a while and as of today I booted up an existing Retropie on my Pi3 after finishing my Pi-Cart project as a gift. Apparently I did something or sat on the controller (again) and the configuration for NES is wonky for lr-fce only(NES lr- emulators, not just lr-fce). I was going to check my controls but the retroarch menu didn't accept the 'A' Button so I figured I accidentally mapped something wrong. I thought I could delete the cfg in configs/nes/ and have it generate a new one. Technically it did, and my issue is resolved control wise, but now the Retroarch menu has the blue theme and a different layout. Can anyone advise how to change this? As it is now it looks like my old PS3 menu :) I'm currently doing a full update while I type this on a longshot, but I had already reinstalled the lr-fce package from Retropie_Setup.sh and that didn't change anything.

KN4THX

FIgured it out and copied an old retroarch.cfg as well as learned a lot tonight about core overrides and permissions thanks to bits and pieces of previous posts on here. Thank you for this awesome forum :)

mitu

@thedatacereal said in Not Recognizing *Start* Input - Super Mario 1 NES:

but now the Retroarch menu has the blue theme and a different layout

That's the default RetroArch menu interface - called xmb. The default RetroPie config will default to the rgui menu interface, which is what you're used to see, but if you deleted the config added by the setup script, then you'll see the default (xmb).

KN4THX

I see that now thank you. I thought deleting the cfg like I did in a non libreto core would regenerate the same but I see there's more tied to those now. I didn't see the hidden .config directory for the core overrides until I simply looked at the default directories in retroarch and saw them. Now I will check out the core overrides and see what the benefit of one over the other is since one locks the other out.

mitu

@thedatacereal If you're looking to create per-core configurations, the easiest is to do them in the RetroArch gui, then save them with Save Core Overrides. They'll be saved into the .config folder and they'll contain only the changed configuration options, much easier to read and maintain.