I have this curse...both at home and I work. I can't figure out a problem to save my life. Then, after I publicly make an ass out of myself by asking...the situation just clears itself up, as if there is some sort of cosmic force at work who wants me to constantly humiliate myself. This situation seems to be no exception. Without changing a thing, it seems to be working the way I want it to the past day or so.
@iazrt The Showcase theme (my favorite) does the same thing as well and also has a blank tag which I just removed. Just search for >< and you'll easily find a blank.
@mitu Of cours, but then you mess up your rom set.
On the other hand some systems or naming conventions use rom sets which have names which are not unique. (I don't find one at the moment, but i saw such discs)
@polygonman244 Hey, there. I know this goes back a year, but emulationstation does not detect my PS Classic controller on the latest version of Retropie on a Pi4 ("no gamepad detected" after boot) and I'm just hoping you can please elaborate on what you meant by "I just used the 'map controller' setting and it worked." Do you mean the Configure Input screen after you press start in emulationstation with a recognized controller? Or is there another way to map a controller that I've missed?
@Garavar You should be able to un-bind that key from the said menu (Esc or delete) and assign the Config menu to Tab instead of right joystick.
What emulator/RetroPie version are you using ? Add more info as requested in https://retropie.org.uk/forum/topic/3/read-this-first.
If I were to hazard a guess, I would say that changing over to a USB boot means that your USB ports are staying powered on when your system isn't running. You should probably just unplug the power source after shutdown.
Make sure your RetroArch works, this is not an Emulationstation problem. Also, this is a RetroPie forum, not a general RetroArch forum - you might want to try the libretro forums if you have problems using RetroArch on Windows.
@roslof The release event is not counted for the unlock passkey, so it doesn't matter what's the mapping reported. At some point, the HAT events have been discarded as valid input from the passcode matching (here) and this causes your issue.
For a Dualshock controller (like yours) unlocking works using one of the joysticks, but not the D-Pad (which is a HAT type input).
@deodekabokat If you're on the command line, you can use mc (maybe you're familiar with the Norton Commander/Dos Navigator/etc. interface) and navigate around the filesystem.
Otherwise, you can copy the file on the ROMs folder and look at it over file shares
Does anyone know if there is there any resolution to getting ALL of the buttons on this controller to work in ES? I'm disappointed that all of the buttons cannot be used. Originally I was attempting the macOS pairing and nothing would work (I read somewhere this is the best setting for retroarch. Cannot cite my current source because I forgot).
After two weeks of trial and error, I'm happier after reading this thread that I can use the Windows setting, but I often use the trigger buttons for load and save states (the shoulders are for ff and rewind). So full functionality is reduced for me.
@mitu I see. I understand. Thank you for the help. I will see if i can find an alternative to NESPi case. Well, the biggest reason i got it was because of the Safe Shutdown script. Pressing a button to turn off the console is neat, so i can prevent any corruptions to the SD Card.
@vladulkom If you have a problem please open a new topic with details of your set-up. The issue above was related to vram - but this thread is 11 months old.
Thanks Mitu for link, seems they have MOVED custom setting number from 22 to 23.
Well know one of the tasks I will need to do over Christmas holidays, cfg file updates :/
