@tzium

These are the soldering s you should check :
usb-solderings.jpg
See if there are no breakages in them.

If you only connect both your controller and keyboard, without other devices, do they work OK then ?

@dmmarti : Thank you for the hint, that was part of the solution that worked for me.

I did notice, that settings are not permanent and was in luck to find the entry „Update Input Remap File“ in the table „MANAGE REMAP FILES“.

@Floob : Thank you for the link to the documentation and mentioning necessary input_libretro_device_p3 settings.

In another libretro discussion I also found settings for _p1:

Input_libretro_device_p3 = „259“

Now I can also use my xbox controller.
For the „259“ setting, I couldn‘t find an explanation in the documentation. But now it works and I slowly start to understand what‘s necessary, to get other games running.

@ all : Many thanks for your instant support and helpful input!

@yserra Hmm, shoot. I wonder if I have a greater issue. I did as you instructed for the C64 and the keyboard is still having the same issues. FWIW, the same issue exists when I connect a straight up PC USB keyboard. I also notice the Scoll lock made no difference.. then again I test that after I edited the cfg, so maybe it doesn't work because I set it to "nul".

@UncleCatfish by the way I do know about the VILROS keyboard/ Pi case but it seems a little cheap for my liking. I'm wanting a real clickity clack retro typing experience :D

EDIT Solved I have disabled and removed the kbdrate service from sytemd. I have then recreated and enabled it again and I no longer get any errors and my U-HID works as desired.

Thank you very much again.

@mitu said in Set keyboard repeat delay:

That's because there's no such file, kbdrate is located at /sbin/kbdrate.

Thank you very much, I was trying to find the correct route, but there was no way.

Now the operation is as desired, the replay problem in the console and in the SDLPOP port has been solved. I have to test the rest.

The funny thing is that despite working, it still gives me an error at the start of kbdrate

● kbdrate.service - Keyboard repeat rate in tty. Loaded: loaded (/etc/systemd/system/kbdrate.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2022-08-04 19:17:26 CEST; 3min 0s ago Process: 456 ExecStart=/sbin/kbdrate --silent --delay 350 --rate 75 (code=exited, status=1/FAILURE) Main PID: 456 (code=exited, status=1/FAILURE) ago 04 19:17:25 retropie systemd[1]: Starting Keyboard repeat rate in tty.... ago 04 19:17:26 retropie systemd[1]: kbdrate.service: Main process exited, code=exited, status=1/FAILURE ago 04 19:17:26 retropie systemd[1]: kbdrate.service: Failed with result 'exit-code'. ago 04 19:17:26 retropie systemd[1]: Failed to start Keyboard repeat rate in tty..

It should already have these defaults:

Arrow keys = D-pad
ZXASQW = BAYXLR
RShift = Select
Enter = Start

You can add additional binds in /opt/retropie/configs/all/retroarch.cfg:

input_player1_b = "z" input_player1_a = "x" input_player1_y = "a" input_player1_x = "s" input_player1_start = "enter" input_player1_select = "rshift" input_player1_l = "q" input_player1_r = "w" input_player1_left = "left" input_player1_right = "right" input_player1_up = "up" input_player1_down = "down" # input_player1_l2 = # input_player1_r2 = # input_player1_l3 = # input_player1_r3 = # input_player1_l_x_plus = # input_player1_l_x_minus = # input_player1_l_y_plus = # input_player1_l_y_minus = # input_player1_r_x_plus = # input_player1_r_x_minus = # input_player1_r_y_plus = # input_player1_r_y_minus =

This works in conjunction with the gamepad. Right now I am playing Double Dragon (arcade, ddragonw.zip under lr-fbneo) using the d-pad to walk around and the keyboard to punch and kick.

@hawkes_84 It isn't too bad. I never had a ZX Spectrum back in the day (I'm from the US), and I also didn't have a computer to have the chance to play the old text-based adventure games. I'm playing this game because it is based off of the first book from my favorite author David Gemmell. I tried this game out via another emulator years ago but didn't really do much. Now, I've decided to play the game all the way through :).

Great, thanks 👍

I've opened a PR to help improve the consistency between the two input types: https://github.com/RetroPie/RetroPie-Setup/pull/3539

@mitu Interesting! Thank you very much for your feedback! I'll check how the library emulates the keyboard!

My fallback is a microcontroller to emulate the keyboard, if the software portion is too complex.

The gamepad configuration is fine, there must be something in the configuration for RetroArch that's not correct.
Can you run a game with verbose logging post the resulting log file (/dev/shm/runcommand.log) on pastebin.com ?

@niyoki said in lr-caprice32 select + start combo triggers 2 actions = Virtual Keyboard & Exit command?:

Hello,
On the Amstrad CPC Lr- caprice32 emulator: if I press gamepad select + start buttons combo, those are triggering two actions at the same time.
Emulator exiting back to the game selection screen on the emulationstation and virtual keyboard for before the emulator exiting.
Because of this behavior I can't use the virtual keyboard.

All the best
Niyazi

I changed above post, maybe know better to read.
All the best
Niyazi

@mitu Thanks for looking at it. I've opened an issue at Retroarch git, just in case

Self-answering...the solution, of course, is to turn on focus mode, something I'd never heard of before today. Live and learn. :)

@sirhenrythe5th Yes we can certainly see that with all the annoying “no retropie for raspberry pi 4 yet” posts that happened.

There's a virtual keyboard on my end when using Netplay, no physical keyboard needed.

I guess first try updating to the latest Retropie version along with Retroarch as well.

solved, thank you.

@mitu Sorry for the late response!

There were indeed no events when I tested with evtest.

I completely removed the keyboard again, rebooted and started Pixel. I again paired the keyboard, and made sure it worked in Pixel. Then I rebooted into ES again, again no keyboard..... some kind of weird inspiration made me go to the Retropie Config (you know, where the setup.sh is started) and, much to my surprise, I found that after a few button pushes the keyboard started working! I have no idea what went on and why it worked, because apart from opening setup I did nothing differently from the first time. After leaving the config I started evtest again (via the remote console) and actually this time around the events were showing up! The keyboard actually started to work!

Soooo happy now, as after adding the proper event source to the moonlight config I actually have full keyboard support there as well!!!

Thank you again for your help and patience @mitu !

@philcomm First off, I'm sorry that your OSK as originally engineered looks like it won't be accepted --- but I wanted to thank you for really moving the ball forward on this, because it looks like the python-based one will make it through as per recent comments on the PR. This is going to save a lot of people time and frustration and you should get a large chunk of the credit.

For fun last week as I was setting up my Zero2W I connected via SSH to it and attempted to enter Wifi via my phone using the existing infrastructure by executing RetroPie-Setup directly. Although in theory this seemed like a good idea, the WiFi won't drop and reconnect to a new network when you're using that connection for the terminal session, turns out. So, still very clunky.

Will check out your music suggestion, and also the new OSK coming down the pike. Thanks so much.

I think I might have found some quirks around the safe shutdown script with the Zero2W around pin allocation and interaction with WiFi but I want to do some more testing this week before making further topics or inquiries about it here. I also will share some additional script suggestions / observations too.

@markyb2021 nope, i have 4 8BitDo Pads running very well and had no problems at all, not with retropie 2 x, nor with 3.x or 4.7.
It is your setup, but as you are not able to answer specific questions we will never know what is wrong with it.