no keyboard output

[Mollymoments]

Current behavior

the program sees the controller inputs as shown at the top, but will not output anything. tested with multiple programs.

Steps to reproduce the behavior

(to install)

1. unzip file
2. add .exe file as program to steam
3. use protontricks to install .NET dependency
4. run program under protonGE10-15

(to run)

1. select from steam VR menu

it runs pretty well except for no detectable keyboard output

Expected behavior

expect it to trigger the output assigned to specific controller button (e.g. L18 -> 1)

Operating system version

Fedora 42 (Bazzite) Linux

SteamVR version

2.13

Application version

v2.1.1

Application location

/home/USER/Games/openVR2Key/OpenVR2Key_v2.1.1/

VR HMD

Quest 2 - connected through ALVR

VR hardware

Quest 2 - connected through ALVR

Software to control

Soundux - Sound Board

Game

VRchat

Additional information

No response

[BOLL7708]

I have to confess that I've not bumped into anyone running this through Proton before this, not that I can recall in any case. I have no idea if the library I use for keyboard emulation would also work on Linux, if all the key codes are a match, etc. I would imagine it would be fine, but your report here indicates the opposite. I'm afraid I don't have much assistance to provide for this.

[Mollymoments]

to make it weirder, turns out the keyboard output works WITHIN the application but not outside of it. linux vr is still pretty fresh but hopefully with the steam frame better tools will become available

[BOLL7708]

Within... you mean when an application has focus? That's how this is supposed to work. It was made to trigger global hotkeys originally, it's not simulating sending the keys to any specific application window. Whatever has focus will receive the input, or as mentioned, any global hotkeys in other applications.

[Mollymoments]

moreso if you set L18 to 1, then select L19 and press L18, it will put 1 into the box - while not being able to output anything when other programs are selected

[BOLL7708]

Right, so possibly the application is sandboxed by Proton. Here you have more experience than me, is this something it does? It might be that keyboard simulation does not pass out of that layer into the desktop environment. I'm only guessing at this point though.