@Doran754 You can check from the command line by running tvservice -s It should show you something like the lines below pi@retropie:~ $ tvservice -s state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive You can set the resolution using Raspi-Config from the RetroPie system - https://www.techcoil.com/blog/how-to-change-screen-resolution-in-raspbian-stretch-with-raspi-config/.

@Amplifuzz said in Assign buttons to combos, to play 4 button games on 3 button setups: but now it doesn't appear anymore and I don't know if it's game-dependent or they removed it in un update from .43 to .44 As you've found out, it's something that's being removed, so there's no upstream support for this going forward.

Thanks everyone. i figured it out. Had to configure the buttons a little weird but now they work.

Hello. I have now used another sd card with a fresh new image. Did all updates as soon as I could, before configuring any inputs. It took about 3 hours and finished with some warnings on emulationstation. But nothing wild. I have then put a psx rom onto the pi and configured one ps1 controller via usb adapter and one ps4 controller via bluetooth. Everithing seems to work fine right now. I am going to add the n64 controllers and some more cores. But for now: Thank you very much @mitu for your support.

So what you are saying is that I need to hookup the buttons on each controller so that they are the same value. IE button 1 for each controller is ''A''. I never had this problem before but will just rewire my board to make sure they match. Thanks for the help

Deleting retroarch.cfg and renaming the other one didn't help. I reinstalled RetroPie with the same image. Installed plugin https://github.com/meleu/RetroPie-joystick-selection. In it I've set detect by name and set Logitech to player1 and Redragon to player2. It worked for player1 in lr-pcsx-rearmed. Not for player2. It is a problem with Redragon gamepad I think. In plugin I've deleted 2nd gamepad and Logitech now works in all my cores and all my games and in RetroArch menu. But when I've tried games the very first time, I had only one gamepad (Logitech) and keyboard plugged. And they didn't work in games. I think it's the problem in RetroArch, that it decides on its own what controller to use for player. And you can't configure it easily. That plugin is a good solution with detect by name option, it sets the corresponding device for the corresponding player as you want it, not as RetroArch wants it. But to be sure I need to test it with normal gamepad for player2, not Redragon one.

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