Meta Quest Pro Settings

[Qcumber]

1 hour ago, slughead said:

Have you guys raised this on the VD discord?

Not yet. I need to get my log then I'll upload it to Discord. It's happened to me 4 times now. 

[Qcumber]

5 hours ago, Majik said:

Another new sub £500 sealed QPro user here, loving everything about it now that I have it all dialed in, including QVFR. Much, much higher clarity than my old Reverb G1, with even slightly higher fps on my aging 9700k, 2080super PC!

I just have one problem; using VD, I fairly often get crashes in the headset, that 9 times out of 10 are unrecoverable with a VD restart in headset. The game in still running on pc, and will move with the headset, but the image is frozen in headset. I've read this can be VRAM issues, but nothing I've tried seems to alleviate this. I already run Taz's optimised texture mods, the background hanger removal mod, in-game textures are normally medium, but have tried low on both and I still get crashes. Godlike in VD gets me the best clarity and decent perf, but have also tried down to high with no luck. I can run fine sometimes for a couple hours with no issues, or get crashes loading into a server immediately. Can't find a rhyme or reason.

Could it be my connection dropping? I'm usually running anywhere from 860 to 500mbps, on a 5GHz AC connection, 20ft from the router (in a different room, but direct line of sight through open door). PC is hard wired to the router, and has always been (cable is probably nearly 20 years old at this point). My latency is usually showing orange and jumps around but often near 60ms. Using auto codec, which defaults to HEVC 10bit, and 150mbps. I wonder if a dedicated 6e router would help this situation?

Wired link gives me lower fps at a lower clarity compared to VD, so I'd like to avoid using that if possible.

Anyone experienced similar, or have any advise?

What Nvidia driver version are you using? Just seen in the VD discord that there were issues with the last version. The one released last week solved these issues. I have just updated to the latest so will see if this has solved it. 

[Majik]

8 hours ago, Qcumber said:

Glad you are enjoying the QP. I have been having the same issue recently. It's happened about 3 times the last couple of days. Not sure why. It's not been an issue for me before. 

I am maintaining 1200 Mbps, occasionally dropping lower. I think the minimum you can get away with is 860 Mbps. That might be part of your issue. I have a dedicated router next to my desk. 6e Mercusys from Amazon for £40. In terms of codecs, try using h264+ at about 200 Mbps. It has lower latency than HEVC 10 but and I can't notice any difference in DCS. 

Which version of oculus software are you using and do you have the Public Test Channel enabled? I am using PTC v65. I might try unchecking the PTC to see if that stops my freezing. 

 

Interesting, so might be new issue? I didn't setup my QP until after latest DCS patch, so have no data to compare to, either VD or DCS. I can't fully remember, but I think I was also getting crashes in Asseto Corsa and AMS2 as well in limited testing last week, so maybe it's more of a VD issue?

I'm definitely not hitting 860 very often, mostly hover around 550-700 so I'll definitely need to look into the router and some new cat cables to replace the aging ones I have. Would you happen to have a link or model number for your router, all I could find at that price point was a PCIE WIFI card?

Headset should be fully updated, so v65 I believe. Definitely don't have PTC enabled.

2 hours ago, Qcumber said:

What Nvidia driver version are you using? Just seen in the VD discord that there were issues with the last version. The one released last week solved these issues. I have just updated to the latest so will see if this has solved it. 

Oh I'm on a very old driver, 536.23. Actually dowloaded 537.58 last night, which from reading seems like the last really, really stable one (I know we're up to 552 currently). Can certainly update to latest and give it a spin though.

Appreciate all the help!

Have also joined the VD discord, will have a look there too

Edited April 24, 2024 by Majik

[Qcumber]

16 minutes ago, Majik said:

Would you happen to have a link or model number for your router, all I could find at that price point was a PCIE WIFI card?

This is the router I got but it cost £40 when I bought it. must have been a good discount. 

https://www.amazon.co.uk/Mercusys-AX1800-Dual-Band-1201Mbps-574Mbps-MR70X/dp/B09BJTR294?pd_rd_w=5LTTE&content-id=amzn1.sym.a6c1c16e-0543-4a2c-84b6-2aad76f80253&pf_rd_p=a6c1c16e-0543-4a2c-84b6-2aad76f80253&pf_rd_r=RV4G4P2PBRD3W2XNS1F5&pd_rd_wg=OvTw5&pd_rd_r=6657cfea-a7bd-4aa9-8b25-066c2c68a93d&pd_rd_i=B09BJTR294&psc=1&ref_=pd_basp_d_rpt_ba_s_1_t

It would be worth checking the VD discord for router advice too. I think the bot command is “/router”. 

 

Edited April 24, 2024 by Qcumber

[Majik]

12 minutes ago, Qcumber said:

This is the router I got but it cost £40 when I bought it. must have been a good discount. 

https://www.amazon.co.uk/Mercusys-AX1800-Dual-Band-1201Mbps-574Mbps-MR70X/dp/B09BJTR294?pd_rd_w=5LTTE&content-id=amzn1.sym.a6c1c16e-0543-4a2c-84b6-2aad76f80253&pf_rd_p=a6c1c16e-0543-4a2c-84b6-2aad76f80253&pf_rd_r=RV4G4P2PBRD3W2XNS1F5&pd_rd_wg=OvTw5&pd_rd_r=6657cfea-a7bd-4aa9-8b25-066c2c68a93d&pd_rd_i=B09BJTR294&psc=1&ref_=pd_basp_d_rpt_ba_s_1_t

It would be worth checking the VD discord for router advice too. I think the bot command is “/router”. 

 

 

Much appreciated!

Just to confirm, yours has 6e? As I understand, WiFi6 and 6e (6GHz) are not the same, but I may be wrong. Nevertheless, if it working fine for you, that's good enough for me, and certainly will be a step up.

[Qcumber]

9 minutes ago, Majik said:

Much appreciated!

Just to confirm, yours has 6e? As I understand, WiFi6 and 6e (6GHz) are not the same, but I may be wrong. Nevertheless, if it working fine for you, that's good enough for me, and certainly will be a step up.

It is wifi 6e using 5Ghz not 6Ghz. 

VD routers

Community Tested Routers

The following routers have been reported to work reliably from a number of users. High End (AXE) - TP-Link AXE300/AXE16000 ($450 US) High End (AX) - Asus RT-AX86U ($300 US) High End (AXE 6E) - Davolink 'Kevin' Minion 6E ($129 US) Dedicated (Wifi 7) - TP-Link BE9300/BE550 ($200-$300 US) Dedicated (AXE) - TP-Link Archer AXE75/AXE5400 ($160-$200 US) Low End (AC) - Opal GL-SFT1200 ($50 US) Low End (AC) - TP-Link Archer C6 or A6 ($40 US) TP-Link AX and Huawei routers have been known to have issues we are unable to identify. Higher end TP-Link AX/AXE routers not listed here may work well but as with any router not on this list, should be considered untested. The TP-Link Archer AXE5400 is not the same thing as the Deco AXE5400. The latter is a mesh router and may not work as expected.

Edited April 24, 2024 by Qcumber

[slughead]

When I tried VD, I set my Z790 motherboard's onboard Wi-Fi 6E AX210 to "mobile hotspot" mode. It seemed to work ok.

[Qcumber]

3 minutes ago, slughead said:

When I tried VD, I set my Z790 motherboard's onboard Wi-Fi 6E AX210 to "mobile hotspot" mode. It seemed to work ok.

I think this can work but is not officially supported by VD. They require an Ethernet connection to a router. 

[slughead]

Just now, Qcumber said:

I think this can work but is not officially supported by VD. They require an Ethernet connection to a router. 

Only if using a router would you need ethernet to it so that you get maximum throughput to the router and then across WiFi to the headset.

If using a hotspot on your motherboard, your PC is already directly connected to the WiFi transmitter via the motherboard. It's all about maximum data throughput to the headset and reducing latency. If you had WiFi to the router and then WiFi to the headset, the latency would be doubled.

[Tophatter14]

On 4/20/2024 at 8:18 AM, Tea-Pig said:

There seem to be a lot of apparently new and sealed QPros for sale in the UK at the moment for around £500ish (half what Meta UK are charging), so I picked one up to replace my G2 and have been setting it up with lots of help from this thread. So far I'm loving the quality of the visuals, not hugely loving the comfort, and not loving at all the bloated, intrusive META crap that comes with it. Part of that crap is the infuriating controller pop-ups. 

So far my research has only come up with keep the controllers on the charging dock or turn them off by holding the menu button for at least ten seconds. This seems to get rid of the pop-ups in game but there's still an even bigger one plastered over the PC link dashboard saying the controllers can't be found. I've even un-paired the controllers and this pop-up persists. Also there seems to be no way to interact with the link dashboard without the controllers. I can use hand tracking to start the link off but only the controllers seem to be able to click that one stupid button needed to show the PC desktop. I was wondering if a Bluetooth mouse might be able to click that button but presumably the stupid pop-up would remain. 

How are people here dealing with these pesky controllers?

A recent update allows you to  ‘clap your hands’ together, which causes the controllers to temporarily disappear/sleep.  Just lightly double tap them together and they should go away as if you turned them off.

[4romeodelta]

On 3/18/2023 at 7:34 PM, Tepnox said:

Quest Pro user here, these are my settings for RTX4090 (was using RTX3080TI and RTX3090 prior):

First: Baseline for your optimiziation should be Oculus Home Settings:

I was running my Quest Pro prior on RTX3090, your RTX3080Ti is similar in GPU-power. I would recommend 80 Hz there.

OTT Settings next:

I would recommend 1.0 in OTT and 1.0 in DCS itself for your GPU. Beware: Since latest OpenBeta on OpenXR, the OTT settings are a multiplier on top of your DCS setting.

Quest Link settings (via Cable):

Again: I would recommend Encode Bitrate max. 500 Mbit on RTX3080Ti. I was getting weird image interruptions above that setting. (not the case on RTX4090).

Ingame DCS settings:

Because the RTX3080Ti only has 12 GB VRAM, it is necessary for VR to get Textures to Medium. If you plan on playing Multiplayer I would also recommend Terrain Textures on Low.

Otherwise you will get alot of stuttering because of too much GPU VRAM usage. It was a pain in the ass to sort this out on my RTX3080Ti.

Visibility Range is another option you could lower to High - personal preference. Another boost is Terrain Object Shadows to Off - again personal preference. It really depends on what map you fly and how busy your surrounding area is.

DCS VR Tab:

In addition to that, I run the OpenXR Toolkit having CAS (Sharpening) enabled with 70% and a custom Fixed Foveated rendering (I am not running the DCS HMD Mask - the mask size i not correct for Quest Pro). Give it a try.

Happy flying. Loving my Quest Pro so far, the edge to edge clarity is a wonder and no more screen door effect - coming from Rift S too ;D

 

Tepnox, 

Thanks so much for this info. Your suggested OTT settings drastically improved my Q3 image quality and FPS. Cheers!

[muzica9]

Hi guys!

I’m considering buying a Quest Pro after testing the Quest 3 for a few days, which left me disappointed. My main problems were:

1. Sleep Mode Issue: If you took the headset off, it went to sleep, and most of the time DCS crashed. I had to go into the Oculus Debug Tool every time to enable the "Bypass Sensor" option. If I forgot to check it, my DCS session was gone.

2. Microphone Quality: The microphone was very bad. I use VoiceAttack for commands, but I couldn’t get it to work properly with the headset. Even after hours of voice training, it failed to recognize commands, and I kept getting a constant low signal/red notification.

I’d like to know if these two issues also occur with the Quest Pro so I can avoid a potential return and save time.

PS: I plan to use the Quest Pro exclusively via Link Cable, as VR Desktop is not an option for me.

 

Edited December 21, 2024 by muzica9

[slughead]

Bypass Sensor - sadly, it doesn't stop it from sleeping for either headset.

If you install the Quad Views Foveated Rendering tool, it fixes the sleep problem. You can use the QVFR tool without the QVFR functionality enabled and still benefit from the sleep fix. Alternatively, you can use Virtual Desktop instead of the Meta Link, which I think also fixes the problem, but I note you say it is not an option for you. Maybe if you expand on your reason, we can offer a solution.

I can't speak for the microphone as I've never used it on my Quest Pro.

[muzica9]

I used the Quest 3 with the Quad Views Foveated Rendering app in fixed mode, which did give a noticeable FPS boost. However, the sleep issue was still present, so that didn’t solve the problem.
Is there any setting that needs to be added to settings.cfg to bypass the sensor/sleep or is just default.

Edited December 21, 2024 by muzica9

[slughead]

3 minutes ago, muzica9 said:

Is there any setting that needs to be added to settings.cfg to bypass the sensor/sleep or is just default.

There's nothing else you can do other than covering the sensor with tape. The problem is within DCS itself.

[Qcumber]

44 minutes ago, muzica9 said:

Hi guys!

I’m considering buying a Quest Pro after testing the Quest 3 for a few days, which left me disappointed. My main problems were:

1. Sleep Mode Issue: If you took the headset off, it went to sleep, and most of the time DCS crashed. I had to go into the Oculus Debug Tool every time to enable the "Bypass Sensor" option. If I forgot to check it, my DCS session was gone.

2. Microphone Quality: The microphone was very bad. I use VoiceAttack for commands, but I couldn’t get it to work properly with the headset. Even after hours of voice training, it failed to recognize commands, and I kept getting a constant low signal/red notification.

I’d like to know if these two issues also occur with the Quest Pro so I can avoid a potential return and save time.

PS: I plan to use the Quest Pro exclusively via Link Cable, as VR Desktop is not an option for me.

 

I have no issues with the headset going to sleep. I have QVFR installed as this was the main reason I got to QP.

I don't use the microphone so couldn't comment. 

You can pick one up for the same price (or less) than a Q3 now. It is the only "budget" option for DFR now. 

[muzica9]

Not quite. Quest Pro is €1100 new, while Quest 3 is €550 new. However, Quest 3 was very frustrating for me, so price is not an issue at the moment. I just want those functions to work so I can use them properly.

[diamond26]

I have no issue with Qpro and its microphone. Nobody mentioned any issues while we are flying together using Qpro microphone.

The sleep issue seems to be more proinent in Q3 (from friends reports) for whatever reason. In Qpro I don't have this problem (I'm using Quad Views)

Edited December 23, 2024 by diamond26

[Qcumber]

28 minutes ago, muzica9 said:

Not quite. Quest Pro is €1100 new, while Quest 3 is €550 new. However, Quest 3 was very frustrating for me, so price is not an issue at the moment. I just want those functions to work so I can use them properly.

I got my QP for £300 used but immaculate. You can get new ones on eBay for about £400-550. Last time I looked anyway, but that was a few months ago. 

[Porkbrain]

1 hour ago, muzica9 said:

Hi guys!

I’m considering buying a Quest Pro after testing the Quest 3 for a few days, which left me disappointed. My main problems were:

1. Sleep Mode Issue: If you took the headset off, it went to sleep, and most of the time DCS crashed. I had to go into the Oculus Debug Tool every time to enable the "Bypass Sensor" option. If I forgot to check it, my DCS session was gone.

2. Microphone Quality: The microphone was very bad. I use VoiceAttack for commands, but I couldn’t get it to work properly with the headset. Even after hours of voice training, it failed to recognize commands, and I kept getting a constant low signal/red notification.

I’d like to know if these two issues also occur with the Quest Pro so I can avoid a potential return and save time.

PS: I plan to use the Quest Pro exclusively via Link Cable, as VR Desktop is not an option for me.

 

In the main Settings menu for the headset, under Power, I've set the Display off item to 15 minutes which works fine for a short break and I use that both with Link cable, when using a joystick and also with the Oculus Air Link, (not VR Desktop), when using a collective.

I also had used Voice Attack extensively when I used a Valve Index headset which worked really well and was annoyed to find that the Quest Pro microphone was duff, with the same low signal notification in VA.  In Windows audio settings the microphone levels would never get past the 50% level and the Meta Help(less) forums had many logs re this with none of them resolved by the Meta support bots.

I tried a boom desktop mike but minor noise levels in the room made recognition iffy, finally got it working with a clip on Lavalier wireless mic setup, which works fine after taking off the 'wind' foam cover, and was only £15. 

This was the only one that I found that works with a PC rather than just with a mobile phone https://www.amazon.co.uk/gp/product/B0CWXRG77S/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

 

[muzica9]

35 minutes ago, Porkbrain said:

I also had used Voice Attack extensively when I used a Valve Index headset which worked really well and was annoyed to find that the Quest Pro microphone was duff, with the same low signal notification in VA.  In Windows audio settings the microphone levels would never get past the 50% level and the Meta Help(less) forums had many logs re this with none of them resolved by the Meta support bots.

 

 

 

So, confirmation that Quest Pro suffer from the same problem in VoiceAttack as I experienced with the Quest 3. Low signal notifications leading to commands not being executed. From what I understand, the problem comes from Meta's noise-canceling implementation, which Meta does not want to change or allow us to modify

Edited December 21, 2024 by muzica9

[Tophatter14]

On 12/21/2024 at 5:22 AM, diamond26 said:

I have no issue with Qpro and its microphone. Nobody mentioned any issues while we aref lying together usuing Qpro microphone.

The sleep issue seems to be more proinent in Q3 (from friends reports) for whatever reason. In Qpro I don't have this problem (I'm using Quad Views)

Same here, identical experience.  

[slughead]

I just tried the mic on my QP. Seems ok to me.

[Porkbrain]

Please don't think that I was in some way knocking the Pro - I think it's a superb headset, great visuals and no mask clamped to my face.

The mics on both of my Quest Pros do work, it is the volume setting that is the problem when using Voice attack recognition.

I have not found a way to increase their recording sensitivity settings in Windows to more than 50%

With my old Valve Index headset it was quite rare to have to repeat a spoken command that wasn't recognised the first time, unless my neighbour started to mow his lawn which dropped the recognition hit rate to unusable.

Sounds from the Index's over ear speakers did not prevent recognition even on outside loud afterburner views,

The Pro only worked reliably if I turned down the volume in the DCS audio settings to just audible, which is no fun when I could barely hear radio calls, engine & cockpit sounds etc., as the sounds from the Pro's own speakers prevented the mic from passing recognisable phrases to Voice Attack.

Using the clip on mic that I bought solves that and I can now use Voice Attack for all commands that I don't want to set on Hotas, until next summer.

[slughead]

2 minutes ago, Porkbrain said:

The Pro only worked reliably if I turned down the volume in the DCS audio settings to just audible

Did you consider using the earbuds for the QPro?