elite-vr-cockpit
elite-vr-cockpit copied to clipboard
dantman
"Could Not Send Keypress" Log Error
Minor bug, I noticed that Elite VR Cockpit doesn't recognize some key presses. My personal experience was with the period and comma keys (which I had bound to open galaxy/system map).
Pressing the overlay button for galaxy/system map outputted the following error in log: "Could not send keypress Key_Period / Key_Comma, did not understand one or more of the keys."
@dantman issue is still there. I have some keys binded to comma, period and numpad and they all don't work
I had this issue with the FSS button, Key_Apostrophe wasn't understood. I found a workaround.
Find the key binding in Elite Dangerous and change it to something else on your keyboard. It can be anything, including multiple keys (to a maximum of 4 keypresses). For me I changed the FSS mode button from ' (apostrophe) to Q + W + E. As soon as you save the binding it should work.
Found the solution from this post https://github.com/dantman/elite-vr-cockpit/issues/198 and a quote from dantman himself "You do not make bindings for holographic buttons. Holographic buttons read your Custom.3.0.binds file, look up the keyboard binding assigned to the action they use, and then send those keypresses to ED."
When you encounter that error I'd like to know, what the key binding is in the error/ED controls file (Key_Apostrophe in this case) and what number you get when you press that same key on this page https://keycode.info/.
When you encounter that error I'd like to know, what the key binding is in the error/ED controls file (
Key_Apostrophein this case) and what number you get when you press that same key on this page https://keycode.info/.
Not totally sure what you're looking for in the error/ED controls file but I'll dump some info for you.
This is what I got from the Keycode webpage when I pressed the apostrophe key on my keyboard ( ' )
That key was bound to the enter FSS Mode command in ED. As far as I'm aware, my inputs didn't make it past EVRC and the "could not send keypress" log error in the desktop view.
Hope that helps!
That key was bound to the enter FSS Mode command in ED. As far as I'm aware, my inputs didn't make it past EVRC and the "could not send keypress" log error in the desktop view.
That's as expected. I have to manually map each and every one of ED's Key_* to a VirtualKeyCode.* but special characters aren't as easy to map as stuff like VirtualKeyCode.VK_A.
It appears that Key_Apostrophe may be VirtualKeyCode.OEM_7 and I'll have to manually add a mapping for that later when I'm able to work on the overlay again.