Keyboard not working in any game

[m33ts4k0z]

@mitu

I tried to do that but I receive an error now when I compile retroarch from source. Here is the log.

[mitu]

@m33ts4k0z said in Keyboard not working in any game:

I tried to do that but I receive an error now when I compile retroarch from source. Here is the log.

This looks like a Github problem to clone the repository for joypad-autoconfig, try again later on.

[m33ts4k0z]

@mitu

It looks like something happens right after the joypad-autoconfig gets cloned. I commented it and the same error occrus right after the libretro-core is cloned. But I can't seem to find the source of this since this error seems to come from the runCmd function that its never called after that?

[mitu]

@m33ts4k0z said in Keyboard not working in any game:

But I can't seem to find the source of this since this error seems to come from the runCmd function that its never called after that?

Not sure what part is called, but I can't reproduce the error. Since it worked before, did you change anything after the initial installation that might make the install fail ?

[m33ts4k0z]

@mitu

Ok I figured it out. The error was that the /opt/retropie/configs/all/retroarch/shaders directory wasn't empty and the git pull was aborting. Maybe you can add a git reset --hard or something similar there? Because the .git directory existed in there.

About the initial issue, I got the keyboard working now but still it looks like the keys that I assigned through emulationstation are not used? Instead the default Retroarch keys are used (z x c v)

I believe I have to delete some more cfg files in order for emulation station to recreate them.

[mitu]

@m33ts4k0z said in Keyboard not working in any game:

Maybe you can add a git reset --hard or something similar there? Because the .git directory existed in there.

It's because the shaders repos are different on a PC than on a Pi. Even if reset is used, it wouldn't work.

I believe I have to delete some more cfg files in order for emulation station to recreate them.

You may have overrides or saved configis in each system's folder that trumps the main config file.
EDIT: if you used reset or save configuration from RetroArch's menu, that's likely the case. Not something we recommend.

[m33ts4k0z]

No actually I haven't touched any Retroarch settings.

For example, for arcade, my retroach.cfg looks like this:

# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

input_remapping_directory = "/opt/retropie/configs/arcade"

#include "/opt/retropie/configs/all/retroarch.cfg"

It looks like fb-neo and mame have totally different key bidnings for some reason although they both use the same cfg:

lr-fbneo = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg %ROM%"
lr-fbneo-neocd = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --subsystem neocd --config /opt/retropie/configs/arcade/retroarch.cfg %ROM%"
lr-mame2003 = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003/mame2003_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg %ROM%"
default = "lr-mame2003"
lr-mame = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame/mamearcade_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg %ROM%"
lr-flycast = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-flycast/flycast_libretro.so </dev/null --config /opt/retropie/configs/arcade/retroarch.cfg %ROM%"

[mitu]

@m33ts4k0z said in Keyboard not working in any game:

It looks like fb-neo and mame have totally different key bidnings for some reason although they both use the same cfg:

Hm, for mame2003 - not from what I've experienced so far - do you have an example where the bindings are 'totally different' ? Excluding any remaps/overrides, just the OOB configuration.

[m33ts4k0z]

@mitu

I tried cadillacs and dinosaurs using fb-neo and lr-mame-2003 and the keys where different. However I'm sure the issue is somewhere with the configs I copied. I have no overrides anywhere but how could I be sure that I have no overrides when a load the game?

[mitu]

@m33ts4k0z said in Keyboard not working in any game:

I have no overrides anywhere but how could I be sure that I have no overrides when a load the game?

Usually the loading of overrides is printed by RetroArch on start, unless disabled. Mame2003 can also be differently configured through the MAME menu, which trumps the input configuration from RetroArch - see https://retropie.org.uk/docs/lr-mame2003/#mame-menu.

[m33ts4k0z]

@mitu

Yes indeed retroarch says that the config is saved to /opt/retropie/configs/arcade/retroarch.cfg when it starts? I suppose the issue is a setting that overrides retropie, right?

[m33ts4k0z]

Issues solved.

The problem was that emulationstation didn't have permission to right to /opt/retropie/configs/all. All keybidnings are working fine now.