@Tom_Neverwinter Could you share what you found?

Thanks that fixed it :)

Also now have a fresh install of 4.4 up and running beautifully.

Autofire switch was broken. Now it's ok!

I have now reinstalled the official image on the Pi3B+; did an upgrade (no rpi-update), rebooted. The buttons then didn't work anymore. I then updated Retropie to 4.4.4., rebooted and all is working again. Thanks for your help.

@grimmey said in Stuck in controller configuration screen:

E: Unable to locate package libcur14-openss1-dev

libcurl4-openssl-dev is in the default Raspbian repositories, so it should be found, but are you connected to the internet ?
Regarding the command prompt commands, what commands have you tried ? jstest is in the normal $PATH and should be available by default in RetroPie's image.

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

@eddie72 said in Cannot get my zero delay controls to work on my newly built bartop HELP!!!!:

My raspberry does not do this
It takes me straight to the emulators and retroarch screen

This sounds like you are not booting into a clean image from this site? How did you write the image? What is the name of the image?

the joystick and buttons are all connected to the circuit board and then into the pie via the Ian connection

LAN connection???

@kdragon_2 RetroPie is just Raspbian Linux underneath, so as long as your setup works with Raspbian and the OS detects your setup as a controller, RetroPie should recognise it and use it. As for the how to communicate with it, that's up to you - Linux/RetroPie already includes a few drivers that interpret GPIO inputs as a controller - look in the Docs.

@mitu Hi ! Thanks, indeed you are right, I used lr-pcsx_rearmed, the default one, and so I read and followed the documentation you sent to me and I solved my problem.
Thanks for your help !

@kane72 Ok I have tried that, switched to 4.3 and then attempt to launch and the Pi completely disconnects form the TV at that moment. I dunno. I'm ready to give up on this. I have made two posts and a great amount of time researching the internet for solutions with little responses either informing me that most people either just don't know or don't want to del with me on this. It is evident that some things are simple and self explanatory and other issues are much more complex and probably require an advanced knowledge of tech. I'm not sure if I would give my kids one of these things but on the flipside I have enjoyed learning the other aspects of the Pi. I will probably end up starting with a fresh copy of Retropie as all this screwing around has either erased files I have uploaded or change settings that I do not know how to fix. I do really appreciate your response .

ive hit this as well and was confused. i see auto stuff and explicit buttons, so its confusing. I checked the input bindings and saw some map to auto and some map to explicit buttons, so i'm assuming this means it depends on the input settings--this mostly works but ive found a few situations where it isn't working, so im not sure.

This is exactly what I was looking for and it worked, thanks a lot!

@dudleydes I realized that I had disabled controller 2 and 3 and when enabling them mouse is now also enabled by default.

By default mine was set to;
CONTROLLER_MOUSE_1=mouse
CONTROLLER_MOUSE_2=joy2

The one on Amiberry github is set to;
CONTROLLER_MOUSE_1=joy1
CONTROLLER_MOUSE_2=joy2

I had to set Mouse to my joypad (wireless ps4 joypad) to my mouseport, and also declare to Amiberry that its a mouse.

@mitu said in Issue configuring PowerA Fusion wired XBox One controller:

@AdamBeGood You should have opened a new topic instead of bumping 2 years old topics.

I'm sorry, I should have started a new topic and referenced this thread. Apologies.

Let me know if I am okay to carry on posting here now, or if the best route is to still open a new topic.

Your issue is probably caused by the usage of rpi-update, which overwrote the xpad driver with the stock Linux kernel version. As explained throughout the topic, RetroPie includes a patched version, which modifies the default driver behavior and maps the triggers as buttons instead of axis.
Don't use rpi-update as a regular update mechanism - it's not intended to be used as such. RetroPie uses dkms to install additional Linux kernel drivers, so that any normal Linux kernel update (via apt) will automatically re-install the drivers. When using rpi-update, this is not possible and causes issues if you rely on a certain driver to be installed and working.

I wouldn't normally use rpi-update but I wanted to try out the KMS change to see how that affected N64 emulation.

Any idea how I resolve this issue now? I looked at amending the line mentioned in the thread but that line doesn't seem to be present in my script, and there is a reference to the trigger issue also so I think the script has been updated since the above was written.

dkms install -m xpad -v 0.4 -k "$kernel" dkms install --force -m xpad -v 0.4 -k "$kernel"

I tried re-installing xpad from Source but that hasn't changed anything.

The below line is also present in "xpad.conf"

options xpad triggers_to_buttons=1

My controller is connected by a USB lead, I'm not using Bluetooth.

Later Edit: it is especially strange as it is only my Elite Controller that is having this issue. Standard XBox One Controller is perfect.

@mcsteve

Assuming your controller has enough buttons to support all of the N64 buttons, all of those buttons are available by default if you configured all of the buttons on your controller during the initial gamepad detection. If you need to reconfigure it I recommend resetting your controller configuration in the Retropie system menu->Retropie Setup so that it prompts you again.

I went through controller setup again. This time I made the XBox button my Hotkey. Now I can start games by pressing Start and Right Trigger and I can exit a game to the main menu by pressing XBox button and Start. The Start button by itself, however, does nothing.

I should mention that the Start button works by itself flawlessly as you would expect from within Emulation Station to bring up the main menu. It's only within the actual games themselves that I have to use the weird Start/Right Trigger combination.

Any ideas?

@g6delta No problem, I hope it solved your problem

@colombia20102018 Try: https://retropie.org.uk/docs/Xin-Mo-Controller/

I wasn't sure about that line as it looked to do the same thing, however when I pulled the lines from the main retroarch.cfg file, both lines were there so I put them both in "just in case."
Could be that the core looks at one line and retroarch looks at another, or that some lines found else-ware look for the other string.