You can choose a hotkey enable button when you configure your gamepad and this will set it also in RetroArch so you can trigger an action with 2 button combos - see https://retropie.org.uk/docs/Controller-Configuration/#hotkey.
However, this is an emulator feature (RetroArch) and not a global/general input configuration option that will work in any program (including EmulationStation).

@mitu said in N64 Controller Setup - Inconsistent Documentation:

@busywait said in N64 Controller Setup - Inconsistent Documentation:

If you don't have a 'retropad A' button defined, of course it's not going to work in the menu . My remark was:

How the button is mapped to the underlying core doesn't matter for the menu (RGUI or otherwise).

I agree, but the reason that I don't have a retropad A button defined is because the core doesn't use it for it's logical function in the mapping. I could have had both [N64 "A" and RGUI "A"] if the core used different bindings.

Obviously this is a minority problem for people trying to use pads without the full set of retroarch inputs, and I can still navigate the RGUI using a keyboard in my case :)

@efriim said in Nintendo Switch Online, Super NES controller.:

I can get them to register/sync in Bluetooth but after I disconnect them I have to redo it in the Bluetooth menu to get them to sync again.

Not sure what you mean by 'disconnect them'. I usually just shutdown RetroPie / Emulation Station and the controllers go to sleep on their own.

I use Switch Pro controllers and mine will stay synced to my RetroPie install as long as I don't plug them into the Switch to charge them. Charging through the Switch will automatically re-pair the controller to the Switch and it won't talk to anything else without a manual re-pairing.

The controller/player number lights on the controller constantly array as if it is still syncing, or as if it can't assign the player number in the controller.

I don't have a solution but my Pro controllers do the same thing so it is somewhat normal for this style controller. I think you are right that the Switch must send information back to the controller to tell it which player number it is assigned and nothing in the RetroPie package will do that at this point.

https://github.com/pyhammond/retropie_wiimote_lights
This project was for Wii controllers but maybe it holds the answer and can be adapted.

If the PSX controller is P2, without any configuration, in order to switch controllers you should have:

input_player1_joypad_index = "1" input_player2_joypad_index = "0"

You can re-order the controllers also from the configuration editor configuration - it's one of the advanced options you can set.

Could find the solution on my own.

The correct syntax is J0B4/H0VX
where the "X" is set to be 1(up) 2(right) 4(down) or 8(left) depending on the direction.

@itsthex said in Controller Issues - Buttons Inop, Controls change:

I picked up a Vilros Pi 4 kit to use with VMAN's 512gb image. Consensus seems to be that one shouldn't use a prebuilt image, but I figured I couldn't go wrong with what was seemingly regarded as one of the best. And, so far so good!

We don't support 3rd party images. Ask the author(s) of the image for support, or use the image from retropie.org.uk/download.

@zantetusken10 I think the problem is joycond. I uninstalled it (manually deleting the files it installed + disabling the service) and now it works. The only quirk are the leds of the controller. For example, if I connect it with bluetooth the first time the first light will be on, if I disconnect and reconnect via bluetooth, the first + second light will be on like if it were player 2, but the controller will work fine nonetheless.

Now, to get it to pair properly with Steamlink :D

@jak75 Start reading the docs: https://retropie.org.uk/docs/Controller-Configuration/

@emulatre71 Oddly it has never happened before, but now again on a brand new install tonight. Tried the same trick and it worked there as well.

@holyheadshot said in Cannot map controls to IPAC:

Maybe another silly question but I've read other threads about emulation station configuring as gamepad vs keyboard. Would changing something like that help?

There's no explicit setting in EmulationStation for that, however there is one for the IPAC and it's referenced in the doc page I linked earlier.

@ohmycommodore Went with mode D instead of X and yes that does seem to eliminate the delay.

actually fixed it, with an entire reimage and 1st install again... dont know what happened. but thanks anyway..

@mitu Thanks for your reply! I ended up removing the cfg files for the arcade button mapping and re-did the process. Success!

Thanks again

@mabelwolf63 said in RetroPie USB Joystick setup:

What can I do to fix this?

Without an additional program that would combine both joysticks into one, there's no way around it. Something like moltengamepad or antimicroX (not sure if it will work for RetroPie on the Pi though).

Also a reminder that arcade games commonly shared a single set of controls, for example pacman. So player 2 actually uses player 1 inputs when it's their turn. There were also games that had distinct player controls such as tmnt or mortal kombat. It would help to specify the game your trying to play to determine if that plays any part in your issue.

I may have forgotten to mention but I've noticed that when doing a initial clean install of RetropIe 4.7 I noticed that with my 8BitDo controllers that there is a bug that does not allow me to configure the Right Trigger and Left Trigger . It does show up as a Xbox 360 controller, I had fixed that input by updating Retropie to current 4.7.11 and redoing the configuration.

In the meantime, hope someday we might get package versions of dosbox staging and disbox-X too, these seems to be eqally cool projects.

@mitu Hey there - so just a quick update, I've managed to get the stick working - but it took some effort!

Firstly, you have to the stick into PS3 mode before the emulation station interface will recognise it, even then - it won't appear on-screen as a controller (the UI remains blank as if no controller is plugged in)- but if you hold down a button on the stick - it is suddenly recognised as a Brook PS3 controller and then configuration / calibration can start.

Emulation station refuses to recognise the L2 or R2 buttons, but you can configure the rest.

However I have noticed that it is then possible to get these buttons recognised after if you manually configure inputs in RetroArch(?) interace (the one with the green pixellated text that you access from in-game) - then with lots of fiddling around you can finally get the Wireless Brook Board working as a retro pie controller (as a wired PS3 controller)

I will try jstest next

Sorry for not posting details on setup - it's a RP4, with offiical usb-c power supply, (but was testing on RP2 with usb power last night) but will get the rest of the details when I can

@dankcushions what is the best way to do the intial config? Set it up for LR-MUPEN, then customize the mupen64plus config file?