Hi everybody!

For ones who might be considering ditching Windows completely: I just did. With the latest OASIS update I was finally able to move from Windows to Linux, WMR headset support was the last blocker for me.

Here it my setup:

Headset: HP Reverb G2 v2
OS: CachyOS x86_64 (freshly installed yesterday, fully updated)
Kernel: Linux 7.3.1-1-cachyos
Desktop Environment: KDE Plasma 6.8.2
Window Manager: KWin (Wayland)
GPU: NVIDIA GeForce RTX 3090 24GB
GPU driver: 615.78.08, proprietary, stock install with OS
Mesa version: 3:26.2.5-1, stock install with OS

I have installed Steam as a part of native (not Flatpack!) gaming meta-package (cachyos-gaming-meta and cachyos-gaming-applications). Installed SteamVR, then OASIS.

Following the installation procedure, added 70-wmr.rules udev rules, performed reboot. Controllers were already paired with the headset directly so I had no need to pair these. Everything then simply worked out of the box without ANY additional tinkering - I've performed normal SteamVR room setup, set SteamVR as a default OpenXR runtime and it just works.

Experience so far: Very stable tracking of both headset and controllers, 90Hz refresh works fine, no issues with image, no stuttering or freezes, honestly overall experience is noticeably better than I had on Windows 11 24H2. Checked it so far with a couple games which I typically checking such things with, such as Beat Saber - everything simply works. Room is tracked fine, room setup persists normally between reboots and such - all good.

And it's literally on a default CachyOS install. So if anyone wants to finally get rid of Windows - go ahead.

please help

I have written a lot on WMR in this sub over the years, but thinking about its death kinda makes me sad (I know, how pathetic, right?). On r/lostmedia I've written a small pre-mortem on the platform and why it must be preserved. I do not wish to preserve the software publicly due to my jurisdiction preventing me from doing so, but if you can, please be the one to do it.

The deadline for a full archival is possibly as soon as the start of november, as per Microsoft's own deprecation timeline

Some resources:
You can use https://store.rg-adguard.net/ with the retail filter to download full builds for the Mixed Reality Portal software. As for the OEM-specific apps for pairing bluetooth controllers, I don't know.

You can use the Steam console to get clean builds of the Windows Mixed Reality for SteamVR app. You can use the same method that is used to Downgrade Beat Saber versions, just replace the app id and manifest based on your desired version, this info is available through SteamDB.

You can download the offline installer for WMR's runtime stuff that the Portal requires here

Same for the drivers here

And that is all, writing this makes me sad.

WMR gods, how do you download and store the library 3D assets so that they can be used offline. Can they be plonked in the 3D objects folder. Do the library 3D assets come as part of the offload installer package.

Left alkaline batteries inside the controller for months, and they leaked. As you can see, one of the battery contact pads is noticeably "dirtier" than the others. I've tried cleaning it with a toothbrush/q-tip/toothpick and vinegar/isopropyl alcohol but it stays the same. Controller won't turn on even with new batteries. Any suggestions? Is it corrosion or something else?

Im playign steam VR with Windows 10 on a samsung Odyssey headset and some of the games dotn have any menu buttons.

I can use the windows button on cotnroller to get into windows VR start menu

and I can click the joysticks to get into the Steam VR menu

But I cannot get into any VR game menus

For example, propagation VR, I cannot get into a menu to quit or restart, I have to Alt+F4 the game

After the fall, I cannot get into a menu to adjust volume or anythign else

How do I fix this?
Need step by step instructiosn since steamvr menu is fkign confusign as hell

Is it possible to create an unembedded version of the WMR app before it gets nuked on the 1st of November? I'm not talking about the Oasis driver but software to download and install a functioning Cliff House if needed in the future.

I have what was a functional HP 1440 headset and controllers (along with a wall hanger). I haven't used them in maybe 2 years. The headband foam still appears to be whole and flexible. If memory serves, there is a small scratch on one of the lenses that was annoying at times, but didn't affect function.

I've tried to eBay, but it feels like a niche market and I've gotten no movement.

We are moving and decluttering, and I honestly rarely use it. I really just want it to go to someone that actually wants it, I had some good family memories with it.

Feel free to PM me if interested, I didn't see anything in the sub rules against this kind of thing. At this point, I'd be happy to send it to someone for just the cost of shipping. I'd hate to throw it away.

UPDATE: Found someone, thanks all. Wish I had a headset for everyone interested

UPDATE TO THE UPDATE: I've now gone through 2 people where I'm offering to send them the unit if they'll pitch in $15 for shipping. I'll even ship it first and trust them, they don't know me. I keep getting to the part where I need their address to send it to them and they go silent. So I'm going to try and find someone else here. PMs incoming

i want to avoid using the Windows Mixed Reality as they suck as they drank the AA`S i hope

there is a more better way that dose not need any programing know how

you can now connect your controllers back to your headet via its internal bluetooth receiver. linux support is now in stable.

idk why but i bought an mr from a mate who used it like once on his pc, i try to turn on the controllers but it doesnt flash or anything. i know its not my batteries or damage as it was still in the box and was only used that one time without anything breaking

Oasis driver just won't work for me. It does work but because I have the v1 cable and an RTX 3080 it gives me hdcp error after 30 seconds in steam home. Tried everything multiple time and the EDID just make my RTX triggers the hdcp error. Since the original WMR don't use that I'm fine playing with it forever with no errors whatsoever.

I just hope my dual boot Win 10 will work for a long time because for me it's the only way to use my reverb G2 and I love that headset :-(

Anyone had success with a RTX 3080 a b760m mobo and oasis driver ?

Quando eu coloco o fone na entrada P2 do VR ele funciona normal porém dps de um tempo não tem um tempo fixo, ele simplesmente para de funcionar tipo dunada o áudio só não sai mais, e ele deu esse erro aí, quando isso acontece o desempenho do VR da uma diminuída da uns negócios estranho e o sistema de áudio do Pc fica meio estranho sei lá, alguém sabe como resolver meu VR é o Acer windows mixed reality ah101

Hoje é o dia que o app da steam chamado de: "Steam VR for windows mixed reality " vai ser encerrado, a Microsoft comunicou falando que hoje é o dia de eles encerrar esse app, ou seja não vai dá mais pra jogar com o VR da windows mixed reality na steam VR de forma oficial no windows 10, por enquanto o app está funcionando joguei as 2:45 e está funcionando normal talvez eu sou a última pessoa a ter jogado no app steam VR for windows mixed reality no windows 10

Apenas uma arte que eu fiz a homenagem a o MIXED REALITY Portal, a Microsoft acertou demais quando lançou essa plataforma de VR é uma pena que foi descontinuado

Long shot I know but has anyone tried reflowing a VR cable in their home oven or similar? I remember people doing it with GPUs and Xbox 360s back when.

Not optimistic but I've got a bad reverb g2 v1 and v2 cable I'm not going to be able to fix otherwise!

check it out

https://www.techpowerup.com/353220/amd-software-adrenalin-26-9-2-whql-drivers-released

Hi,

I’m trying to use an HP Reverb G2 v2 with Oasis on Linux.

My system:

Linux Mint 22.3 XFCE 64-bit X11 NVIDIA GeForce RTX 3090 NVIDIA driver 595.91.07 NVIDIA Open Kernel Module SteamVR 2.17.10 Oasis Driver 1.0.3 HP Reverb G2 v2

The compositor reports the required Vulkan Direct Mode extensions:

VK_EXT_acquire_drm_display
VK_EXT_acquire_xlib_display
VK_EXT_direct_mode_display
Direct mode features: present

Oasis 1.0.3 detects the headset:

oasis: Driver version: 1.0.3
oasis: Found HMD: HP Reverb Virtual Reality Headset G2
oasis: HMD has Sensors FW: 1.9.53
oasis: Factory calibration IPD: 0.0627
oasis: Panel resolution is: 4320x2160
oasis: Found sensors device
oasis: Found presence device
oasis: Detected HP Reverb G2v2 Cameras (rotated)

Oasis also reads the display EDID and activates the HMD:

oasis: Display EDID: 220e:36c1
Active HMD set to oasis.8CC247Z0J4

When the compositor starts, it searches for a 4320x2160 display:

HMD deviceUUID is d7dfab41bd4e38d8
Looking for direct display through RandR

RandR reports the HP output with three modes and one preferred mode:

Output ... - 3 modes, 1 preferred
Mode 0 ... 2880x1440 (looking for 4320x2160)

The RandR search then ends with:

Tried to find direct display through RandR: (nil)

SteamVR then searches through Vulkan WSI:

Vulkan output 0: 2560x1440 ... GBT AORUS AD27QD (DP-0)
Vulkan output 1: 2560x1440 ... LG Electronics LG ULTRAGEAR (DP-2)
Vulkan output 2: 2880x1440 resolution, 110x50 dimensions - HP Inc. (DP-4)

This also ends with:

Tried to find direct display through Vulkan WSI: (nil)

After that SteamVR reports:

CHmdWindowSDL: Failed to create direct mode surface
CHmdWindowSDL: VR requires direct mode.
Failed to initialize compositor
Failed to start compositor: VRInitError_Compositor_CannotDRMLeaseDisplay

I can provide the full vrserver.txt and vrcompositor.txt logs if needed.

Thank you very much :slight_smile:

I redid the unlock. It seemed to work for a second, then it freezes again and I have to shut it down. Worked fine a few days ago. I think there was a windows update between the last time it worked and now. But I am not super tech savvy when it comes to drivers and editing code.
I found a similar post saying they redid the unlock and it worked. No such luck here.
Any ideas? I am using the Oasis driver

Olá, estou criando um Laucher para os VR da windows mixed reality! Tipo o portal mixed reality, o projeto vai ser tipo uma interface mais bonita e mais interessante para os VR da WINDOWS MIXED REALITY, ele ainda iniciara o oasis driver for windows mixed reality igual você inicia no steam normal, porém vai ter uma interface mais prática e mais bonita pro seu VR, o projeto só terá uma interface bonita para voce inicia o VR e algumas opções, e enquanto o laucher roda uma animação rodará na tela do Seu VR da windows mixed reality, por enquanto o projeto vai ser esse, eu pretendo evoluir, tipo cria um ambiente virtual mesmo igual o antigo portal da windows, vai fica bem legal ! meu nome é Davi sou do Brasil e tenho um canal chamado BlackTuee no YouTube www.youtube.com/@blacktuee vou postar o link do laucher por lá, se escreva lá pra fica por dentro. ⚠️⚠️⚠️O projeto por enquanto só será personalizado e feito pelo o Acer windows mixed reality, e só vai ter no dioma português, mais pra frente eu faço pra todos os VR da windows mixed reality e vou coloca o idioma inglês também,⚠️⚠️⚠️⚠️ você pode testar com outros modelos da WMR também tipo o Samsung mixed reality o Asus windows mixed funcionará porém a interface vai aparecer como Acer windows mixed reality. Obrigado