Configure input for individual emulators?

Libretro Lakka
#1

Hello all, I thank you in advance for your time and I apologize for being an absolute noob when it comes to my knowledge of this very cool distro that I installed for the first time this morning. After playing a little with RetroPi for a little while on my RaspberryPi for an NES case mod that I would doing for funzies, I became interested in Lakka and decided to install it onto an old netbook that I no longer had plans for. After completing the installation I had very little trouble getting up and going by throwing some roms onto the device through the Samba shares, however I’ve run into an issue that has gotten me a little frustrated. I’ve noticed that the controller input scheme that I have set up for the rig only works well for certain game systems and can seem mixed up on others. To put it in other words, the A button in one game might seem right bound to a specific button on my controller on one system, but might seem wrong on a different console. I remember running into this issue on RetroPi but there were input config files that a user could edit to change input schemes for each emulator if they wanted or needed to that would run as you launched a game from that specific system. Does Lakka have this functionality? I assumed that it did, since they are both built off of Retroarch, but I’m probably misunderstanding.

Again I apologize if this is common knowledge and or explained clearly somewhere. I’m assuming that there is a folder of config files that I haven’t been able to locate.

Perhaps a better question for me is to ask if there is a good place to learn about the configuration of the individual emulators? As I am also having issues getting mupen64plus to run - I’m assuming that it is a configuration issue, but I don’t quite know where to look for that yet.

In any case, thanks again for any advice or links that anyone is willing to share with me.

#2

You can edit the retroarch.cfg file in /storage/.config/retroarch or you can temporarily change over to the RGUI menu and map your buttons and then switch back to the Lakka/XMB menu. There’s an option (maybe only accessible from RGUI) to enable ‘core-specific configs’ which will let you use different button mapping–and other options, too, such as decorative overlays–on a per-core basis.

#3

Hello hunterk, thank you for your reply. I found the per core configuration option that you touched on in the RGUI and was pretty excited to see that the system generated some new config files for me to play with. I was able to manually rebind my keys for the SNES emulator by editing the SNES config file. Now when I run SNES games the buttons function as I would expect. Unfortunately however it seems to create a new problem for me - after I close down the emulator the SNES control configuration seems to stay in effect, which then messes up the RGUI controls until I run a different emulator. To put it another way, the controls seem fine when I first start Lakka, and again are fine when I run SNES, but then are messed up again once I leave it (since they are still set to SNES keybindings and no longer the global ones).

I hope this makes sense. I’ve checked the retroarch.cfg file before and after seeing this behavior and it looks like the SNES control scheme is actually being written into the global retroarch.cfg when I run any SNES games. I then have to go back and rebind the global keys to get the control scheme that I want again.

Am I missing something? Should I be putting the global control scheme into a different config file? Maybe this core-options config that I see here?

Thank you again for your time.

#4

Ah, yeah, when you have binds in the core-specific configs, it will indeed change the mapping in menus, as well. There’s a new feature you can use in very recent builds (dunno if it’s made it into the version you’re using or not) where you can re-assign the retropad buttons in the core options (core remapping or something, I think it’s called). This will let you change how the buttons function in the core without changing the menu mapping.

#5

Ah I see, thank you much for that info. I’ll look into compiling a newer build to see if that is what I am looking for. Thanks again for your help.

#6

You can also wait for a future release, when we will update the version of RetroArch in Lakka, you will be able to use the per core input remapping feature.