From what I've seen, loading bindings in general on Linux is very slow. I've had some luck getting them to work for the Half-Life: VR mod, but eventually the "legacy" bindings menu slows to the point of not working.
SteamVR Beta, Solus Linux, Proton 5.0-6
Bindings are screwy on my machine as well.
Ryzen 9 3900X
Device: AMD Radeon VII (VEGA20, DRM 3.36.0, 5.6.0-1-amd64, LLVM 9.0.1) (0x66af)
Mesa Version: 19.3.3
SteamVR installed on Samsung 970 Evo in /opt/steamapps/
Linux 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 GNU/Linux
SteamVR Beta 1.12.4
Manually updated to latest Linux firmware from 05-19-2020
Steam controller bindings are very slow. This is due to #307 .
My workaround currently is to launch the GUI without the controllers enabled.
There also a file in the SteamVR folder that needs to be deleted. I cant remember the name atm, ill add it later.
I don't have my Steam Controller connected at all-- It is in the carrying case. Only Index + Controllers and Vive Trackers.
After some more messing with it, it is workable as long as you're OK waiting 5 minutes for each button press to react.
I was talking about the index controllers, start SteamVR without them powered on.
As far as the file you have to delete its SteamVR/resources/config/legacy_bindings_generic_hmd.json
This file is read by steam multiple times per second which kills the vrserver performance.
This seems to be improved in the latest Beta 1.13.5.
I was able to use the "Legacy Bindings UI" with very minimal lag
proton 5.0-6x1 2020-04
Describe the bug
The following "Loading" message never disappears when using the SteamVR controller bindings UI for any Proton apps, tested with HL: Alyx and VRChat.
And in HL: Alyx, I cannot seem to proceed beyond the initial "press trigger to start" screen.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Controller settings are available.
System Information (please complete the following information):
Additional context
Note that I am running on Sway with a patched version of wlroots, sway, and Xwayland to enable direct display mode on Wayland. I would be surprised if this were causing input issues, but nevertheless the applicable patches are here:
https://github.com/swaywm/sway/pull/4289
https://github.com/swaywm/wlroots/pull/1730
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/248
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.