Controller not working in certain retroarch cores

NullValue

Oh sorry about that I meant retroarch.cfg. Anyways I'm using a raspberry pi 3 model b with retropie 4.4. As I have stated I'm mainly using a duelshock 4. I'll get the log and update you on the results. And I also think i enabled save on exit globally.

NullValue

@mitu okay so I've attempted to enable verbose logging on genesis but it cant save because no input works including the keyboard. so I can't exit out of retroarch properly and the log isn't saved.

mitu

Remove the keyboard and leave only the gamepad, then try again.

NullValue

@mitu okay so I disconnected everything but as soon as I did that I opened picodrive with verbose logging and my controller was low on battery so it disconnected but when it reconnected it worked fine.
Anyways here's the pastebin:
https://Pastebin.com/47Mf41Je

mitu

@nullvalue Well, if it worked fine, then there's no error to see in the logs :(. However, I see you enabled 'Save Config on Exit' for the megadrive system. I'd advise to not do it, it's usually the cause of controller errors like this (i.e. controller works fine in ES, but it's not working in RetroARch). Revert retroarch.cfg in the megadrive config folder to the default setting and see if this fixes the problem.
If you wish to save configurations for the MegaDrive use the 'Save Game/Core Override' menu item - https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping.

NullValue

@mitu thanks a ton for the help however the error still persists even after save on exit being disabled. This issue only effects my duelshock as after setting up my xbox controller it works fine. So when I have my duelshock on boot up it doesn't work but when it gets reconnected it works great. So now I'm hoping to fix that issue.

mitu

@nullvalue said in Controller not working in certain retroarch cores:

thanks a ton for the help however the error still persists even after save on exit being disabled

You also need to revert the config file to the default content, it's not enough to disable the setting. This is what the default content looks like for /opt/retropie/configs/megadrive/retroarch.cfg:

# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

input_remapping_directory = "/opt/retropie/configs/megadrive/"

#include "/opt/retropie/configs/all/retroarch.cfg"

NullValue

@mitu I did that and it and the problem still persists.

mitu

@nullvalue So, the controller works with other cores, but not for the Mega Drive core(s) ? Do you have any other controller connected while you're testing this ?

NullValue

@mitu yes I have an xbox 360 wired controller which works great on all cores. The problem only comes when I use my wireless duelshock 4 with Bluetooth which has this bug when i use Mega Drive and PS1 games. This persists on all mega drive cores as well. I should probably mention that my Nintendo cores work great without any issue.

mitu

@nullvalue said in Controller not working in certain retroarch cores:

This persists on all mega drive cores as well.

Looks like a configuration problem. If the controller works with the other cores, but not on the MD cores, then the hardware is ok (OS wise), but the configuration doesn't get applied. I'd start with an freshly installed image (if you have another SD card) and try to test there.

NullValue

@mitu I don't have another sd card so is there another option for testing.

mitu

@nullvalue said in Controller not working in certain retroarch cores:

I don't have another sd card so is there another option for testing.

Re-install RetroPie ? Take a backup of your existing image, write the 4.4 image on the card, update everything (OS + RetroPie), re-configure your controllers and then try to see if the error still occurs.

NullValue

@mitu okay that will take a while, is there any way to reset all controllers in all systems so the controller mapping would be fresh.

mitu

@nullvalue Yes, you can try resetting them from the Emulationstation package. You might also try to move out of the way the global retroarch.cfg file and re-install the RetroArch package.

NullValue

@mitu I fixed the issue! I knew that the issue was coming from the retroarch.cfg in the gen/ps1 system and snes worked fine so by using that retroarch.cfg it worked great! Thanks for the help on figuring that out.