Second hand Quest Pro worth having when i already have a Quest 3 ???..

[diamond26]

1 hour ago, Gunnergolly said:

Yeah i really want the Quest Pro to work out, but we're not just not getting on very well together at the moment :)...

I've posted my link settings, i have a dcs profile dedicated for the Apache which is locked at 45 so that i can achieve smooth frames when i'm flying on the Syrian map.

They work well for the Quest 3...

 

 

Personal preference is to have Distortion Curvature at Low, Encode resolution 3664, Encode bitrate 500 and Link Sharpening on Normal (or enabled). I would suggest also to check the adaptive option in ASW provided by OTT since you want ASW for Apache.

[Gunnergolly]

Thanks for your settings, i'll give them a try later...

I normally use Virtual desktop which works really well for me providing i can maintain the headsets refresh rate..... only time i use link is for the Apache when playing on either the Syrian or Marianas map when i need to use ASW. 

My first challange is to get eye tracking working, i need to get the toggle switch in  "developer" mode in the mobile app to appear. I've hit a brick wall at the moment with my current Meta account not playing ball, so will try markturner1960  advice and create a new account from scratch. Not exactly sure how he did it but i am going to dedicate my Quest Pro purely as a flight sim PCVR headset with only Virtual desktop installed.

So my plan of attack tomorrow is :-

1) Factory reset my headset.

2) When i power up the headset i'll set up a new account as a first time Meta user using a different email address.

3) Try and avoid tying in my new user account with facebook if i can.... my current Meta account is already associated with facebook, not sure how that might effect my new account. 

4) Pair my headset with the mobile app.

5) Sign in as a developer (https://developer.oculus.com/manage/organizations/create/) using my new email address and password.

6) Create a new developer organisation using the method in the Youtube video below and verify it by whatever means.

7) Go to the headset settings tab on the Meta mobile app and hopefully the "developer mode" toggle switch will have magically appeared..... i hope.

It's been confirmed by Phantom711 that my current Developer account looks like his and should be good to go. Hopefully doing the above will help to establish were the problem lies with not been able to enable developer mode on my mobile app. If createing a totally new account dosen't resolve the issue than i'll have start looking elsewhere.. 

That's my plan anyway.... any suggestions are always welcome...

Edited November 16, 2023 by Gunnergolly

[freehand]

I used my 2017 account I did not go through the pain you are experiencing lol good luck. 

But the old developer mode back then is different from now and had to go through the new process.  

Edited November 16, 2023 by freehand

[Gunnergolly]

I'm probably making a complete meal of it as i'm just guessing here, but i have to do something as it's not working.... the whole point of me buying the Quest Pro was to use Dynamic QVFR .... and i can't at the moment !!!.

Originally in the good old days a few years back i imagine that i would have created a developers account using just my Oculus account ..... unfortunately it's grown arms and legs since then now that Meta and facebook have got themselves involved.....

What could possibly go wrong ........ We'll see what happens ....

Edited November 16, 2023 by Gunnergolly

[markturner1960]

Good luck buddy!

 

[Gunnergolly]

Sorry for the long post, but i wanted to provide details on how I managed to finally get eye tracking working on my Quest Pro up and hopefully I might just save somebody else hours of frustration in the future. The fact that i was expecting to see a "Developer mode" toggle switch in the mobile Oculus app headset settings menu after successfully creating a developers account threw me. 

We’ll I’m happy to say that I finally have eye tracking up and running on both Virtual desktop and Oculus link.

My previous post with it’s choreographed steps didn’t quiet go according to plan as I could not create a new user account when doing the initial headset setup after factory resetting it. Instead, I had to create a new Meta account online and then assign my Quest Pro to that new account…. Which wasn’t easy as I had to jump through a few Meta hoops to get there…

However, the new account didn’t work either so Phantom711 was right when he said in his post that he thought that my original developer account was ok and I ought to maybe look elsewhere….. However at least I had proven it beyond doubt now that it wasn’t my original developer account at fault…. So I deleted my second account, paired my Quest Pro to the original account and started looking elsewhere.

Concentrating on Virtual desktop first, previously I was unable to tick the “Forward face/eye tracking to PC” checkbox to enable eye tracking in VD. Following mbucchia VD OpenXT eye tracker setting up instructions I had only enabled eye tracking in the Quest Pro’s settings -> Movement tracking menu. I eventually realised that in order to allow me to enable the "Forward face/eye tracking to PC" checkbox I also had to enable Natural Facial Expressions in the same Oculus movement settings menu as well.

Ticked Virtual Desktops “Forward face/eye tracking to PC” and it stayed on, tested eye tracking using mbuccia’s OpenXR Eye tracker app and it was working perfectly.

Moving on to Oculus link next, so I turned on the “Developer Runtime Features” and “Eyetracking over Oculus link” switches on the Oculus PC app in the settings -> Beta menu…. but the eye tracking was not working when tested.

Did a bit of googling and it said that on the phone app the under headset settings the “Developer mode” also had to be turned on.  

I still don’t have the “Developer mode” option available on my phone app under the Quest Pro's "headset settings", I only have “Debug mode” available, so I turned that option on and the Oculus link eye tracking started working.

When I tested Oculus link a couple of days ago, I wrote that the performance was awful, so yesterday, I uninstalled the Oculus app deleted anything Oculus related in the Local, LocalAppData, LocalLow, Roaming folders located in C:\username\AppData. Used CCleaner to clean the Registry and then went in to the registry using Regedit and manually deleted anything remaining that said Oculus……

Reinstalled the PC Oculus app, tested again and now have good Oculus link performance…. Still needs tuning but at least it’s running smooth now.

My next challenge with this headset is to find out if I can run it use a wired internet connection like I can on my Quest 3 using my ethernet to usb C adapter which also supplies power to the headset when using Virtual Desktop….. however that's for another day…. I’m just going to enjoy playing with my new Quest Pro now…..

Edited November 18, 2023 by Gunnergolly

[Phantom711]

vor 55 Minuten schrieb Gunnergolly:

I still don’t have the “Developer mode” option available on my phone app under the Quset Pro's "headset settings", I only have “Debug mode” available, so I turned that option on and the Oculus link eye tracking started working.

That`s what I meant..I think "Debug mode" is just their new terminoligy for "Developer mode".

Good to hear that you finally got it working. 

Still curious about your comparison.

Specifically:

Is the Q3 niticably clearer on the MFDs (i.e.: Hornet) at the default head position (so without leaning forward)?

What is the performance boost of QVFR?

All this is especially interesting to me since my system is almost the same as yours (without the oc´ed CPU).

Edited November 18, 2023 by Phantom711

[Gunnergolly]

I've not had a lot of playtime on the Quest Pro at the moment.

However my initial thoughts are that in terms of reading the Hornet's MFD's, cockpit labels, etc etc the Quest 3 has the slight edge but that said .... barely.

Where the Quest Pro has the advantage is that the view through it's lenses just seems more "panoramic", more natural feeling and has better vertical FOV..... i oversample using XR Toolkit and i'm having no problem reading the MFD's.... even if i turn DLSS on.

The view through the Quest 3 lenses is equally beautiful, especially if you have the horse power to drive it, nice contrast and colours but i don't know how to explain it, kind of feels like your view is slightly squashed together ...  To be fair i think once a comfortable aftermarket soft facial interface becomes available it will make a world of difference. ... out of the box comfort of the Quest 3 is awful.... i have an elite strap, but still using the original face gasket at the moment. 

Performance wise, i can't offer you numbers but the Quest 3 on my system performs better than the Quest Pro when using Qculus link, with less audio/graphical stuttering ... however to be fair i need to spend time with the Quest Pro tuning it on link,  it's still very early days yet as i have been to busy trying to get the damn thing to work !!!.

The Quest 3 on Virtual Desktop with the new VDXR runtime runs beautifully with a wired USB C internet connection, the Quest Pro running on VIrtual Desktop wirelessly also appears to be running well too.... i'd prefer a hard wired internet connection.... but it is what it is at the moment..

On the Quest 3 using Fixed QVFR my system is rendering 57% less pixels, this compared to if i were using the same resolution over the whole view without QVFR installed.

With the Quest Pro my system is reducing both the "horizontal and vertical focus sections" parameters from 0.5 to 0.15 in the QVFR user settings.cfg file my system is having to generate 73% less pixels. 

I can't give you performance figures for comparison between the two headsets, but in terms of how smooth they feel when flying.... it's hard to discount either of them...their both excellent headsets... and i'll be keeping both ..

If my interest was purely PCVR flight simming ... then personally i would choose the Quest Pro, the view through it's lenses in DCS world is beautiful and just has the feeling of depth..

Hope that helps...

Edited November 18, 2023 by Gunnergolly