Meta Quest Pro Settings

[markturner1960]

Yes, it is. On mine, I dont need to turn it off, I just use the link cable, this one, https://www.amazon.co.uk/JSAUX-Compatible-Accessories-Powered-VR-White/dp/B0BM93GWF1/ref=asc_df_B0BM93GWF1/?tag=googshopuk-21&linkCode=df0&hvadid=641590092677&hvpos=&hvnetw=g&hvrand=11004870776423324534&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9073540&hvtargid=pla-1947951132662&psc=1&mcid=6f3d13887e93384ab1b30c8eda6a8aa5which also charges it. All data goes through the cable. I had to set the wireless up when I first installed, but it only works via wireless if you turn the cable off and airlink on AFAIK. 

Edited November 21, 2023 by markturner1960

[YoYo]

49 minutes ago, markturner1960 said:

Yes, it is. On mine, I dont need to turn it off, I just use the link cable, this one, https://www.amazon.co.uk/JSAUX-Compatible-Accessories-Powered-VR-White/dp/B0BM93GWF1/ref=asc_df_B0BM93GWF1/?tag=googshopuk-21&linkCode=df0&hvadid=641590092677&hvpos=&hvnetw=g&hvrand=11004870776423324534&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9073540&hvtargid=pla-1947951132662&psc=1&mcid=6f3d13887e93384ab1b30c8eda6a8aa5which also charges it. All data goes through the cable. I had to set the wireless up when I first installed, but it only works via wireless if you turn the cable off and airlink on AFAIK. 

 

Did you try test cable option in Oculus soft? How the result looks?

[diamond26]

58 minutes ago, markturner1960 said:

Yes, it is. On mine, I dont need to turn it off, I just use the link cable, this one, https://www.amazon.co.uk/JSAUX-Compatible-Accessories-Powered-VR-White/dp/B0BM93GWF1/ref=asc_df_B0BM93GWF1/?tag=googshopuk-21&linkCode=df0&hvadid=641590092677&hvpos=&hvnetw=g&hvrand=11004870776423324534&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9073540&hvtargid=pla-1947951132662&psc=1&mcid=6f3d13887e93384ab1b30c8eda6a8aa5which also charges it. All data goes through the cable. I had to set the wireless up when I first installed, but it only works via wireless if you turn the cable off and airlink on AFAIK. 

 

I believe @Gunnergolly asks for more than data/power USB cable, as in his message he mentions ethernet adapter and internet feed to the headset. 

[Gunnergolly]

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

Edited November 21, 2023 by Gunnergolly

[diamond26]

3 hours ago, Gunnergolly said:

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

That was actually my problem that turned me away from VD at the end. Although it has a lot of nice things, it's not able to keep framerate the way Link does and as you said ASW is much better. Fortunately I 'm happy using Oculus link both with Q2 and QPro. I don't understnad why you are able to use it with Q3 but not Qpro . When I first moved to Qpro from Q2 it worked exactly the same with better clarity. It's very strange if you want my opinion

[Mordants]

I did all the VD things for my Quest Pro and loved the graphics, however I could not get either sound or mics working correctly in SRS. Sometimes one or the other and most times I had to go into settings and play with the default sound/mic outputs. Then in DCS muck about with sound/mic inputs/outputs there. Real faff where with link cable it just works.

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

Edited November 21, 2023 by Gunnergolly

[sze5003]

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

That's odd, I have stuttering too in DCS but I didn't consider it to be the headset or oculus link itself.

Isn't h265 the default for airlink and for link cable it's h264 because it can achieve a higher bandwidth? H265 is higher quality but limited to like 200-250Mb bitrate.

Whereas h264 you can push a higher bitrate so to me it doesn't make sense that there would be no stuttering with a lower bitrate over link..also h265 will push the processor more too on the headset.

[Gunnergolly]

2 hours ago, sze5003 said:

That's odd, I have stuttering too in DCS but I didn't consider it to be the headset or oculus link itself.

Isn't h265 the default for airlink and for link cable it's h264 because it can achieve a higher bandwidth? H265 is higher quality but limited to like 200-250Mb bitrate.

Whereas h264 you can push a higher bitrate so to me it doesn't make sense that there would be no stuttering with a lower bitrate over link..also h265 will push the processor more too on the headset.

I didn't know that about the two different codecs.

That would explain when testing my QPro using AIrlink it ran smooth.... because it's using the H.265 codec

I've no idea why it's so stuttery when using the link cable with the H.264 codec .... bearing in mind that i have tested it with three different link cables, two powered ones and the expensive Oculus one..... so it's not the cable. Ive also tested the three link cables with the link speed tester and the results were all similar. 

Yeah i can only turn my bitrate up to a maximum of about 230Mb before the video breaks down using the H.265 codec over link.

On the Q3 i've had my bitrate up to 940Mb, the sound stutters but it works, so my Q3 is happily using the H.264 codec.

It get's me wondering that i must have a setting wrong somewhere because i'm able to reach whatever refresh rate i set in the Oculus PC app, but it's just not quiet syncing/locking in.... almost like i have two ASW's fighting each other causing a slight stutter and fluctuation in frames.

It's a mystery with the QPro ???...

Edited November 21, 2023 by Gunnergolly

[sze5003]

I didn't know that about the two different codecs.
That would explain when testing my QPro using AIrlink it ran smooth.... because it's using the H.265 codec
I've no idea why it's so stuttery when using the link cable with the H.264 codec .... bearing in mind that i have tested it with three different link cables, two powered ones and the expensive Oculus one..... so it's not the cable. Ive also tested the three link cables with the link speed tester and the results were all similar. 
Yeah i can only turn my bitrate up to a maximum of about 230Mb before the video breaks down using the H.265 codec over link.
On the Q3 i've had my bitrate up to 940Mb, the sound stutters but it works, so my Q3 is happily using the H.264 codec.
It get's me wondering that i must have a setting wrong somewhere because i'm able to reach whatever refresh rate i set in the Oculus PC app, but it's just not quiet syncing/locking in.... almost like i have two ASW's fighting each other causing a slight stutter and fluctuation in frames.
It's a mystery with the QPro ???...

I tried H265 on link cable with my Pro tonight. At 220 bitrate it wouldn't smoothly load oculus desktop, it would take some time and the screen would lag. It loaded DCS but it wasn't smooth at all.

I had to lower the bitrate to 200 then it was ok. It looked a little brighter maybe more detailed on the outside and the terria but cockpit text wasn't as sharp as using h264 with 500 bitrate.

I still had microstutters on h265 with link cable. When ASW kicked on and off it produced some microstutter along with a smearing effect I wouldn't see on h264. I still have microstutters with h264 codec but they seem to happen when the frame/CPU graphs spike.

I also saw microstutters in single threaded DCS even when fps seemed stable too with both codes. But I'm convinced multithreaded DCS is not using my pocesor properly as sometimes after a while it completely locks up. If I remove processor 8 from affinity it unfreezes but this doesn't happen every single time so it's bizarre.

[freehand]

The QP when I had one run wireless but did not like but ok on cable on my pico in VD runs nice even on my 10 year old router.

Edited November 22, 2023 by freehand

[markturner1960]

I am not using VD , so dont know, but can report, I use Force ASW 45 FPS in ODT, 72HZ, charging link cable I linked to above and H264 codec and 500 bitrate. I have zero stutters or audio problems, it runs lovely, no issues at all.......

[freehand]

6 hours ago, markturner1960 said:

I am not using VD , so dont know, but can report, I use Force ASW 45 FPS in ODT, 72HZ, charging link cable I linked to above and H264 codec and 500 bitrate. I have zero stutters or audio problems, it runs lovely, no issues at all.......

Yea cable is the way.

[toni]

ok, at the end I got my Pro working fine. But I see the game textures like granulated, why is that ?

[slughead]

1 hour ago, toni said:

ok, at the end I got my Pro working fine. But I see the game textures like granulated, why is that ?

You're going to need to provide more information if you want anyone to help. My crystal ball has a very limited range and can't see your settings.

[Phantom711]

vor 8 Stunden schrieb toni:

ok, at the end I got my Pro working fine. But I see the game textures like granulated, why is that ?

Do you have Link sharpening turned on?(OTT/ODT)

Or any other „Sharpening“ setting in DCS or OXR toolkit companion?

[toni]

do I need all of them to be ON ?

[Phantom711]

vor 36 Minuten schrieb toni:

do I need all of them to be ON ?

No. Sharpening causes the granulation. And they certainly add up to each other if multiple sharpening modes are on.

You have to experiment a bit and see how much sharpening you like and how much is too much.

Edited November 25, 2023 by Phantom711

[diamond26]

I prefer Oculus sharpening first because it affects everything on headset and then per application I control how much I want. For DCS I use 0.5

[YoYo]

After one of the last updates for Meta Quest Pro, I noticed a new problem (from 2-3 weeks) - I have some stutters from time to time, this is also a selective effect. I thought it was the fault of the DCS MT, which has some problems with it, but now I also fly the IL-2 and I see it too. Something like reading data but without any reading (looks like lag, kind of stutter), interestingly, CPU and GPU timings do not drop during this time, constant 72 frames (out of 72), VRAM at about 50%. As if the image was hanging on some object, it would give 15 frames, also for a fraction of a second. There is no routine here so it is impossible to determine the frequency of this. I wanted to record it and interestingly enough, when the processor in the goggles is working and recording the image, does not occur, well done. Something's probably wrong again. It's a bit like the effect of turning on ASW, but I have it turned off and don't use it. For now, I'm looking for an idea of what it could be. Has anyone encountered this?

Edited December 26, 2023 by YoYo

[diamond26]

57 minutes ago, YoYo said:

After one of the last updates for Meta Quest Pro, I noticed a new problem (from 2-3 weeks) - I have some stutters from time to time, this is also a selective effect. I thought it was the fault of the DCS MT, which has some problems with it, but now I also fly the IL-2 and I see it too. Something like reading data but without any reading (looks like lag, kind of stutter), interestingly, CPU and GPU timings do not drop during this time, constant 72 frames (out of 72), VRAM at about 50%. As if the image was hanging on some object, it would give 15 frames, also for a fraction of a second. There is no routine here so it is impossible to determine the frequency of this. I wanted to record it and interestingly enough, when the processor in the goggles is working and recording the image, does not occur, well done. Something's probably wrong again. It's a bit like the effect of turning on ASW, but I have it turned off and don't use it. For now, I'm looking for an idea of what it could be. Has anyone encountered this?

 

No I’m on the latest version and haven’t seen that.

[YoYo]

5 minutes ago, diamond26 said:

No I’m on the latest version and haven’t seen that.

I feel like I've found the solution. I think it's the Encode Bitrate option, I had 960 like before. They definitely changed something, because for a while I sometimes had the familiar raining rainbow pixel effect, known issue. It's possible that something has been solved, because I can't see it anymore from 2-3 weeks, and it was quite a serious problem. They also closed this topic on Meta forum. I reduced the Encode Bitrate to 550 and looks ok so far.

[nikoel]

16 hours ago, YoYo said:

I feel like I've found the solution. I think it's the Encode Bitrate option, I had 960 like before. They definitely changed something, because for a while I sometimes had the familiar raining rainbow pixel effect, known issue. It's possible that something has been solved, because I can't see it anymore from 2-3 weeks, and it was quite a serious problem. They also closed this topic on Meta forum. I reduced the Encode Bitrate to 550 and looks ok so far.

You must be one of the few people who know what they are doing and are not running Virtual Desktop

Give In. I have found that wireless VD over a crappy WiFi5 modem and a Ethernet Connection is better than wired link in basically every way. I can imagine a WiFi 6 connection is the next step up

[sze5003]

I have a wifi 6e connection with the pro being only item on the network. I definitely have had stutters in virtual desktop but I also get stutters using link cable with a bitrate of 500. While the microstutters could be dcs, they are intermittent, not related to lowering settings either. I noticed they still happen even with steady fps because I now use quad views foveated rendering which keeps the fps steady but the stutters are still random and intermittent. Last I checked my pro was in version 59 oculus software.

[nikoel]

35 minutes ago, sze5003 said:

I have a wifi 6e connection with the pro being only item on the network. I definitely have had stutters in virtual desktop but I also get stutters using link cable with a bitrate of 500. While the microstutters could be dcs, they are intermittent, not related to lowering settings either. I noticed they still happen even with steady fps because I now use quad views foveated rendering which keeps the fps steady but the stutters are still random and intermittent. Last I checked my pro was in version 59 oculus software.

It could be as easy as settings. You can try with Turbo on/off. Also be careful with having turbo on in multiple places that really screws everything up. (i.e. in the toolkit and the quadviews)