ALVR VS openvr

Otherwise, there are some tricks out there that allow you to run games through SteamOS via ALVR: https://github.com/JackD83/ALVR . I haven't gone through with this approach but I've heard success stories. Getting this to plug n play out of the box isn't really going to happen. So depends on how badly you'd like this to work. Realistically, better to stick to the Quest 2 standalone.

if you're here looking for a cracked version of Virtual Desktop, there isn't one. VD is uncrackable as far as I know. If you want a PCVR streamer for Quest, here is a free alternative.

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.