No particular error shows up in the logs, the 360 is detected but not initialized as a gamepad though. Nothing comes to mind on what's going on.
You may want to post in the Steamlink forums (https://steamcommunity.com/app/353380/discussions/0/) and post the link to your log there also. If any of the controller works by itself, then it's not a config issue and usually in situation like this I'd check if there's enough power for both the WiFi and USB at the time, but since they already work (simultaneously) outside Steamlink that can't be it.

@mitu That worked! Thank you!

@mitu I ran an update last night and the issue of the in-game menu causing the controller to become unresponsive until the select button is pressed has been fixed. I can now pull up the menu, take screenshots, save states, and return to the game without any problems.

The issue with running the setup from within the RetroPie OS still remains. The workaround is to sudo ./retropie_setup.sh from the terminal.

Can you run the following commands and post the output here in the topic ? If xpad is not recognizing the gamepad, we can try and force the driver to load is we know the device's Vendor and Product Ids

lsusb cat /proc/bus/input/devices

@sugarfree thanks! Good to know there is a way to do this from the terminal window. I ended up following the instructions from this video to reset the emulation station input configuration for the controllers.

@mitu Thanks guys - I'll give it whirl

@mitu
I ended up having to do a full re-install of Mint Mate 22 for other reasons. This is my third install in the past 2 weeks and I hope I do not need to do so again.

Let it be known that even after a fresh full-reinstall of Mint Mate 22, the same lack of joypad recognition continues. I have to access the setup through terminal via the sudo command in order to make it work. Otherwise, accessing the setup through the Retropie OS itself does not enable joypad function in Mint Mate 22. I did not have this issue with Mint Mate 20.

@ScOULaris You may want to add the solution to your reddit post.

Get a ROM to test the gamepad - like https://www.psx-place.com/resources/padtest.396/ for PS1 - and run it under RetroArch to test your inputs.

EDIT: outside am emulator, you can use the jstest utility to test the connection/input response with your controller. You'll have to exit EmulationStation and run it from the command line like so:

jstest /dev/input/js0

To finish the test and get back to EmulationStation, use Ctrl+C (this will close the jstest session) and type emulationstation (+ enter) to start EmulationStation again.

@mitu Cool, thank you for looking into this, and I look forward to the release that will resolve this!

@willelind said in GPIOnext input works great during menu but stops working after game boots:

What did you mean by that? It seems that my input keybindings are from the /opt/retropie/configs/all/retroarch.cfg file, listed under keyboard, not joypad/gamepad.

Look in a verbose log and see if an additional joystick/gamepad input type is detected. It may be that GPIONext adds an additional gamepad device, even if you configure it as a keyboard.

@mitu hey! sorry, school started so I've been busy. here's the requested info:
Raspberry Pi 4 Model B Rev 1.5
RetroPie 4.8.8
Installed from the SD image on the website
All that's connected rn is the one dragonrise controller
I get a not configured error message from retroarch

About the config files, I was the one who mistakenly deleted them after trying to fix different control issues (it was a long night and at that point every button except select was unresponsive). I might try going from retropie-setup and seeing if that works?

there's a chance I disabled autoconfiguration, but I have no clue how I did that or how I would turn it back on. I definitely did not mess w es_input.cfg though, I never touched the es folder anyways.

I'll get back to you if the reset via retropie_setup helps, I didn't know that was a thing at all. thank you for your help :)

Did you try following the steps from https://retropie.org.uk/docs/Controller-Configuration/ ?

@sleve_mcdichael That worked! If I hold down select, now any of the quick menu hotkeys open the menu. Hey, I can go with that! Cool, then that's problem solved!

@vorvy
Do you have any update on this? I am currently trying to make the same controller work, but I am not having much luck.

I think thats exactly it, many thanks!

@CobraDesign47 said in Retroarch no Core installer:

. Could someone help?

RetroPie doesn't have a 'standard' RetroArch installation w.r.t. cores. Cores are managed manually from RetroPie setup and they're automatically set to be started depending on the system where the ROM/game is located. You don't need to start RetroArch and then open a core/content like you'd normalluy do on a bare RetroArch installation, instead you launch the game/ROM directly from EmulationStation.

As for the original question - did you configure your keyboard in EmulationStation - as an input/controller ? It should automatically configure the keyboard for RetroArch also.

By default, configuring the keyboard from EmulationStation will configure it as P1, if you wish to make the keybord work as P2, then you'll need to manually modify the retroarch.cfg configuration file for RetroArch and replace the player # in the bindings, i.e.

input_player1_a="X" input_player1_b="Y" ... #etc

with

input_player2_a="X" input_player2_b="Y" # and so forth

Is the controller configuration saved in /opt/retropie/configs/all/retroarch-joypads ? Do you see a .cfg flie there for the controller ? If yes, can you post the contents of the file surrounded by code tags here, in the topic ?

@zipino82 Could you please provide more info about your problem? If you're using a keyboard, just remember F2 saves your state and F4 loads it.