First, you should provide the information asked in https://retropie.org.uk/forum/topic/3/read-this-first.
Second, you might have stumbled upon the news Sony driver behavior in newer kernels, where the rumble appears as a separate device and messes up the controller numbering. See this topic for a workaround.

Bump?

Thank you so much, that solved it :)

@joserto86 Do you have a keyboard attached to the PI ? Please see the questions from https://retropie.org.uk/forum/topic/3/read-this-first and try to give some answers so we can better grasp your configuration.

@mitu I did it, but then suddenly my wi-fi dongle stopped working. Then I tried some more troubleshooting attempts for that and messed stuff up even more.

Much as it pains me, I'm just reinstalling RetroPie and doing it all from scratch. I made backups of everything, so hopefully I'll be able to salvage some of my customizations.

@caelthunderwing @Ecks Man, I really didn't want to have to flatten and reinstall because I'd already put a LOT of roms on this thing, but the Kintaro image appears to have been the problem, yup. Using the base one from the website solved the problem. Time to start moving the roms over again!

At this point I just have input lag to deal with, but that's a separate issue I'm going to have to look into and make a separate thread for if necessary. Thanks for your help!

Well, first you have a lot of addons installed that might be related to "piracy", I don't care about it, but that might cause problems, especially because many of them are done by people with little experience in coding and/or with malicious intents, be carefull about what you add to Kodi.
Second, you have a lot of errors (besides the ones from the addons I mentioned above) that Kodi cannot read or says that the file is read only:

1:43:30.972 T:1631396784 ERROR: SQL: [Textures13.db] Attempt to write a readonly database

This generally indicates that your system suffered file corruption, or most likely, your microSD card is broken or faulty.
This isn't easy to fix, and is impossible if your card is broken.
Try to move or delete your Kodi settings (/home/pi/.kodi) to start fresh with default settings.

Use @meleu's joystick selections script, it allows you to choose the (player) order of the joysticks per core/system. But if you're DragonRise controllers are always USB connected, they'll probably always be js0 and js1, so I guess you can use the RetroArch gui and choose that player1/2 and joysticks on 3rd and 4th position and save the the core remapping.
For N64 though, I think you'll need to edit the configuration file explicitly if you're using the standalone Mupen64 - more details are in the docs for the emulator.

@wihaedud

Hi. What did you reconfigure in RetroArch to solve your XBox One Controller problem? I think I have the same problem.

Thank you very much. I appreciate your offer pjft, I will let you know if I run into any difficulties :)

@mitu OK. I tried what you suggested and paired it with my Windows PC first. It paired right up without any issues. I then moved to the Pi. Before I started pairing with it again, I first removed the 8bitdo Bluetooth controller, updated to Retropie v 4.4 and then rebooted. This time it recognized it and paired up with it without issue but just like the first time I got it to successfully pair up, it didn't seem like any of the buttons would work when I went to configure them.

When I go back to check Registered/Connected Bluetooth Devices, it shows the Quadstick is registered and gives its MAC number but doesn't list it as active in active connections.

If it is registered and connected, and I'm trying to configure the inputs, should it not be active? Or does it not become active until after the inputs are set?

@mitu Yes, it is definitely connecting. As the Pi boots, the light blink, but then when it connects, it vibrates and goes solid.

@solomruby2018 3.6.0 is really an old version. Regarding the error message, starting a service requires administrative (root) privileges, so you need to prefix the command with sudo:

sudo systemctl start bluetooth

The current (4.4) version works for the 3B version, but since your running version it's quite old, I'm not so sure that an update of the RetroPie-Setup script would work. If you want to upgrade to the latest version, I'd recommend to save your data (configuration/ROMs/artwork) and to write the new image to the SD card.

@mitu Thank you, I will definitely look into this and test it out this weekend.

I apologize for not replying sooner, I have not been getting site notifications for some odd reason.

@mitu Thank you for your response. I've already seen those cases, however I cannot reproduce the same behaviour . The second like you posted does not help because I'm able to use the controller on ES. The first link I cannot really follow because when my Xbox controller AND the IPEGA controller are connected, both key mappings get really weird...

@mitu No, I did it but the behaviour is still the same, as the 8bitdo N30 pro (with the difference that it doesn’t have the TURBO button).

USB >> 8Bitdo NES30 Arcade
Bluetooth >> szmy-power Ltd.Joypad

@mitu said in 8bitdo dosent work in bluetooth mode:

@lesk You would pair it just like for a PC (Windows). Normally just press Start for 3 seconds and it will start to blink blue with one pulse. I'd suggest you reset the controller to the defaults, remove the BT pairing from RetroPie and start again using the PC mode and do the pairing and then reconfiguring in ES.

I did this. But still it does not work in any game. Only in Emulationstation as I stated before.

I tried one thing last night. While connected via bluetooth I went into config and then retroarch.
There I found user binding(or something like that under inputs) and I used my controller and rebind all the keys there, and pressed auto save config.
Aaaaaand I could use it in game! But the hotkeys dont work. I cant quit games, cant load save slots or change save slots. So im still puzzled.