VR Discussions, Questions & Feedback

Why don't you just rollback the Nvidia drivers?

 

Because I need the latest drivers for other (non VR) games.

I could solve my problem today by installing and using Virtual Desktop (even with my Link-cable) for the first time .

Only problem I have now is that my FOV-reductions via OculusTrayTool-Profiles don't work anymore (to get huge performance gain in night/rain-races).
I tried the FOV-reduction in the Virtual Desktop-app, but here I can only set it global (for ALL VR-games, even those who don't need this performance-boost) and even if I set it globally there the mainmenu from AMS2 is not a fixed window anymore but moves around when I move my head (which is quite annoying). Only when I start a race and jump into the cockpit suddenly the FOV-reduction is working as intended. After race when I go back to main-menu the menu starts to move around again. Any ideas? I'm new to Virtual Desktop.

EDIT: I just wanted to clarify that I still use the openxr trick (SteamVR bypass with my good old 2 dll-files in the game directory). So I start as usual from Steam with "SteamVR"-mode but in Virtual Desktop and it bypasses SteamVR and uses OpenXR (which brings more FPS). So everything is fine and even better (better graphics, better clarity, super fluid except in rain/night-condition and this is where I miss my FOV-reduction so gain FPS)

 

FYI - Interesting News on the Oasis Driver, now for Linux! Looks like it's a WIP, but it's great to see development for old WMR glass on Linux.

Oasis Driver for Windows Mixed Reality - Oasis for Linux - Support with Ignition - Steam News

I have been building a new Linux home lab over the past few months and my sim-rig is currently in pieces. This time last year, I had switched over to using the Oasis driver (with Windows & Reverb G2), and it worked great for me. Switching over to Linux, I figured the Reverb would be collecting dust. This is certainly something I'll be looking into, once I get all my other equipment up and running .

 

You might find the latest Nvidia drivers will cause issues with Virtual Desktop as well. The developers recommend driver version 610.62 as later versions have been known to cause all sorts of issues with VR (including Meta Link).

If you're set on using Virtual Desktop with OpenComposite, I'd suggest getting the version of OpenXR Toolkit by Ohnespeed that has the CROP2FOV function. Apply the crop in the toolkit and it avoids the cropping issues that comes with Virtual Desktop's implementation.

Worth noting is that the new USB support by Virtual Desktop and Steam Link doesn't utilise a direct data connection like Meta Link does. Instead, they use TCP & UDP over USB and it's been reported it's far more susceptible to stutters and drops, depending on the cable. A more reliable option at this stage would be a USB-C to Ethernet adapter.

I've tried changing over to Virtual Desktop but the clarity and sharpness of Meta Link for me is still far superior. It's just a shame that Meta updates in January have rendered my Link a stuttery mess with bitrates over about 300. Even at lower bitrates though, I find Meta's image quality better compared to Virtual Desktop at 500mbps. The sharpening that Meta applies has some sort of magic that Virtual Desktop doesn't come close to.

 

Thank you for your answer. In my case I use my good old (original) link cable to connect via the latest Virtual Desktop app.
For me the quality is now (with VD) much better than before.

I use following settings (hope this might help you to get also better quality):

Virtual Desktop Streamer App on PC:
- Preferred Codec: AV1 10-bit
- OpenXR Runtime: VDXR

Virtual Desktop App in Quest 3:
- Connected with Link-Cable (USB 3 / 5,120 Mbps)
- Streaming settings:
- VR Graphics Quality: Godlike (= 3072x3264)
- VR Frame Rate: 72 Fps
- VR Bitrate: 200 Mbps (= max)
- Sharpening: = 75%
- Synchronous Spacewarp (SSW): DISABLE!

Inside the Quest I have 1.3x resolution (max res @ 72hz), but I don't know if this matters anymore as these settings are in the Meta Horizon Link app, which I don't use anymore since I switched to VD today...

With these settings my VR-games (including AMS2) run super crisp and fluid (except in rain/night-conditions - there I can't hold the 72 FPS and therefore get stutters that's why I want to crop the FOV, like I did in the past with the Oculus Tray Tool profiles). It's interesting that I get better VR-quality with my above new settings although the max is 200 Mbps here whereas with my old Meta Horizon Link I had 800 Mbps (but H.264 codec).

-> I will try your suggested "OpenXR Toolkit by Ohnespeed that has the CROP2FOV function". Do you have a link to that? I thought that the OpenXR Toolkit has been abandoned since 2024?

 

I have landed on exactly the same settings you're using. I have Quest 3s and have only an occasional hiccup and very happy with the video and smoothness.

 

If you're using cable with virtual desktop you should use H264+ at 500mbps. IMO it looks better than AV1 or HEVC at 200.

 

Ok, so if anyone is on the fence this is definitely worth doing. I think previously I was chasing shadows when optimising detail level, when in fact wifi interference in my block of flats was actually causing problems. Currently running F1 races on godlike, unlimited vehicles visible, getting 120 FPS outside of the start, most of the details on medium.

 

Just a short Q to be clear: I am still running Win10. If I upgrade to Win 11 my G2 will still work the same way as before with Steam? Thx.

 

Yes via Oasis Driver

 

If you upgrade to Win 11 23H then you can keep Windows Mixed Reality, any version above this will delete WMR from your system. The Oasis driver will solve that though.

 

This application allows foveated rendering in VR for AMS2 among other things.

 

FrameGen for VR is here;

Original Mod - https://github.com/tig3rmast3r/OFXR-Bridge/releases
Fork with further advancements - https://github.com/djules75/OFXR-Bridge

Ultimately I've been able to max out all AMS2 settings and maintain 90fps (OFXR) at night in the rain with 47 cars and 20+ visible, something that quite simply would not be possible to maintain at 45fps let alone 90fps without the mod!

It's not often a "game changer" comes along but I do firmly believe this is one, definitely worth keeping an eye on both the Original & the Fork as they're both getting updates, one may work better for you than the other depending on your rig/HMD etc.

 

Thank you, this sounds very interesting as I need 72 FPS in my Quest 3 but can’t hold them in night&rain condition or in replays.

Is there a step by step guide what exactly we need to do to use this?

I play AMS2 with Virtual Desktop app and link cable and use the openxr trick with the SteamVR bypass by putting 2 DLL-files in the game folder. Will this „FrameGen“ work with my „setup“ and what do I have to do or change?
Thank you for helping.

 

All the info required to get it running is in the first link, I can't help with your specific requirements as I have no knowledge with your setup. There is a discord channel you can ask for help (also in the first link)

 

Tried with Meta Link and a Quest 2, with a 4070 super, but can't see the fps overlay and does nothing with ASW off. But, by some magic or placebo effect, ASW looks smoother.

Thank for trick my optimistic brain.

 

Thanks mate!

I tried this mod and it works!!! At least for me. The only things I noticed, obviously, were increased latency and VRAM usage, but you can get good results by tweaking the settings! The only issue I spotted was with moving cars—there’s a sort of jitter or flickering, hard to explain—but otherwise, it does the job! Simply fantastic and definitely one to keep an eye on! I just launched the program and saw the native overlay showing a steady 90!

 

Which one are you using? The Djules (bottom link) is getting daily updates and I've been assisting with testing due to a recent issue with AMS2 (now fixed in latest version)

 

Will try again to see If It works now. It's better than the motion smooth in NVIDIA APP? I tested It and looks worse than ASW.

 

I would like to play Zero to Apex (Z2A) in VR. I use Quest 3 with latest Virtual Desktop connected via Link cable and use the OpenXR trick with the 2 DLL files in the game folder (SteamVR bypass). I see the Z2A screen in VR but when I should start a race in AMS2 it doesn’t switch to it. The AMS2 stays on my monitor and the Z2A stays in my headset. I think both should be in my VR headset and it should switch automatically between the 2 apps but it doesn’t. Any ideas how I could solve this?