Gunnergolly

The Q3 has been the easier headset to get up and running.... it always just worked for me straight away with very little tinkering required. Initially the problem that i found with the QPro when using Oculus link is that it was constantly stuttering, even through it was achieving the required refresh rate. Eventually i figured out after playing around with the Oculus Debug tool settings that when i changed the Video codec from default to H.265 it started running smooth. Tomorrow when i have a bit of time, just out of curiosity i'll connect the Q3 up to Oculus link and try both codecs and see which one of the two run's better with that headset. I'm also finding that when i use OTT to try and force 1/2 refresh rate it stutters like crazy with the QPro. At the moment when using Oculus link i'm just ramping up the settings/resolution so that my system is forced into using ASW ... it looks good and is pretty smooth when flying the Apache... my RTX 4090 is certainly getting a good workout. Within Oculus Debug tool, i've also tried changing the (PC) Asynchronous Spacewarp to "Force 45fps" ASW enabled/disabled but they have no effect in game and they just change's back to disabled in ODT. I've done quiet a bit of googling and i can't find anything with regards to connecting the QPro to a cable for internet via a ethernet to usb C adapter.... i'm thinking that it maybe can't be done ??... I've had my QPRo for a week now, it's been a challenge (some of it down to my own ignorance i have to admit), but i'm getting there with it now, the eye tracking is working well and it's certainly a nice headset for flight simming..

My preference is to use Virtual Desktop with the new VDXR runtime and it runs well on the Quest Pro wirelessly and looks really good.... However i'd much prefer to use a cable if i could. As good as VIrtual Desktop is it falls down when my system is unable to maintain the headsets set refresh rate (72 in my case) and the ASW method on Virtual desktop is ugly..... not to be used... There is a work around that achieves a smooth 1/2 refresh rate experience with VD, but if what your flying has either a set of rotors or a propeller it's horrible. I've been experimenting with Oculus link for a couple of days now using the above link cable and it's working well now...... however Oculus link is my second choice.... I only use Oculus link when i know that i can't achieve full frame rate reliably, i'e flying Apache over certain parts of Syria. My initial Oculus link experience with the Quest Pro was not good, i was achieving the frames but it was jerky/ghosting effect with choppy sound. I've since discovered in the Oculus Debug software that if i select the H.265 video codec than it's smooth. When using my old PICO 4 or current Quest 3, both headsets allow(ed) me to turn the headsets wifi off and use a cable that supplies both power and internet via a ethernet/USB hub instead... it works really well..... compared to wireless it boosted my connection by about 50%. Is it possible to connect my Quest Pro directly to my router via an ethernet to usb C convertor ??. I'm using the one below which has proven to be very reliable. https://www.amazon.co.uk/dp/B08NXS46DN?psc=1&ref=ppx_yo2ov_dt_b_product_details

The Quest 3 allows me to turn off the headset's WIfi and instead use an ethernet to USB C adapter via a long cable to supply power/internet to the headset. I've tried doing the same with the Quest Pro, the power side is working, but it's not recognising the internet connection..... is it possible to supply the internet to the Quest Pro in this way ??.

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...

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…..

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 ....

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...

Yeah i really want the Quest Pro to work out, but we're 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...

Yeah i could maybe do a factory reset of the headset and create a new account as a totally new user totally dedicated to this headset . Obviously i would lose all my games and content, but as i only intend to use this headset for DCS i would only have to repurchase Virtual Desktop once i have know that i can turn developer mode on ..... i would still be able to use all my other Meta content/games using my current account on my Quest 3... I tested the Quest Pro on link this morning, i'm not impressed.... F18C free flight quick start mission is awlful, flying over the buildings at high speed i'm getting a lot of ghosting and stuttering..... the sound is chopping in and out and my bitrate is only set at 300. Tested the Quest 3 using the same settings/link cable and it's super smooth and i can turn the bit rate up to arounf 750 before the sound starts stuttering. Virtual desktop is running really good, but another problem with this headset is that i can only use it wirelessly with VD, the Quest 3 and PICO 4 allowed me to turn off wireless and use a ethernet to usb C hub and feed the internet via the cable into the headsets usb port. When i get the time i will try and create a new account..

Guy's just want to say thanks for you help and interest, i'm just going to forget about it tonight. I've spent to much time on it today already....just going play some DCS with it and see how it compares to the Quest 3 :)...... Tomorrows another day...

Within the Meta App i have another verification screen, it looks like it's for verification of an organisation.... does yours look the same as this... just that it says that it's not verified... I have QVFR working ok in fixed rendering mode, however because i can't enable the developer mode i can't get QVFR to work dynamically .... i.e. follow my eyes.... I know that eye tracking is enable in the headset settings under the movement tracking option, i've calibrated it and it's all working ok.... i've set it all up as per mbucchias guide.. I've included mbucchia's guide, the vey last section refers to using an OpenXr eye tracking app for testing ...... it's the last test that you do just to ensure that everything is working ok in either VD or link..... my headset is not tracking my eyes in that app... https://github.com/mbucchia/OpenXR-Eye-Trackers/wiki/Meta-Quest-Pro#with-virtual-desktop The whole point of me buying the Quest Pro was to use the eye tracking functionality so that i could use Dynamic QVFR ... at the moment i've achieved nothing more than to spend £500 for a headset that's doing exactly the same job as my Quest 3 ..... very vexing .. I have to get that option to turn on developer mode in the headset settings for it to work !!!!. I just don't know how to fix this, the Meta account system is mind blowing .... watching the Youtube videos i should be able to configure Meta developer app in 1 minute 40 seconds, it looks so straight forward...

markturner1960 This is how my app looks, normally where the the picture is it says that it's connected (my headset was turned off when i took this screenshot). Wnen the headset is turned on the "Headset setting" icon is highlighted, if i click on it then it takes me settings menu.. when i click on the developer mode icon i should then see an option to turn enable developer mode..... i don't have that option available and so i can't turn on head tracking in VD. Are you located in the UK ??, i can't talk to at the moment but we could maybe organise a time ...... i'll PM you..

Yeah it's the official Meta Quest app off play store on my phone... i've tried uninstalling it and downloading it again today... version 240.0.0.4.115

This is what i'm seeing under headset settings... I have the developer option but when i click on it i only have the debug mode that i can toggle on and off.... the picture five posts back is what i can see. after i have clicked the developer mode option below...

How did you create a new account, do you mean adding another account on your headset using app share....... i'm getting really confused and at a loss with how the meta accounts work....

It's a no go at the moment:- 1) I can't enable developer mode on my mobile meta quest app. 2) I can't tick the "forward face/eye tracking to the PC" checkbox in the Virtual Desktop app. Until i can do the first one...... nothing is gonna happen ....

I'm getting nowhere with the accounts, extremely fustrating. I used side quest a couple of years back on my Quest 2 so i would have had to have developer access. Watching Youtube videos this should only take me a couple of minutes to do... It looks like my current account is verified ??... However on the mobile app under developer i don't have the option to turn developer mode on.... only have debug option available.. You created a whole new meta account, i might have to try and see if that works...

I wouldn't really say that the Quest 3 is a big upgrade over the PICO 4 as they are quiet similar, the PICO 4 offers much better value for money. Personally i have chosen to keep the Quest 3 as i prefer the screen, i just think it has better colours and they just seem to "pop" out more. In comparison to my eyes at least the PICO 4 screen just looked so bland. Unfortunately the comfort of the Quest 3 out of the box is terrible, i've bought the elite strap and i'm waiting on somebody to make a decent comfortable facial mask. The vertical FOV is also slightly less, hopefully when i eventually get a better facial mask that might improve slightly..... the stock mask is just to hard to strap on to you face with any force. If you have the computing/graphical horse power and a good router than the Quest 3 is capable of delivering beautiful scenes and is working really well with the new VDXR runtime and fixed foveated rendering. If you decide to get one, maybe buy it from amazon and return it if you don't like it...

Appreciate your help, i'm googling stuff and people are saying that you need to input your credit card details to verify a meta developers account.... i'm going around in circles here

Sorry about all the big pictures, do i need to verify myself by providing my passport, driving licence details ??.. The headset is paired, registered and synced to the mobile app ok ...... it knows it's serial number and details...

I don't have the option at all.... it's not there. The only option that i have to turn on under the "Developer Settings" tab is "Debug mode"..... no other options exist Not 100% sure that i even have a developers account, the link that mbucchia provides me takes me to the web pages below..... judging by my icon in the top right corner i must have created a devoloper account two or three years ago when i had a Quest 2 ... i certainly have a profile..

In the mobile app under headset settings, i don't have the option turn to turn on Developer mode, i'm guessing that it's not happy with my developer account...

Sure will, it was delivered around three hours ago and i've tried it in DCS and it looks really nice ..... the slightly lower resolution is really not immediately noticeable.... colours are nice... However i'm struggling setting up the eye tracking :- I'm using mbucchia Quest pro eye tracking guide for virtual desktop https://github.com/mbucchia/OpenXR-Eye-Trackers/wiki/Meta-Quest-Pro, i've installed the required eye tracking software I've enabled eye tracking on the quest pro headset and have done the calibration, tested it and it's working ok. When i tick the "forward face/eye tracking to the PC" checkbox within the Virtual Desktop app it initially asked me for my consent to use eye tracking, when i clicked yes it than unticked itself. When i try and click on the above checkbox again, the tick disappears again after about 0.5 seconds. So i'm stuck at the moment trying to enable the "forward face/eye tracking to the PC" option within VD ???. Secondly, i have my router located right next to my computer and previously with the PICO 4 and Quest 3 i have turned off the headsets WiFI and used an ethernet to USB C convertor hub instead which also allows me to charge the headset. The Quest Pro is not recognising my wired internet connection via my ethernet to USB C hub...... is it possible to do this with the Quest Pro ??. This headset is very new to me so i'm obviously missing something, so i'll need to read his setting up guide again when i have more time. Possibly thinking that it's something to do with enabling "developer mode" for the eye tracking, but any advice is much appreciated edit.... the way the guide reads, developer mode is not required for Virtual desktop....

The PICO 4 is an excellent headset, reluctant to let it go as i have fitted a third party face interface and fitted an after market head strap and mine is really comfortable to wear.... however it's listed on ebay now.... I just couldn't justify keeping both as their quiet similar, so i decided to keep the Quest 3 for non flight sim stuff, mainly half life Alyx, table tennis and some other daft standalone games .. Hopefully the Quest Pro will provide some happy flight simming for a year or so and then maybe i'll consider one of the premium headsets .... we'll see...

I've owned both the the Reverb G1 and G2, and in their time they were both excellent headsets. However since i've now had a taste of the pancake lenses on both the PICO 4 and Quest 3, i just can't go back to Fresnel lenses again. I've decided to sell the PICO 4 and keep the Quest 3 as in my opinion the colours just seem to pop out more on the Quest 3 and the display just feels warmer..... With the Quest 3 i've had to sacifice a little FOV, buy an elite strap and the comfort of the facial interface is awful but hopefully that will be rectified once a decent third party facial interface becomes available. I've gone ahead and bought the second hand Quest Pro, i've not received it yet but the price i've paid for it i could easily sell it on again for the same price if in the unlikely event that i just didn't like it...