Just navigate to the folders containing the cores. Long story short: autoconfiguration works, hotplug works, DPad, buttons work. Configs -> sd:/retroarch/config (Set the route in order to save Configuration) Cores -> sd:/apps/retroarch (This is where you have placed your cores. (please note the valid options, it's sdl instead of the used sdl2!) (spice in the story that even the two gamepads have different button values for some buttons also - in retroarch input config screen)įinally I edited the retroarch.cfg file, entering sdl2: This is the reason for not working buttons. Using the input configuration in retroarch, it prints different values for the buttons (A is 11, B is 12, etc.). also would like to configure more controllers for multiplayer gameplay (they. Jstest /dev/input/js prints for button A, B -> 0, 1 etc., same values as configured in the controller's config file in /opt/retropie/configs/all/retroarch-joypads/Gamepad.cfg file. How to configure a N64 USB Controller in RetroArch for N64 games. In lr games (SNES, NES, GBA, etc.) the navigation works, buttons don't. To access the Emulator, you can go in the Retrobat System in the System View. Hardcoded Configurations - made by editing retroarch.cfg file (s) Core Input Remapping - an easy way to do specific control configurations for specific cores, made in the RetroArch RGUI. AutoInitcfgOLD.ini rather than delete them, so you can get them back. There are 3 main ways to configure input for RetroArch: Autoconfigurations - made in EmulationStation. Same issue here with retroPie v4.4, and with 2pcs of cheap (~10 USD) chinese bluetooth controllers.Ĭonfigured properly with EmulationStation. With AUTOCONFIGURE CONTROLLERS set to OFF, you need to configure your controllers directly in the Emulator. Safest way is to just go into the folder where they are and rename them e.g.
0 Comments
Leave a Reply. |