Configuring the keyboard in ES doesn't mean you can't use it as a keyboard in the emulators. Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first and specify which emulators have you tried and didn't work.

@mitu Thanks for your reply. I'll give it a try.

@jordanhuckaby

Update if anyone is looking for a solution:

I confirm I now have a working solution to play Backyard Football 2-Player using two built-in joysticks.

Since lr-scummvm already recognized the first joystick as a mouse, I left player 1/joystick 1 untouched. My problem was with joystick 2; ScummVM would not recognize this as a keyboard, and thus Player 2 could not control anything.

I used xboxdrv to configure the second joystick as a keyboard when ScummVM is used. This was done by editing the runcommand-onstart file, as outlined here: https://retropie.org.uk/docs/Universal-Controller-Calibration-%26-Mapping-Using-xboxdrv/. Since Backyard Football only needs the keyboard directional keys and the right-control button, I only mapped these (joystick as the directional keys, and a cabinet button as right-control). Once ScummVM closes, this virtual keyboard gets eliminated through the use of the runcommand-onend file (again, in the doc linked above).

After doing this, a notification would appear when opening ScummVM mentioning that an X-Box Keyboard Emulator has not been configured. This was a positive sign because it shows that the virtual keyboard was being created by opening ScummVM. Unfortunately, Player 2 still was not configured to use this keyboard.

The final step was then editing the retroarch.config file for ScummVM. I first had to map Player 2 to use the new virtual keyboard, which was done by pointing to the new joystick number (2 in my case). I also had to re-do the B=right-control mapping in retroarch that was done in the runcommand-onstart file.

After doing this, Player 2's movements were being registered in ScummVM. Strangely, Player 2's movements were also moving the mouse cursor (Player 1). The final step was to tell the retroarch.config file that player 1 should not have any keyboard functionality. I did this by manually mapping each directional key and right-control to "nul" for player 1, similar to the following: input_player1_up = "nul". Now, moving joystick 1 controls player 1 (mouse), and joystick 2 controls player 2 (keyboard, via xboxdrv).

Good luck!

Hey it WORKED!

~/.config/openbox/autostart

gnome-terminal --full-screen --hide-menubar -- bash /home/pi/autostart.sh

and
~/autostart.sh (chmod +x)

#!/usr/bin/env bash kodi-standalone sleep 2 emulationstation

So on boot, Kodi launches. On first Kodi exit, the script will launch ES. From then on, ES does what it does when launching Kodi and returning to itself on exit.

Thanks for your help @mitu!

@gogoretro yes. In general:

For an snes labeled controller, alter labels for x-box

Keyboard keys = controller buttons

Arrows = direction buttons
Z = B
X = A
A = Y
S = W
Q = L1
W = R1
Etc

@fruitybit said in Keyboards no longer work:

@mitu @BuZz
I may have exceeded the maximum ‘user error’ level of stupidity here.

Yeah, they promised to limit that variable to a bearable value in a future update of this universe fork, but I slowly begin to lose any confidence that they'll deliver that in my lifetime.

@oofiskoo Did you come up with a solution to this? I appear to be having the same issue.

I figured it out - key is to map the controls in the native emulator (in this case RPCS3) using a keyboard. Then, when playing on the pi via the Steam Link, everything worked great. What a fantastic addition!

Many thanks for your advice @BuZz. I modified the startup script as you mentioned and it still works.

My understanding is that BasiliskII should ever load the 'keycodes' file so the host keyboard layout (the one configured in Raspbian/RetroPie, here) is taken into account, whatever international layout it is. Without the 'keycodes' file, only US-layout would be recognized and typing from another host keyboard layout (i.e French AZERTY, German QWERTZ...) under Basilisk would produce weird result. If I understand well, the keycodes file contains the USB keycode for any environment BasiliskII has been built for (so, the Linux framebuffer, here).

By the way, loading or not this keycodes files every time BasiliskII starts is not necessarily the most important point. With your permission, I would rather suggest that there is something to fix somewhere, since BasiliskII doesn't open this file when it is told to do so from its basiliskii.cfg config file.

@mitu Thank you all for your help as always!

Thanks for your reply mitu! I want to configure advmame with joypad (I have all controls except analog sticks and this I want) for this reason I cant access to "tab" menu (only if use keyboard plug) but I cant plug to cm3 the usb keyboard for this reason I think the solution is virtual keyboard.....but if I cant do this....I search other options ^^'' Thanks for your reply! (If I only play with GP430 I done but If I want the limit of the GP430 I can only try, mod & fix =) )Thanks again!

@mitu Thanks! :Banghead: Now that was a typical case of "Betriebsblindheit" (1) inmidst my current setup orgy - Sigh. Should have also tried 'em without the bindings 1st. !

[1]: I never came along a real translation for that, but Target fixation or Tunnel vision (metaphor) may come close to it.

Turn 'Game focus' on in RetroArch by pressing Scroll Lock, this way RetroArch will not interpret the keys as gamepad actions/hotkeys. To exit the game, you'll need to press again Scroll Lock to activate RetroArch's keys back (so Esc would exit).

We don't support 3rd party images - image your sd card with the image from retropie.org.uk/download. We don't know how the sdcard you purchased was configured or pre-installed with RetroPie.

@mitu This was it! I have a script that controls an LED light/Power button on my case, (as well as shows heat/fan speed, etc) and it seems that the new update doesn't like it. If I delete the python line, the retropie command line and the RetroPie UI work as expected. Not sure what the conflict is, but it's clearly to do with the script on my end.

Below is the autostart.sh if you're curios. Thanks so much for your help!

python /home/pi/scripts/picontrol/picontrol.py&
emulationstation