![]() ![]() Long story short: autoconfiguration works, hotplug works, DPad, buttons work. (please note the valid options, it's sdl instead of the used sdl2!) The main difference in the configuration files with respect to keyboard controllers is the lack of btn in the mapping. (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: RetroArchs use of these configuration files is described in detail here with references to gamepad/joystick controllers. ![]() ![]() This Citra should now store all of its config, save files and such inside of this. Just navigate to the folders containing the cores. Yes, you can configure your controller directly through the GUI in. This is the reason for not working buttons. Configs -> sd:/retroarch/config (Set the route in order to save Configuration) Cores -> sd:/apps/retroarch (This is where you have placed your cores. Using the input configuration in retroarch, it prints different values for the buttons (A is 11, B is 12, etc.). 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. See edit next: Edit: I realize merely saying to switch A and B for the NES controller is too vague. In lr games (SNES, NES, GBA, etc.) the navigation works, buttons don't. Same issue here with retroPie v4.4, and with 2pcs of cheap (~10 USD) chinese bluetooth controllers.Ĭonfigured properly with EmulationStation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |