VR-on-Linux VS openvr

What headset do you have? VR works great when it works, but the protocols on Linux don't play well with all headsets. If you have a Vive, Vive Pro, or Index, it should work well with SteamVR. Otherwise, you'll have to dig around and test yourself using something like OpenHMD or more likely Monado, which both have limited device support. In my search, I came across this page, which might help you out.

As a rare VR on Linux user, SteamVR for Linux is in a sad state and I wouldn't recommend it to anyone who's not extremely dedicated. The fact that it exists at all is a step up from other vendors but man is it a bad experience right now. Worse than it's been since the earliest days IMO

Yep. Here's a relatively out-of-date list: https://gitlab.com/vr-on-linux/VR-on-Linux/-/tree/master/Proton

They are untested but should work, they use Valve's firmware. I reached out to the developers about it a while ago for this document.

Also, check out /r/virtualreality_linux and: https://gitlab.com/vr-on-linux/VR-on-Linux

I've removed it from the list.

Aside from the smaller list of native/supported games, here's what I've found has been tested to work.

I have been using C++ for a while but never really touched on using a full on SDK and now I want to use this SDK from Valve but my issue is that it isn't clear to me how to use it. What I mean by this is that it comes with a lot of subdirectories and extra stuff but how can I make a hello world program and able to call functions from the header file included in this SDK? I have used .h files before so I understand how the linker and all that works but with such a robust SDK I am not getting how this works on VSCode or maybe that I shouldn't even be using VSCode?

1) I considered switching a while back, but I was already really far in by the time I realized that OpenVR was outdated. If you search for SteamVR, OpenVR comes up as the API to use, and the github site does not mention it being deprecated anywhere. It's generally not obvious unless you are specifically searching for confirmation of obsolescence. In any case, my question is API agnostic.

OpenVR is open to anybody writing a driver to support their equipment there. Anybody can do it. Always has been. Citation, for my point: https://github.com/ValveSoftware/openvr

This is awesome! I requested something similar back in 2019 (https://github.com/ValveSoftware/openvr/issues/1262) but Valve never delivered.