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

@mitu Thank you. This is exactly what I was looking for.

@LostnIL Are you using the image from retropie.org.uk/download or a 3rd party image ? RetroPie doesn't come with any overrides, did you save any input overrides from the RetroArch menu (RGUI) ?

@alrotem said in Joystick orientation swaps: I am pretty sure, this can be resolved by meddling with the configurations/scripts, but I suspect it would be too much work, and overkill, rather than take 10 minutes and just make sure one controller set is identical to the other. Not quite, since the names of the gamepads (P1/P2) are identical and the configuration file governing both is the same (it's created based on the device name). The approach suggested by @grant2258 is the correct one - there's just one configuration for both controllers, so making them work similarly is the best solution.

@Bluescreen2001 this can be done. I did it but it was many months ago now so I am somewhat rusty. First to back into the way you normally configure a controller in retropie (like when you boot up the first time) and reconfigure your controller to how you want it to operate in-game. Second, go to the command line, and use the js_test utility to figure out what button numbers your raspberry thinks your buttons are: type into the command line jstest /dev/input/js0 Then press your buttons and it should tell you which button number is assigned because when you it the button the appropriate number will say “on.” Write down a reference for yourself. Third, exit the jstest by pressing CTRL + C on your keyboard. Now you are going to edit the emulation station input config file to make new controls for navigating the emulation station menus. At the command line type sudo nano ~/.emulationstation/es_input.cfg that will allow you to change which buttons do what in the emulation station menus by using the button numbers you found and recorded in jstest. You will make button “a” the number button that you found was your start key, you will make button “b” the number button you found was your “stop” key and you will make the “start” button (which usually brings up the menu) the number button you found was your “coin” key. For the sake of still having use of the other buttons In concept you may want to then assign the “select” key to some other button since it will likely be assigned by default to your “coin” button. After you make your changes save the file and go back to emulation station by typing emulationstation in the command line and see if it works.

I don't think there ever was or will be native support for Minecraft Pi Edition. They stopped making updates to it years ago. :(

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

@w0rM Best to start your own topic and please also post this info: Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..) Power Supply used: (If using a Pi) RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used) USB Devices connected: Controller used: Error messages received: Log found in /dev/shm/runcommand.log (if relevant): Guide used: (Mention if you followed a guide) File: (File with issue - with FULL path) Emulator: (Name of emulator - if applicable) Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS) How to replicate the problem:

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.

@quicksilver said in PC Engine Controller Layout in Docs: Never seen that before 😄 It will probably be the only time

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.