@jasonmadeapie How do you change the controls ? When you open the controls menu (for P1), you have on the left the button on your RetroPad (your controller) and on the right the emulated buttons. Use Left/Right to change the values on the right, cycling between the possible buttons that the system accepts. Go back in game and test the buttons, then once you're set, just save a Core or Content Remap from the Controls menu.

Please add some some info about your system and emulator used, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Well i can F4 out of it, and outside of RetroPie it works fine, same with the controller, but if i try to configure any kind of device as a controller in RetroPie it has that problem.

I got a USB Hat on the pi and thats how i connect USB and ethernet to it. it got power LEDs for each of the inputs and nothing seems out of the ordinary with it when entering into EmulationStation, so i doubt that the Hat is the cause of the issue.

@Crush I haven't tried that.

That depends. First and foremost, it's a secure behaviour to only give yourself administrator rights (e.g. via sudo) when absolutely necessary. Also, if you happen to change the file's owner or permissions by accident in a way that the normal user can't access them anymore, it can cause further problems.

In short, by training yourself to use sudo only when necessary you avoid future problems and, at worst, security holes.

In your particular case, mere editing an existing file shouldn't make you any trouble, but if the file doesn't exist, you'll create it with the owner root instead of pi. Because a new file will be created with only write permissions for the owner, any application like an emulator that's run by pi wouldn't be able to write to this file afterwards.

Again, that may or may not be a problem depending on the file, but avoiding to use sudo will negate this uncertainty alltogether.

Mitu- ok. That makes a lot of sense. Thanks.

David

@killerpoke said in Configure controller emulation station:

How can i change that controller configuration pops up every start when no controller is connected ?

Connect a keyboard and configure it as a controller, then disconnect it. You sholdn't be prompted to configure your input on start, even if you don't have a controller connected.

@lostless Thanks for all. Yesterday I bought two controls and for now they work, I have not been able to test them much. In time I will see how it works.

@tspgallagher said in Brand new Pi4 2GB, controller works in Estation, not in actual games:

I just have to figure out how to get OUT of a game once I get into one.

Hotkey + start

@barbosa22 there was an update to lr-PCsx where it seems it now emulates a standard, analog, or DualShock controller. If you originally setup to use and analog controller, Change it to DualShock. Also some games require it to be set to standard, especially older games. Ran Into this a week ago where Medal of Honor would not work after starting a game.

Hey, @mitu, here is the photo that came up with the USB devices. .

As to P1/P2 controllers, I configured only P1 and that did the trick for both.

As I'm writing this I realized my mistake and am horribly embarrassed! I just realized that "X" refers to button "X" and not keyboard "X". I reset my controls again to see which is "X" (I think in terms of Buttons A, B, C, etc.), and now I've been able to get into the menu and reconfigure. Problem solved. I really appreciate all the help!

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