Retroarch and Joypad problems (solved)
-
@mitu said in Retroarch and Joypad problems:
This would get you the same configuration file as the .dist one. Check your system's configuration file and make sure it's also reset to the defaults.
er, how can I do that?
-
Fortunately, you can "restore the factory settings" with the file /opt/retropie/configs/SYSTEM/retroarch.cfg.rp-dist. Just rename it to retroarch.cfg.
-
@mitu My factory settings have the same problem :(
-
Can you upload the
retroarch.cfg
files for the system you're trying on and the general one in/opt/retropie/config/all
to pastebin.com ?
Also, when launching the emulator, use the Runcommand launch menu and select "Launch with verbose logging" and also upload the/dev/shm/runcommand.log
file. -
@mitu said in Retroarch and Joypad problems:
Can you upload the retroarch.cfg files for the system you're trying on and the general one in /opt/retropie/config/all to pastebin.com ?
The general one in /opt/retropie/config/all: https://pastebin.com/A71RhzX4
and the runcommand.log: https://pastebin.com/Bqj24NGD
The snes retroarch.cfg (sorry): https://pastebin.com/YiYKEWHF -
Remove
/opt/retropie/config/all/retroarch.cfg
and then reinstall RetroArch from the RetroPie-Setup script, the problem is that the joystick auto-configuration folder is not set and the default (which you have updated with the online updater) has the default Libretro joypad profiles, which probably don't have a hotkey set.... [INFO] [udev]: Plugged pad: Wireless Controller (1356:2508) on port #0. [INFO] [udev]: Pad #0 (/dev/input/event5) supports force feedback. [INFO] [udev]: Pad #0 (/dev/input/event5) supports 16 force feedback effects. [INFO] [Autoconf]: 302 profiles found. ... [INFO] [autoconf]: selected configuration: /home/pi/.config/retroarch/autoconfig/udev/Sony-PlayStation4-DualShock4v2-Controller.cfg
-
@mitu Nothing. Still the same
-
Check the runcommand log file and see if your joypad configuration is loaded (Wireless Controller.cfg) and not the one from
/home/pi/.config/retroarch/autoconfig/udev/
. -
@mitu It's the wrong one
[INFO] [autoconf]: selected configuration: /home/pi/.config/retroarch/autoconfig/udev/Sony-PlayStation4-DualShock4v2-Controller.cfg
-
Try clearing up the
/home/pi/.config/retroarch/autoconfig/
folder and leave only the.cfg
files - you should have one for each one of your controllers. See if this time the right configuration is picked up. -
@mitu said in Retroarch and Joypad problems:
Try clearing up the
/home/pi/.config/retroarch/autoconfig/
my path is kinda different on my Pi folder. There is only "hascheevos", "RetroPie", "RetroPie-Extra" and "RetroPie-Setup".
How can I see this "/.config/"?
I'm using WinSCP, but can use Putty too. -
@CapNinja said in Retroarch and Joypad problems:
How can I see this "/.config/"?
This is part is for the people from future, people who probably did the same mistakes. To follow Mitu advice I needed to learn two things
I used Putty to see that folder, on there:
to delete files
rm myFile.txtto delete folders
rm -rf foldername/Now I need to thank this person who help lost souls like me.
Thank you very much @mitu my problem is solved. For learning reasons I just want to understand your line of thought, can you please explain to me? -
@CapNinja said in Retroarch and Joypad problems (solved):
Thank you very much @mitu my problem is solved. For learning reasons I just want to understand your line of thought, can you please explain to me?
You updated your auto-configuration profile from RetroArch, this downloaded the
.cfg
files from https://github.com/libretro/retroarch-joypad-autoconfig to the/home/pi/.config/retroarch/autoconfig/
folder. The same folder also holds the RetroPie generated gamepad configuration files, the difference between them is that the ones shipped by Libretro don't have a hotkey assigned.When starting, RetroArch prioritised loading the Libretro config file (this one) so deleting that file - along with the other profiles which might apply to your other controllers - will make RetroArch load the correct
.cfg
file - the one produced by the RetroPie scripts. -
@CapNinja said in Retroarch and Joypad problems (solved):
This is part is for the people from future, people who probably did the same mistakes. To follow Mitu advice I needed to learn two things
I used Putty to see that folder, on there:
to delete files
rm myFile.txtto delete folders
rm -rf foldername/For the you and others from the future: For such file operations, you can also start a text-based file manager by entering
mc
(Midnight Commander). Just mentioned as another option to the console commands and their simplistic might. 😌 -
@mitu suddenly my problem came back and said "THIS IS NOT EVEN MY FINAL FORM!".
I played with every control to test and it was fine yesterday, and today too. But was 1p games, and my kid wanted to play some Mickey game (that Mickey & Donald from snes). After choosing 2p suddenly the configuration was all wrong again.
Now my PS4 controller works fine, but the 2 8bitdo is all messed up.
And my shader options reset everytime, even with "core override" -
@CapNinja said in Retroarch and Joypad problems (solved):
Now my PS4 controller works fine, but the 2 8bitdo is all messed up.
Check if you have any extra auto-configuration configuration files for the 8bitdo in the auto-config folder.
And my shader options reset everytime, even with "core override"
Shaders pre-sets are not saved from the core overrides, but with the 'Save Shader pre-set' option from the 'Shaders' menu.
-
@mitu said in Retroarch and Joypad problems (solved):
Check if you have any extra auto-configuration configuration files for the 8bitdo in the auto-config folder.
I have one for each controller in that folder
@mitu said in Retroarch and Joypad problems (solved):
Shaders pre-sets are not saved from the core overrides, but with the 'Save Shader pre-set' option from the 'Shaders' menu.
It wasn't working properly (I've created a topic talking about it not much time ago) and override was a workaround to set it, but I've tried and it worked like it should.
-
Do you have any controller remapping set-up ? Maybe you've re-mapped the 2nd player controls ? Check the
/home/pi/.config/retroarch/config/retroarch/config/remaps/
folder and see if you've set any such re-mapping. -
@mitu no remaps
-
@CapNinja said in Retroarch and Joypad problems (solved):
It wasn't working properly (I've created a topic talking about it not much time ago) and override was a workaround to set it, but I've tried and it worked like it should.
This is the thread. Just for the record. :)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.