Quest Pro - VirtualDesktopXR and Quadviews

[Jive]

Hello everyone,

I recently changed from a G2 to a Quest Pro. I've been doing the standard non-stop tweaking we all inevitably do to try and get the results we want and I think I'm more or less there with this exception.

Over Link (wired) I see QuadViews working dynamically with the eyetracking, no real issues. However when I alternatively run VDXR wired or wireless I'm very happy with the results yet QuadViews seems to revert to being fixed. Is there something I'm missing or is eye tracking not a feature that Virtual Desktop can make use of yet?

A follow on question would be to check my understanding: VD can use Local Dimming but Link cannot? Aside from 'feeling' like the VDXR runtime was nicer this is the main reason I was hoping to have everything running via VD. 

Also grateful for any other QPro DCS tips and if anyone would kindly share their preffered Quadviews settings to dial into the companion app

Thanks!

[Mr_sukebe]

Sounds like you’re up and running.

Two points that spring to mind, which won’t help performance, but might be useful:

- out of the box, I found the QP very uncomfortable.  My solution was a pack of 4 Zeltauto straps (£11 on Amazon).  I use three over the headband and makes it massively more comfortable 

- the inbuilt audio is crap.  Koss KSC75s.  They’re dirt cheap and not amazing quality by a long way. They do however work fine and again are for me, comfortable to use 

[Jive]

I just answered my own question haha
In Virtual Desktop's in-headset Streaming setting there is a check option for sending eye tracking data to PC, that enabled it. 

Honestly I'm shocked at how nicely and clearly DCS runs in wireless Virtual Desktop

Thanks @Mr_sukebe
I got a KKCOBVR battry pack that has a headstrap through the middle and counters the weight nicely but I'm still getting pressure on the forehead so I'll try your idea too.
Also, yeah I was looking for an audio solution so thanks again. I don't hate the onboard sound overall but there is zero bass!

Edited July 23, 2024 by Jive

[VR Flight Guy in PJ Pants]

1 hour ago, Jive said:

A follow on question would be to check my understanding: VD can use Local Dimming but Link cannot? Aside from 'feeling' like the VDXR runtime was nicer this is the main reason I was hoping to have everything running via VD. 

Local dimming is in the Experimental Features section in the QPro setting menu, not sure if it would work with PCVR, but iirc, it does not.

[Jive]

17 minutes ago, VR Flight Guy in PJ Pants said:

Local dimming is in the Experimental Features section in the QPro setting menu, not sure if it would work with PCVR, but iirc, it does not.

Afaik it needs a call that it can't get from Meta Link (either wired or wireless) but Virtual Desktop and in-headset apps can use it. I think the experimental setting is to have it globally enabled and appears to work in those latter conditions but still not in Link. Seems VD is the way to go to me so far although I suppose with Link you could push higher resolutions than the highest VD preset. 

 

Still getting my head around it 

[Tomcat388th]

For the quad views/eye eyetracking to work. On the VD streaming tab menu that you pull up while in the headset. Select "Forward tracking data to PC".  

Edited July 23, 2024 by Tomcat388th

[VR Flight Guy in PJ Pants]

The problem I have had with VD is that it uses SteamVR only and I hate it. I just updated VD to the latest, turned on local dimming and tried to launch DCS, only to have it crashed...

One more thing, I dunno but as far as I can see, VD does not support cable Quest Link. Please let me know it works now. thanks.

Edited July 23, 2024 by VR Flight Guy in PJ Pants

[Tomcat388th]

13 minutes ago, VR Flight Guy in PJ Pants said:

The problem I have had with VD is that it uses SteamVR only and I hate it. I just updated VD to the latest, turned on local dimming and tried to launch DCS, only to have it crashed...

I get so confused with all the runtimes  I thought VD was it own runtime  I do see the option on one of the menu screens for launching Steam.  I keep it as a backup in case link get messed up. Performance wise it right on par with link with my system now. The only thing that I notice is the text on the displays are not quite as crisp as link but still plenty clear

@Jive @Mr_sukebe    If you haven't done it already if you flip the back head pad 180 it really helps with taking all the pressure off of the forehead.  It's clipped on there pretty good but it will pop loose.

[VR Flight Guy in PJ Pants]

You mean VDXR. It works and I need to sort out the audio, NeckSafer and hand tracking issues...

[VR Flight Guy in PJ Pants]

Okay, make audio, handtracking and XRNecksafer working. Shall make a video citing the differences. Thanks for the idea.

[mbucchia]

2 hours ago, Tomcat388th said:

I get so confused with all the runtimes

Here's a very comprehensive explanation:

https://github.com/mbucchia/VirtualDesktop-OpenXR/wiki/Oculus-"Runtimes"

 

Edited July 23, 2024 by mbucchia

[VR Flight Guy in PJ Pants]

Thanks. so VD do support link cable then? Or should I use the standalone VDXR?

[Tomcat388th]

2 hours ago, VR Flight Guy in PJ Pants said:

You mean VDXR. It works and I need to sort out the audio, NeckSafer and hand tracking issues...

 As far as I know VD is wifi only  but I could be wrong.  I'm using an asus router wired into my computer with the oculus pro on the the 5Ghz wifi. 

Here are my settings on the computer app.  On the VD menu in the headset I'm running 72hz with the asw disabled with ultra or godlike

51 minutes ago, mbucchia said:

Here's a very comprehensive explanation:

https://github.com/mbucchia/VirtualDesktop-OpenXR/wiki/Oculus-"Runtimes"

 

 

Thanks again

J

Edited July 23, 2024 by Tomcat388th

[Jive]

1 hour ago, VR Flight Guy in PJ Pants said:

Thanks. so VD do support link cable then? Or should I use the standalone VDXR?

I was hoping it could do all it's stuff over cable too but doesn't seem to. 

 

[VR Flight Guy in PJ Pants]

Question: I know that eye-tracking is supported by VDXR for QPro, but I find it is not as noticeable as Oculus OpenXR. Is it about setting in QuadView? This is my VD setting:

 

and sorry for going OT.

[Qcumber]

Future updates for VD aim to integrate QVFR. At least according to some posts on Discord by mbucchia a few weeks ago. This should make integration of QVFR much better. 

9 hours ago, Jive said:

I recently changed from a G2 to a Quest Pro

Welcome to the QP. It is still an amazing headset and often overlooked now. 

[Tomcat388th]

@VR Flight Guy in PJ Pants  when you say you find it "not as noticeable" are you talking about being able to see the faint outline of the focus box or something else?   When running on cable link I can make out the focus area at times looking up at the sky I dont see it as much with VD. I also use this program to tweak quad views settings. Its called   Quad View Companion  I believe it listed in ED's user file section.

J
 

[VR Flight Guy in PJ Pants]

This is what I meant to be not so noticeable:

Thank you all for your help.

And one minor issue too:

 

Edited July 23, 2024 by VR Flight Guy in PJ Pants

[Phantom711]

vor 23 Stunden schrieb VR Flight Guy in PJ Pants:

 

Question: I know that eye-tracking is supported by VDXR for QPro, but I find it is not as noticeable as Oculus OpenXR. Is it about setting in QuadView?

 

I guess it might have to do with the codecs that Meta uses vs. VD.

I used HVEC10 with VD and I feel the same way. Maybe HVEC10 handles the „lesser“ pixels in the outer area differently from H.264.
In your video, side by side, I would say that VD makes the outer area rather blurrier whereas OculusLink makes it kind of pixelated/grainy. The latter would certainly be more noticeable  in the peripheral vision.

 

The ghost trails: do you use DLAA or DLSS? They tend to do that.
 

Edited July 24, 2024 by Phantom711

[VR Flight Guy in PJ Pants]

6 minutes ago, Phantom711 said:

The ghost trails: do you use DLAA or DLSS? They tend to do that.

Nope.

I think I am going to increase the sharpening factor in VD while bring the FPS down to 72.

Edited July 24, 2024 by VR Flight Guy in PJ Pants

[Jive]

Am I crazy or does the eyetracking with QuadViews seem much faster in VDXR? I notice it way more in Link than in VD

[mbucchia]

7 minutes ago, Jive said:

Am I crazy or does the eyetracking with QuadViews seem much faster in VDXR? I notice it way more in Link than in VD

Quest Link is really just a "devkit" of Meta's standalone (Android) platform. You should get that hint from the fact that you need to enable developer mode to even get these features

Virtual Desktop and VDXR on the other hand are fully optimized for what people actually care about and use. We take the eye tracking data at the beginning of each frame and send it as quickly as possible to the application. No B.S in between. So I'm not quite surprised if you find it better. Haven't done any analysis myself, but I can only imagine this isn't even a thing Meta tests on PC beyond their Avatars SDK that no one else seems to use (good product though, just not what people actually care about).

[ricktoberfest]

15 minutes ago, mbucchia said:

Quest Link is really just a "devkit" of Meta's standalone (Android) platform. You should get that hint from the fact that you need to enable developer mode to even get these features

Virtual Desktop and VDXR on the other hand are fully optimized for what people actually care about and use. We take the eye tracking data at the beginning of each frame and send it as quickly as possible to the application. No B.S in between. So I'm not quite surprised if you find it better. Haven't done any analysis myself, but I can only imagine this isn't even a thing Meta tests on PC beyond their Avatars SDK that no one else seems to use (good product though, just not what people actually care about).

I realize this might be a bit off topic, but any way to get better hand tracking in VD, or hand tracking at certain times. I find when I enable hand tracking I can no longer use my mouse and the pointer for hand tracking seems to come out the top of my knuckles rather than in line with the finger tip

[Jive]

I used VD for some DCS earlier but I had some networking issues at the time so I switched back to Link via cable and the eye tracking was noticably faster in VD than Link. Eyetracking/Quadviews was my main reason for choosing the QPro over the Q3 and I had been slightly dissapointed with how often I could see the blurring of the non-foveated area off my periphery, mainly with clouds. Increasing the size of the foveated area helps yet this of course reduces the performance gains. I find this much less obvious in VD, which I'm delighted with. 

With VD providing local dimming, faster eye tracking and a more optimal runtime with VDXR it's all looking very bright. Thanks for all you dedicated work @mbucchia I would have given up VR in DCS without the progress you've brought to the table. 

Perhaps counter-inuitive for the most part but do you know if we'll ever see a wired option for Virtual Desktop in the future?

Edited July 24, 2024 by Jive

[Qcumber]

47 minutes ago, mbucchia said:

Quest Link is really just a "devkit" of Meta's standalone (Android) platform. You should get that hint from the fact that you need to enable developer mode to even get these features

Virtual Desktop and VDXR on the other hand are fully optimized for what people actually care about and use. We take the eye tracking data at the beginning of each frame and send it as quickly as possible to the application. No B.S in between. So I'm not quite surprised if you find it better. Haven't done any analysis myself, but I can only imagine this isn't even a thing Meta tests on PC beyond their Avatars SDK that no one else seems to use (good product though, just not what people actually care about).

Any update on if/when QVFR will be included in VD?