Unfortunately after loading a game it is as if it was unmapped, although going manually into the quick menu settings shows the controller still mapped. I would assume that it would, and when RetroArch is opened it is exactly what happens, the gamepad gets immediately recognized after pressing any button, it works fine, all buttons do. V1.2.2 does NOT have this issue, it seems to start in the next v1.3.0 (Feb 25 2016) along with the implementation of the new material design menu, lasting to this day (although possibly only affecting marginal number of hardware/controllers), hence the short amount of complaints and attention to this issue. I also tested as far back as v1.2.2 (Jul 19 2015) Anyone has any idea why this happens?ĮDIT: workaround here: Controller works in menu, stops working after loading game I’ve tried saving the autoconfig file too, but it makes no difference at all… works until a game is loaded and I’m back to unplugging/plugging back. So far the only thing that works is unplugging/plugging back the usb gamepad and pressing any button, then I get the bottom-left notification message about it being detected again and it starts working within the game and RetroArch menus. The USB gamepad is recognized upon opening RetroArch, I’ve been able to map all the keys properly, the issue is after loading a game the gamepad does nothing as if it had been disconnected, not even if I return to the RetroArch menu (the gamepad is still responsive to the OS). I’m using a generic USB gamepad with OTG connection.
0 Comments
Leave a Reply. |