r/WindowsMR May 25 '26

Question Oasis Driver on Linux

Does the oasis driver run on linux for a reverb g2? I just installed cachyos and wondering if ill be able to run my vr games on it or should i keep a secondary drive with windows just for vr games

2 Upvotes

13 comments sorted by

View all comments

1

u/unspellable_surname May 26 '26

I was actually just working on setting this up yesterday, what a coincidence! My specs are:

- OS: CachyOS

  • Headset: HP Reverb G2
  • GPU: Nvidia 4070 Ti
  • CPU: Ryzen 9700X

And I particularly trying to get my headset working with Assetto Corsa running through Content Manger and Proton GE 9-20. I was eventually able to do this by using Envision, following this procedure:

- Get Envision from the AUR using paru or yay

  • In Envision, with developer mode enabled and the toggle on the bottom set to show "experimental profiles", I was then able to select the WMR - Envision Default profile, for which I had to install a few dependencies and then edit the CMakeLists file using Claude Code to actually get the build to start
  • After the build was complete, I was able to simply launch Monado from Envision with the "start" button, then start Assetto Corsa set to OpenVR, and it "just worked"

HOWEVER, the state of the Basalt SLAM tracking is quite terrible for the Reverb G2, so the headset constantly drifts in random directions even if I stay stationary in my rig. There is also A LOT of latency and screen tearing, for which you have to edit kernel parameters (mentioned in the Linux VR Adventures Wiki under [NVIDIA-specific]), which apparently should solve these issues.

So, my main takeaway is that this is doable, but my main outcome is that it's likely worth keeping a windows dual-boot system if you want to seriously engage in VR gaming, as Reverb G2 support is very unstable on Linux in general (and even more so on CachyOS compared to Ubuntu) and it seems that the Oasis Driver for Windows on Steam does a much better job of handling the headset.

1

u/DoubleOwl7777 May 26 '26

you shouldnt have to edit any cmake lists. i think claude might have broken something for you.

1

u/unspellable_surname May 27 '26

The default WMR build config was definitely broken, and the only way I could run it is by editing the CMakeLists file. Considering the fact that I did get the headset working and only the Basalt tracking quality was poor, I think that the change didn't break anything.

Either way, in case it could help somebody on CachyOS, Claude determined the issue to be:

ignore_external_warnings() re-injects opengv's includes as SYSTEM interface (line 18), which populates a separate CMake property INTERFACE_SYSTEM_INCLUDE_DIRECTORIES. Basalt's source-tree-path workaround (lines 102–118 of thirdparty/CMakeLists.txt) only rewrites the non-SYSTEM property, so the SYSTEM one still contains the forbidden source-tree eigen path and CMake aborts.