@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.

@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 :)

Thank you for your answer. Actually I played a bit with retroarch.cfg, with someof the controllers pluged in in differents usb port and it seems to work now ! Not exactly sure what really made it work though :)

@mitu

great, many thanks!

@mitu Thanks! I forgot, that individual controller settings can be done by the quick menu. I set it to "---" now an it works.

The hotkey enable button, being RetroArch specific, is part of the joypad auto-configuration profiles saved in /opt/retropie/configs/all/retroarch/autoconfig.

Hey! Thanks to you guys and the other linked posts, I found and fixed the same issue. I had some old overrides saved and sure enough, my Multitaps were "auto". Changed to "disabled" and all is well again in PSX land!

@mitu FANTASTIC !!!!
Everythings working with lr-fmsx!!! I focused to much on Lr-BlueMSX. For Lr-BlueMSX, It's only playable with keyboard . The joypad working only for Coleco. Not enough gamepad buttons are associated with basics keyboard fonctions. They should enable the "RetroPad Keyboard Map - Joypad - Awaiting description" option in Control menu in RetroArch for MSX.
Thank you
REGARDS

@kevin55605 Thanks for sharing your findings.

@Dj-EKI If you'd like that combo to open the menu, then open RetroArch from the RetroPie system in EmulationStation, set the option and then save your configuration.
To leave a game, you'll have to use either a Hotkey + Start - which you don't want - or disable the Hotkey and choose another button for the exit hotkey. Pressing that button will automatically exit the game.

@Dj-EKI map z to left trigger I believe

@mitu Yes, on Windows it works normally. Anyway, thanks for your help. I'll try to find more information all over google.

@mitu one success for us. The edition on that .cfg worked. One interesting thing I've noticed is: every value was 11 more than normal.
If my select button value is 10, on that .cfg he was 21.
If my B button value is 4, there was 15.

On a side note, I've used @Clyde "mc" tip and man, it saved at least 1h of my time.

Again, guys. Thanks for your time, for your effort, for your attention and for caring and sharing your knowledge with us.
I request now my promotion to Private 1st Class Noob.

In the end, I connected a mouse to play Arkanoid in lr-mame2003, and it worked from the off. Xbox 360 controller just too baggy and too huge a deadzone to make it playable. Thanks for advice though.

I have the same awful controller. It tries to detect the device that it's connected to and select mode based on that. If the system is running Windows it will switch to Xbox mode.

I'm still not sure how exactly to switch mode, but last I got I working by holding select+analog. But I also found this on a sellers website:
"press the "home" button for 7 seconds, you can freely switch the mode."

Linux actually seams able to use the gamepad in all 3 modes (it also has an Android mode), but the device sometimes won't fully register before switching the mode a couple of times.

Found driver, installed it, connected pad. All good. Thanks @mitu

@MajorDangerNine lr-vice has a virtual keyboard and you can control the mouse with your controller. Lr-bluemsx works. Msx does have some games that require some keyboard keys. Linapple works but there might be some games that require a keyboard press. Not sure though. After setting up controls you can play a ton of games in dosbox without a controller. Thats the extent of my computer gaming systems.

@theretroprince said in Xbox One Blue Tooth Joy-Pad Connection Problem:

@lip9571 The udev rules are an option that you can automatically set in RetroPie-setup. They just write a line of configuration to your bluetooth rules. It is not enabled by default. As long as you haven't enabled them, you don't need to concern yourself with them. If you have enabled it, you can disable it within the Bluetooth setup in RetroPie-Setup.

Thanks for the reply. I got it all working in the end all I need to do was re bind the buttons for Bluetooth in retro arch and it worked perfect