@90sgamer Please provide all of the information that's asked for in https://retropie.org.uk/forum/topic/3/read-this-first.

@zappyowl2482 those instructions are correct and current for official retropie. we do not install third party builds like those on twister os.

@jamrom2 I did, but that doesn’t give me the option of choosing keyboard keys when I go to the config.

The Xbox controller has been causing me some problems in the past. If your 8bitdo gamepad is set on x-input mode it might act in the same way as a regular Xbox controller.

I'm not 100% if your issue matches the symptoms I had encountered myself, but consider checking this post. There is a solution at the end that.fixed the problem for me.

https://retropie.org.uk/forum/topic/26623/ppsspp-mapping-problem-wireless-xbox-controller/14?_=1619570216264

@yfzdude great many thanks

@yfzdude and @dankcushions , thank you for joining the discussion, and glad to have someone who is familiar w/this controller... geez I can't believe all this time that I didn't realize that the Logitech logo was a button as well(!!). I may have to do that controller test again to see what it comes up as, because somehow I missed it even there. So fortunately, I was able to assign it as the HotKey button, although it didn't actually show up the first couple of times I pressed it, which isn't entirely reassuring, but it seems to be working now.

So that said, I may wanna look into getting different controllers moving forward (including possibly that Dualshock that you mentioned), but for the moment this seems to get the job done and pause the game as I'd originally hoped, so yeah, doesn't look like I may wanna return this controller as I'd feared.

But yeah, re: that weird "Mode" button, you're right, it DOES seem to alternate you btwn/enable and disable the cross-shaped directional controls and the thumbstick one, and there'd been a few times during games when one control didn't seem to be working (when I'd pressed Mode without realizing it), and had to switch to the other directional option. Usually I'd end up just resetting the game to get it back to normal, but glad to know now what the purpose of it is.

I have the same controller and it isn't even recognised when it's plugged in. :(

@shonee That SD card is probably set up in a way that nobody can possibly predict and therefore support cannot be offered according to the guidelines shown in https://retropie.org.uk/forum/topic/3/read-this-first
Only the creator can help you with it.

The best thing to do is install retropie from the official image and follow the first install guide. All your controllers will be autodetected.

Reset your controller configuration and re-configure it again in EmulationStation.

@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