Flashing the wrong firmware to my 3070 was a stroke of genius.

When I use #WiVRn with GPU Encoding and run a game, it absolutely sits at the power limit (300W) when the original was 240W, with an extended limit at 270W, while now it's 270W up to 300W.

And it will sit at 300W all day long. Thank you EVGA for overbuilding these cards so much. <3

(I flashed the FTW3 firmware to my XC3 Ultra)

...It amuses me opening OpenRGB and seeing "EVGA GeForce RTX 3070 FTW3 Ultra LHR" instead of the XC3 Ultra as well.

Anyone know if it's possible to make the clocks in wlx-overlay-s use 12 hour formatting instead of 24?

#Linux #LinuxVR #WiVRn #wlx_overlay_s

Edit: Solved! Turns out a sneaky pyenv shim replaced my cmake with an older one that the WiVRn build did not support because it was expecting the missing newer features without warning that this version of cmake is too old.

I’m trying to install #wivrn (Monado for wireless #VR headsets) on Arch Linux and having this odd problem where both #envision and the wivrn-server AUR are failing to link monado-service. Specifically, #monado is erroring with these undefined references:

I’ve been sitting on this for several days and I have no idea what’s going on. At least as far as listen_socket goes, I do have the systemd-libs installed so I don’t know why it’s failing.

If anyone has any ideas, I’m as lost as it gets.

#linux #virtualreality

Consegui fazer meu setup de realidade virtual funcionar no Linux usando a stack open source! Usei Monado (runtime OpenXR e OpenVR via OpenComposite); #WiVRn (conexão com headset standalone, Oculus Quest 2) e #WlxOverlayS, um overlay para acessar o desktop, monitores, controlar volume, teclado virtual etc...

Os recursos do WlxOverlayS são algo que jamais funcionou no meu setup de antes com SteamVR (runtime) e ALVR (conexão headset) no Linux, por mais que no Windows desse certo via Virtual Desktop. A Valve ainda não tornou o cliente da Steam nativo sob Wayland, acho que isso acaba limitando as funcionalidades que o próprio SteamVR consegue fornecer em Wayland no Linux por conta disso - captura de tela via portais e pipewire, principalmente. Felizmente, o lado open source da força veio para nos salvar!

Consegui rodar todos os meus jogos de realidade virtual da Steam através desse setup (só requer colocar umas variáveis de ambiente nas opções de inicialização deles) e ainda por cima consigo usar um monte de utilitários baseados em OpenXR como o WayVR e WayVRDashboard :)

So we just completed our first full #VRChat session under #Linux and we have some thoughts that we wanted to share :) Long post incoming~

First off - we are honestly very impressed how far #VR has come on Linux. We remember when the Vive and Valve Index was the only headsets that would work at all, so the fact that we have not one but two wireless streaming solutions for the Quest headsets is awesome. #ALVR and #WiVRn are both amazing pieces of software, and it makes me happy to see that you can combine them with Proton to make Windows VR games work on Linux. And, all of these worked flawlessly on Wayland with an NVIDIA GPU, which honestly kind of shocks us.

That being said I want to talk about a few things - our experience with VRChat on Linux specifically, and our experience with both ALVR and WiVRn, since we used both during this play session.

(For reference sake, all playing was done on Nobara Linux 40. Our system has a Ryzen 7 7800X3D, an RTX 3080 Ti, and 32GB of DDR5.)

Starting with VRChat specifically, we did a three-hour session. We spent it with a friend, hopping around Winter VKet for a while and then settling down in a chill world. All in all, using the custom Proton-GE-RTSP fork, it worked almost exactly like it did on Windows. Video players and music worked, AudioLink worked, everything rendered correctly, and the experimental Linux build of VRCX has 99% of the functionality it does on Windows. Really impressive stuff. We did crash three times - twice in ALVR and once in WiVRn - which is suboptimal, but random crashes aren’t necessarily a Linux-only problem; although they did occur more frequently than usual. Performance was ultimately good enough, but it did look visually worse than on Windows and ran a little worse too, with more framerate drops and more inconsistent frame-pacing.

Now, as for the VR streaming solutions themselves.

ALVR was a bit more reliable out of the gate. It’s more polished and has more features, and connecting to our PC had less hangups than WiVRn. Customization is boundless (perhaps too boundless…), and we feel it is the closest thing to a “Virtual Desktop replacement” on the platform. It hooks into SteamVR, like VD, and generally ‘just works’. Visual fidelity felt ‘good enough’, but the default foveation was very aggressive, to the point of feeling almost low-res and distracting. The image also, weirdly, lacked some contrast, and looked kinda washed out. Playable, but not great. ALVR also felt smoother out of the two, but would have some really disorienting moments if the FPS dipped too much, like reprojection or motion smoothing weren’t quite working. It also crashed pretty catastrophically at one point, taking both SteamVR and VRChat with it, but we’re not really sure what caused this - the world we were in had a lot of different audio sources playing, so maybe this was an issue with Proton-GE-RTSP or SteamVR or something else. Still, it sucked.

WiVRn + Monado worked better than we’d expected. Visual fidelity was better, and the image had more contrast and looked more vivid than ALVR. However, it felt notably more jittery. Frametimes felt higher, even though the framerate was statistically higher than ALVR, almost as if it wasn’t doing any reprojection at all. It wouldn’t halve the framerate like VD or ALVR do when they can’t reach the target (in this case, 120 FPS), so the framerate would often hover around 80-90 FPS or so. Despite this, we never got that disorienting “floaty”/“shaky” feeling that ALVR gave us when it was struggling. We think it was ultimately a slightly better experience than ALVR, but not by much. That being said, because it uses Monado as its VR runtime instead of SteamVR, the “initializing/connecting” screens in between worlds didn’t render properly, which made it impossible to tell that VRC had actually crashed when we entered a world portal. We waited for about two minutes before realizing the game needed to be force-quit and restarted. Unsure if this was a VRC problem, or a WiVRn problem, but portals did work fine for us in ALVR.

At the end of it though, it was a successful VRChat session. We still have reservations - stability is lessened, both WiVRn and ALVR look worse than Virtual Desktop, and performance takes a notable hit - so we’re not sure if we’ll stick with Linux full-time. But it’s awesome that VR has come this far. We’d say that for those who are truly Windows-averse, Linux is definitely viable for social VR. It may not beat Windows just yet, but it’s amazing to see that for those who decide to switch, it’s one less thing they have to leave behind.