The temperature (31 C) seems fine - I don't think that's the problem. Does this happen when the you're configuring the input in EmulationStation, after the first boot ?

@meleu , what do you think? Would it be possible to add something like that to your script?

@Halvhjearne That's the thing I didn't want to do, but... So I saved all the data from my Pi, formatted the USB key, and installed a fresh version of retroPie: I was able to configure the controller. Then I updated the system and RetroPie, tried again to configure the controller: it worked this time again. I restored all the games now, and it's still working. I don't know what was the problem, but now it's gone Thank you all

Many thanks for the info on evdev. I thought it wasn't being used since evdev-joystick --l doesn't show anything, but the gamepad was being assigned to /dev/input/eventX I ended up using this solution: https://joaorb64.github.io/2018/02/14/Configuring-a-Nintendo-Switch-Pro-Controller-on-Linux.html

Thanks, somehow I missed it.

Please add more information about your system - https://retropie.org.uk/forum/topic/3/read-this-first, including the model of the controller (maybe also a product page). Can you test your controller from the command line (exit Emulationstation with F4) by running jstest /dev/input/js0 ? If the controller is detected, it should detect when you press the buttons/d-pad/joystick.

@hushkin Instead of re-flashing you could just reset the controller configuration and start over with it. You can reset them from the emulationstation package in the RetroPie-Setup script. After that, ES should prompt you to re-configure them again. Try starting with the problematic controller and see who it behaves.

Update: For the 4-Player Xtension the IPAC2 runs players 1 and 3 (and left click) and the MiniPac runs players 2 and 4 (and right click and trackball). I tried both the new 1.50a firmware (on the IPAC2 only, it doesn't support MiniPac) and the 1.39 firmware on both the IPAC2 and MiniPAC and configuring as gamepads. Even though all the connections looks programmed properly, it was very inconsistent for what actually worked as a gamepad. It was about 40% working. I may have made some missteps. I have gone back to default for both IPAC2 and MiniPAC in my 4-Player Xtension. For others with the 4-Player Xtension who want to be able to get back to default configuration for the IPAC2 and MiniPAC, here are the files: https://drive.google.com/drive/folders/1qpPneE7E88_qc65JXOPq6gZYvpD1Ubki?usp=sharing

@mitu said in SNES Start button not working, USB controller: @kamban Can you try to remap one of your controller from RetroArch - does Select + X bring up the RetroArch Gui ? Yes, GUI shows up. I checked the controls and see Auto: 8 (N/A), (Key:rs... Select as well as the other mapped keys. Also tried another SNES rom, same here. I really have no idea why the select is not working...

Thanks for this info, glad you brought this up, got it running thanks. I can use my virtual keyboard to type on my desktop now :)

@benniebax Bind the Player 3 keys if your controller says is the 3rd

Hi, I just tried that, it has the same effect.

I don't know how to help but I would recommend that you try lr-vice. It's considered experimental but it works fine for me and benefits from RetroArch's control and shader goodness.

@mitu okay, cool I'll give that a shot. Cheers.

@mediamogul thank you, I will try them

@gtoilet if you mean the configure a controller screen, the info you want is in the docs: https://retropie.org.uk/docs/RetroArch-Configuration/ Scroll down to the bit where it shows the controllers and what each button on them corresponds to in retroarch. That'll show you what to map each N64 button as. Anything else you don't have on the 64 pad, hold any button on the controller to skip it.

@mitu thank you, I appreciate the information. sorry, i skimmed the read first, must've not been paying attention.