Describe the bug
I use two overlay applications, OVR Advanced Settigns and openvr-widgets. Whichever of those two tools I launch first, that one works just fine. The second overlay application I start will not receive inputs though (OVR AS is mainly receiving double presses on the A buttons, while openvr-widgets received double tap on grip and single click on trigger button).
To Reproduce
Steps to reproduce the behavior:
Start OVR-AS
Start openwr-widgets
Try to trigger openwr-widgets overlay with double-tap on right grip.
Nothings happens
Expected behavior
The openvr-widgets overlay should appear.
System Information (please complete the following information):
Additional context
I already noticed this bug a few months back in the beta branch. I thought it was just a bug with in the beta which would eventually be fixed, so I switched to the stable branch. Since the SteamVR 1.17 stable update, I now experience this issue on the stable branch.
I didn't note down back then on which exact version this bug was introduced. I'm wondering if there's some way I can roll SteamVR back to version 16 for now?
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.
Describe the bug
I use two overlay applications, OVR Advanced Settigns and openvr-widgets. Whichever of those two tools I launch first, that one works just fine. The second overlay application I start will not receive inputs though (OVR AS is mainly receiving double presses on the A buttons, while openvr-widgets received double tap on grip and single click on trigger button).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The openvr-widgets overlay should appear.
System Information (please complete the following information):
Additional context
I already noticed this bug a few months back in the beta branch. I thought it was just a bug with in the beta which would eventually be fixed, so I switched to the stable branch. Since the SteamVR 1.17 stable update, I now experience this issue on the stable branch.
I didn't note down back then on which exact version this bug was introduced. I'm wondering if there's some way I can roll SteamVR back to version 16 for now?
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.