Meta Quest Pro Settings

[DirtyMike0330]

2 hours ago, YoYo said:

Thx, I have to install OTT, Im using only ODT but I noticed that it doesnt remember settings (not always).

I'm on Link cable of course. One more thing puzzles me, but I honestly haven't had time to test it. Perhaps you know the answer?

It's about the ground textures, the ones further away, which at these settings (as in the screenshot below) seem more blurred. While it is not so visible in DCS (but this effect is present as well), it is more visible in IL-2 BoX, e.g. However, interestingly, the Default settings of QPro hasnt this effect. The textures on the horizon are not that blurry. Theoretically, it should be the other way around . There's probably some culprit for that, but I don't know what.

It's not a big problem, but the fact that with the HP G2 the textures were sharper.

I'm interested in your findings here if you decide to try to figure out what specific setting is causing the blurriness for you. 

[DirtyMike0330]

2 hours ago, slughead said:

As for your blurriness.... you've answered your own question. You said it doesn't happen with default settings. That means something you've changed has caused this. Go back to default, and make one change at a time to isolate what has caused it.

Interesting comment on link sharpening and the encode resolution here: 

 

I’ll have to try enabling/disabling the link sharpening while in headset today and see how it actually affects anything on the horizon. The 3600 vs 3905 debate is also interesting. 

[slughead]

1 hour ago, DirtyMike0330 said:

Interesting comment on link sharpening and the encode resolution here: 

 

I’ll have to try enabling/disabling the link sharpening while in headset today and see how it actually affects anything on the horizon. The 3600 vs 3905 debate is also interesting. 

Why not just leave the encoder width at default? Other than that, I have said in another thread that setting the encoder width greater than the resolution width of the headset is a pointless waste of processing power that's better used for extra headroom or visual features.

Besides, this is the encoder resolution, not the render resolution. Encoder resolution is the streaming resolution - the image you are sending across the link. Render resolution is the image that the application generates. Setting the encoder resolution low would cause blurriness. Setting it higher won't make any difference to the visual quality. That's governed by the render resolution.

FWIW, I run the encoder resolution width at default, i.e., 0. I also run with dynamic bit rate at default settings.

Edited June 5, 2023 by slughead

[markturner1960]

1 hour ago, DirtyMike0330 said:

I'm interested in your findings here if you decide to try to figure out what specific setting is causing the blurriness for you. 

Plus one as I also notice some indistinct textures at distance.......may be related to draw distance, will need to look, but was not an issue with my G2.....

[YoYo]

I made a dedicated throne for QPro :

G2 was hanging but QP must sit at the station.

Edited June 5, 2023 by YoYo

[slughead]

What's the lowest FOV that people are running at? I'm currently at 0.75. I can see the top edge of the image when looking straight up (head up, eyes up) so this will be noticeable in turning fights. At 0.6 the edge is visible all the time. I can see the top edge at most FOV reduction values so it's a tradeoff of fps vs some loss of realism in certain head positions.

The fps improvement is significant though, so much so that I've also enabled turbo mode in the OpenXR Toolkit and have a good 18% GPU headroom with all settings maxed out in DCS. (4090, 13900k). In Caucus I'm maintaining 72fps and rarely dipped into ASW flying fast, low and turning over cities. Yet to test on other theatres which we know will zap the fps.

[DirtyMike0330]

3 hours ago, slughead said:

What's the lowest FOV that people are running at? I'm currently at 0.75. I can see the top edge of the image when looking straight up (head up, eyes up) so this will be noticeable in turning fights. At 0.6 the edge is visible all the time. I can see the top edge at most FOV reduction values so it's a tradeoff of fps vs some loss of realism in certain head positions.

The fps improvement is significant though, so much so that I've also enabled turbo mode in the OpenXR Toolkit and have a good 18% GPU headroom with all settings maxed out in DCS. (4090, 13900k). In Caucus I'm maintaining 72fps and rarely dipped into ASW flying fast, low and turning over cities. Yet to test on other theatres which we know will zap the fps.

I’ve only tried .87 so far and only on Enigma’s Cold War, where I’m able to maintain 90fps with all high+ settings. I need to see how it fares on other maps and maybe something like the Hoggit server as well. We both have 4090s and comparable CPUs, I’m surprised you’re not easily hitting 90 on Caucasus  

[slughead]

1 minute ago, DirtyMike0330 said:

I’ve only tried .87 so far and only on Enigma’s Cold War, where I’m able to maintain 90fps with all high+ settings. I need to see how it fares on other maps and maybe something like the Hoggit server as well. We both have 4090s and comparable CPUs, I’m surprised you’re not easily hitting 90 on Caucasus  

I haven’t tried 90Hz yet. The frame timings look ok for it though but I prefer to have the extra headroom.

[markturner1960]

.8 for me…… I don’t want to lose any visual real estate!

[some1]

Openxr toolkit has a similar feature that works with any headset, you can adjust fov in real time and see how low you can get before you start seeing screen edges.

Difference is, IIRC openxr increases pixel density for the visible part instead of simply shutting down pixels, so this setting does not improve fps, but image quality.

[YoYo]

Guys, a slightly different question. In general, I like QP more and more, there is one technical thing that I don't like. Namely, when I take off the headset that works, it immediately goes into sleep mode. If I put it back on after 2-5 minutes, for example, there is a half chance that something will hang (take off the headset, e.g. when flying in DCS in VR mode, sometimes it's ok, sometimes it causes CTD). Any idea to stop the goggles from going into sleep mode right away? Is there any way to turn it off or delay it? I'm on link cable. There is some sensor that causes this sleep mode.

[slughead]

1 minute ago, YoYo said:

Guys, a slightly different question. In general, I like QP more and more, there is one technical thing that I don't like. Namely, when I take off the headset that works, it immediately goes into sleep mode. If I put it back on after 2-5 minutes, for example, there is a half chance that something will hang (take off the headset, e.g. when flying in DCS in VR mode, sometimes it's ok, sometimes it causes CTD). Any idea to stop the goggles from going into sleep mode right away? Is there any way to turn it off or delay it? I'm on link cable. There is some sensor that causes this sleep mode.

There’s a setting in the Oculus config for this. Might be in the developer settings in the headset or pc app.

Yup, in the headset under power settings.

[YoYo]

Thanks for guiding, that's probably it (example from Q2), and in these "without cable" options I didn't play too much yet ;), thanks.

Different solution: https://levelup.gitconnected.com/how-to-keep-your-oculus-quest-2-from-going-to-sleep-when-you-take-it-off-8cfb4b661248.

Edited June 6, 2023 by YoYo

[slughead]

A few people have mentioned the QP audio quality is poor. Have you tried placing your hands on either side of your ears? It makes a huge difference. You can get some clip-on cups that mimic the effect. Or DIY some card and clips.

Meta Quest Pro Audio Booster and Top Strap Comfort Mod also - Etsy UK

You can also get these... I haven't tried them. Stereo VR Headphones Custom Made for Meta Quest Pro-Fully Immersive Improved Audio Experience with Deep Bass 3D 360 Degree Drivers - Clip On Design Easy to Install and Remove: Amazon.co.uk: Electronics & Photo

[skywalker22]

9 minutes ago, slughead said:

A few people have mentioned the QP audio quality is poor. Have you tried placing your hands on either side of your ears? It makes a huge difference. You can get some clip-on cups that mimic the effect. Or DIY some card and clips.

Meta Quest Pro Audio Booster and Top Strap Comfort Mod also - Etsy UK

You can also get these... I haven't tried them. Stereo VR Headphones Custom Made for Meta Quest Pro-Fully Immersive Improved Audio Experience with Deep Bass 3D 360 Degree Drivers - Clip On Design Easy to Install and Remove: Amazon.co.uk: Electronics & Photo

I use my own headphones (hyperX II) over vr headset, its tight, but it can be done that's comfortable.

[slughead]

I just tried the optional Oculus earbuds. They're not bad to be fair.

[freehand]

I don't mind the sound except for big explosion's which could do with little more boom. 

I like placing friends in VR standing on the ground during a replay and see them jump when the **** hits the fan lol.

Edited June 6, 2023 by freehand

[sea2sky]

Can someone confirm that it is enough to use either OTT or ODT alone please? I prefer OTT, but got an impression that some settings (particularly FOV) don't get applied until I run ODT on top of OTT.

[nikoel]

3 hours ago, sea2sky said:

Can someone confirm that it is enough to use either OTT or ODT alone please? I prefer OTT, but got an impression that some settings (particularly FOV) don't get applied until I run ODT on top of OTT.

I can only speak for myself but I use one tool alone that’s ODT as it’s first party. The length of time that has passed since OTT was updated doesn’t stand well with me

Additionally I see some people have all kinds of multipliers everywhere thinking they are doing some magic voodoo bs to channel more pixel density without the cost to performance. They set 1.3x inside oculus, then 1.5x inside the the debug then 0.6 value inside OpenXR Toolkit and I’m sure there is someone out there who also had a fiddle with the DCS Pixel Density as well. Their graphics card fans spin up before launching the stupid game because it’s too busy computing the end resolution value which was equal to the one they started with 

 

Edited June 7, 2023 by nikoel

[YoYo]

5 hours ago, sea2sky said:

Can someone confirm that it is enough to use either OTT or ODT alone please? I prefer OTT, but got an impression that some settings (particularly FOV) don't get applied until I run ODT on top of OTT.

The biggest problem of ODT is that this software doesnt remember part of settings (Service corner), so it needs to look everytime after restart of Windows if you want to use VR mode. Btw. You have ODT right now (its a part of Oculus soft) OTT is a separate download.

[slughead]

5 hours ago, nikoel said:

Additionally I see some people have all kinds of multipliers everywhere thinking they are doing some magic voodoo bs

Yes, it's very entertaining reading it 

[TZeer]

7 hours ago, slughead said:

Yes, it's very entertaining reading it 

Or they leave the resolution at standard in the occulus software, just to fire up the ODT 2 sec later and pushing the multiplier...

 

[skywalker22]

An issue to resolve: when dogfighting, flying in one circle fight, and when having the other aircraft on the edge of my visible sight, aircraft is not a clean one, but it's ghosting. Didn't have that issue with Reverb G2 before. Maybe it is just some setting. Anyone noticed that, and maybe even fix it?

[skywalker22]

Also another issue, some artifacts started to appear at the bottom of the lenses. Is that white line, and bellow it is all more white (that whiteness takes about up to 40% of the whole width of the lenses at the bottom. Anyone see anything like it before?

This is how it looks like (picture taken in msfs):

null

[slughead]

1 minute ago, skywalker22 said:

Also another issue, some artifacts started to appear at the bottom of the lenses. Is that white line, and bellow it is all more white (that whiteness takes about up to 40% of the whole width of the lenses at the bottom. Anyone see anything like it before?

This is how it looks like (picture taken in msfs):

null

Yes. Have you changed the settings from default in the ODT?