@mitu Pi Model or other hardware: RPi 4 B+ Power Supply used: (If using a Pi) RetroPie Version Used 4.6.6 version USB Devices connected: none Controller used: ps4 replica sorry I'm late with this. Could this bluetooth connection problem be connected to the recent hack?

Welcome to this forum. Please provide more information about your setup: all the information that's asked for in https://retropie.org.uk/forum/topic/3/read-this-first What do you mean by "not the same"? Are the control settings different or gone? Does the effect happen in Emulation Station (the frontend where you choose the games) and/or in the games themselves? What kind of "a few things" did you try? edit: typo

@mitu a huge thank you! It works like a charm!

@mitu Alright thank you so much, I've discovered that the reason that my control only worked on Spider-Man was because that game supported Dualshock and not all ps1 games support Dualshock. What happened is when I went into the options menu, I had the pad type originally on standard and moved it to Dualshock, not all ps1 games are compatible with Dualshock and are only playable through Standard pad type. Thanks for the article @mitu I really appreciate it homie ❤.

After not being able to find an answer anywhere I decided to reformat the sd card and do a fresh install with a nespi+ case that I was using before and the same os 4.5.1 and 3b+ pi. I have however run into the following issues. I have just recently had to reformat and reinstall retropie 4.5.1 on my 3b+ with nespi+ case. Installed the image and the safe shutdown script but for some reason the power button isn't working on the case. If I push it in to turn on the case nothing happens but if I push it again to make it come out the pi boots up but there is of course no power light. The pi won't power off with the button and the reset button seems to not work at all. I am not sure why this is happening as its a fresh install and previous to the reformatting the case and buttons installed and worked without issue. Any help would be appreciated.

@jackpage43088 https://retropie.org.uk/forum/topic/3/read-this-first You're welcome here but please install RetroPie from our site. We can't (nor want to) support a modification of our software provided by someone else. It's against the licenses of software included in RetroPie for it to be sold or included with a commercial product. Rpi4 support is still being worked on. It's not officially supported yet and many/most of the images out there are hacks also and don't implement things correctly.

@treebo88 said in Controller and core help: One wrong click and you have a world of problems lol... As @mitu said, it depends, and most problems can be reset just by editing or deleting the resp. config file. One thing I do like about Linux (since late 2006 in my case) is that plain text config files are the norm – many of which will be just recreated with default values if deleted – and thus, don't require a particular tool to edit them. Just an onlooker's two cents. I wish you success and fun in your journey to a new operating system. :)

Well, the usual troubleshooting steps are start with the RetroPie image from retropie.org.uk/download. It's a tested and mostly stock Raspbian image and the best baseline system to start experimenting. make sure you have an adequate power supply and you don't get any under-voltage warnings. test if the device is detected by the OS by running a few command line utilities # see what USB devices are connected with lsusb # see what input devices are detected by the OS and what kind (gamepad/keyboard/mouse/etc.) cat /proc/bus/input/devices test if the device inputs are registered in the system by running a few joystick/gamepad testing programs fromt the command line that capture the button/joypad/d-pad presses and show them on the terminal: # 1st joystick jstest /dev/input/js0 # 2nd joystick jstest /dev/input/js1 # another testing utility evtest

...

@zmb187 Please add more information about your system as asked in https://retropie.org.uk/forum/topic/3/read-this-first. What controller types ? Are you supplying enough power to the PI with a proper power source ?

@mitu I finally tracked down the issue. When the triggers on the controller were initially set the left triggers release was set as the right triggers pull. The system was registering a constant trigger pull and mucking everything up. Thank you for your help though.

@europadecas Despite my arcade, electronics, Linux, and coding experience I found Retropie to be a very complex and difficult to manage project. Kudos to the devs for integrating this many emulators into a single environment, and kudos to the support forum here for the help!

@johnodon said in What buttons should I press? A controller cheat sheet: @chipsnblip said in What buttons should I press? A controller cheat sheet: https://github.com/RetroPie/RetroPie-Setup/wiki/runcommand#adding-custom-launching-images You can also set how much time this will be displayed before launching the game. What would be a nice option is if you could set it to stay onscreen until a button is pushed. I don't think this is available today. John pressing q or escape on the keyboard will close the image and launch the game, then you can set image_delay to a high number of seconds. the only thing left to do would be map one of those 2 keys to your controller, but i'm unsure if this would require any changes to the scripts in ~/RetroPie-Setup/scriptmodules/supplementary/runcommand/

gotcha. let me refresh ans use that image. thanks for the feedback.

@colty250 Your problem is not a common occurrence, so there's must be some configuration that's not correct. Please provide the information asked in order to be able to diagnose it.

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

@stoney66 Thanks for the advice. I've got a config for /opt/retropie/configs/all/retroarch-joypads/USB\ Gamepad\ .cfg that looks reasonable, but still nothing is working. I have remapped them all repeatedly, and still no love. Any other ideas?

@columbo Yes, you can.