@sleve_mcdichael yep! I missed out that it actually is printed out on the board and it booted up when I powered on the wrong input i.e. power in on the USB-port. But there's no USB I/O on the power inlet port. Low-level-mistake, caused me some googling hahaha

@Chronicomos Post the details requested so that further help can be offered.

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

Are you controllers connected via USB ? If so, do other USB devices work - it might be an USB connector problem. I assume you tried to configure the (new) USB controller in EmulationStation and this is where it's not working ?

@ElrasM said in False controller inputs:

But nevertheless any suggestions for my problem?

First, xboxdrv should not be installed unless you really know how to use it. It's not a real device driver, but emulates an Xbox compatible controller. The xpad is usually used for X360/Xbox controllers. If that doesn't work, then it means you're encountering the same issue.

Is there any chance that there is a seperate file for controller input detection in ES?

The configuration for EmulationStation's input is in \\retropie\configs\all\emulationstation\es_input.cfg. You can verify there that your input is mapped correctly and there are no button overlaps.

You can also start EmulationStation with the --debug flag and it will log the inputs pressed.

Try to see if it's happening on other systems also. Can you upload your retroarch.cfg (from /opt/retropie/configs/all/retroarch.cfg) to pastebin.com ?

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

@psytron said in Raspbian Buster - retropi install on os - retropi crashes when turn controller off.:

I should have pulled the latest before running the script

Support for Buster (and the Pi4) has been slowly been tested on the development branch, which recently was merged to the main repository. There still might be some quirks, but you should be able to install from binaries (without re-compiling).

@jcthrity3 Anyone? Beuler? Beuler?

@Sebiohazard Please add more info about your system - https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu said in Controller only works on menu:

@X_Splinter This looks like a power issue - starting a game would increase the power draw and possibly reset/disconnect your wireless chip and the USB ports. Are you sure you're using a proper power source ? Are you using a case ?

Yes, what an idiot I swaped the power supply and didnt even notice, now it's late I'll try tomorrow with official power supply.

I hope thats the issue, it got to be it's only the thing that changed... the same happens when I open retroarch, also the system only shows the pop-up that a controller was disconnected when I reconnect it which is strange

I'll confirm tomorrow. Thanks

@yorks361 Each line is one command to execute in the order they are listed.

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

Please don't post multiple posts on the same issue.

You have already asked this here: https://retropie.org.uk/forum/topic/15510/newbie-with-no-tech-skills-needing-help-controller-and-multidisc

@danielmewhouse said in "B" turns to "X" on second controller after restart:

@notechskill said in "B" turns to "X" on second controller after restart:

@danielmewhouse just to be clear. On my keyboard hit f4 and go to the command prompt and type in exactly what you have typed out there?

If your problem is on EmulationStation, use "sudo nano /home/pi/.emulationstation/es_input.cfg" to edit the file. You'll need to find the X and B buttons on the config file and swap the id value.

i could be wrong, but sudo shouldn't be necessary when editing files in one's own home directory

@Farmer-Ted I would be very interested in knowing if you found a solution to this. I am in the process of building my own and would like to use controllers that are USB like you are.

Any info you could provide would be great! Thanks for your help.

@duggeryskull this solution works for me although the Cdown remains unassigned. Do you leave RIGHT ANALOG DOWN (which is Cdown) -NOT DEFINED-? That's an issue I have not been able to find a solution for so far... Cheers

How did you solve this? I have the same problem with C down unassigned. Any help would be highly appreciated, thank you. :-)

@epd For the most part, yes. You need to add your ROMs, and set up your controllers, but other than that, should be good to go!

Still looking for some help :D

Thank you for the reply. I'm using the Pi supply.

The controller works on the pc for my emulators great. So not sure what the issue is here.

I have ordered a snes one from PiHut now. See how that goes.

Once again thanks for the reply.