@mitu

FYI, solved with help from the moonlight team.

https://github.com/moonlight-stream/moonlight-qt/issues/1563#issuecomment-2774382989

@sugarfree
Thanks!

@enjoilogic14 said in No gamepad detected - total newbie:

I am able to get to the configuration menu but it does not detect my wired controller nor my wired keyboard in any of the USB ports

Are the keyboard/controller not detected even if they are directly connected to the Pi's USB ports ? Are you using a proper power supply for the Pi ? Does it work if you connect just the keyboard directly to the Pi ?

@yctn said in no Gamepads Detected:

@mitu i found out that the start + home button will quit the emulation and return to th retropi menu when i am in a rom. this is nice cause i notice that the graphics of mupen64plus-glide64 are better then with the ir/libretro core.

/opt/retropie/config/all/autoconf.cfg

Mupen64plus_hotkey = "0"

!Turns off hotkey in N64 emulator only!

/opt/retropie/config/n64/inputAutocfg.ini

choose your button combination for exit/load/save

/opt/retropie/config/n64/mupen64plus.cfg

Find these options under [CoreEvents]

Joy mapping stop = "J0B10/B11" Joy mapping Load state "J0B10/B6" Joy mapping Save state "J0B10/B7"

This worked for my Wireless Xbox one controller, (usb-C wired is again different buttons).
I believe N64 8BitDo is J0B9/B12

Each controller type might have different button setup

Disclaimer: it will no longer adjust the hotkeys for other controllers for N64 as player 1. This is not flexible at all. If you want to change it, it must be done manually.

@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 Ok I have posted a issue.

https://github.com/jehervy/node-virtual-gamepads/issues/103

@Nash does xboxdrv have hotkeys, turbo, and toggle settings like antimicrox?

Made a post here: https://retropie.org.uk/forum/topic/35784/does-xboxdrv-have-hotkeys-turbo-and-toggle-settings-like-antimicrox

@Isolved: the solution of the problem was throw away 2.4 dongle and connect gamepad through standard pi Bluetooth - work fine

I want to bring up this topic again!

As I have noticed from experience, at SWITCH mode sn30pro + retropie could has much delay! And it's awful :(

So, in 2024 year, could someone tell how to get work sn30 at XINPUT mode? ( with both working Triggers and "hotkey" buttons)

@mitu said in RetroArch UI - Gamepad issue:

My advice would be to back-up your current retroarch.cfg and use the RetroPie default one (retroarch.cfg.rp-dist).

It works now. Thanks
The problem seems to be from the new retroarch.cfg file . With no retroarch.cfg file, it works well. When I reinstall retroarch, the new retroarch.cfg file create that problem. I don't know why? Probably, a new setting create that

NEW EDIT:
In the new retroarch.cfg I changed all_users_control_menu = "true" for "false"
and now everything is fine. That was the problem.! Don't know if other people got this issue, but on on my side, this solved the problem.

Thanks a lot for the support !

@mitu I tried the testing through gpionext testing 1 & 2 for each gamepad, all the buttons were picked up properly. I am still getting the same issue however. When I go to set up my gamepad, despite the fact it says 2 game pads detected, when I hold down a button to being set up, it comes up as keyboard.

@waterslip said in Unable to play 3 or 4 players on Emulation Station Arcade:

The menu's are the same and it was installed as per documentation.

No, they're not. Your screenshot show a heavily customized RetroPie installation - that's not what a default RetroPie configuration looks like (even with added games). You're clearly using a 3rd party image, for which - as @Ashpool mentioned - we don't offer support.

Issue with mame2003-plus has been corrected. For anyone following this, Update from source to receive the update.

that worked. THANKS!
yes it was 49686 for product id but i had a typo for vendor id, that's 1133 instead if 1133.

Thank you very much!

@vic-viper-001 Well, now I feel like a complete moron. All I needed to do was re-install LzDoom, and overwrite the new lzdoom.ini with my old one.
Everything works again like it's supposed to.

@roslof Ah OK, that was it! My version was just called "Bolo" and the crack was by Trystan II. Seemed to work fine except for the the joystick. When I tried the 4AM crack, it worked!

Thanks!