Meta Quest Pro Settings

[FupDuck]

On 10/26/2023 at 9:09 PM, halufpv said:

 

The one thing I'm not too happy about is the local dimming. The halo around bright objects against a dark background is very noticeable. This is specially bad with the HMD (tried both F16 and F18), as it makes it look as though there's a moon behind a cloud anywhere you look at. With a starry night (I tried persion gulf case 3 recovery in instant action), the whole of the sky has a bloom to it, as any star causes the entire area around it to light up. What's even more disappointing is that turning local dimming off just makes everything light up completely, as if I had turned up the brightness on the display to "overdrive" and light is leaking all over the place. It almost feels as if local dimming is a technology designed to try to mask the shortcomings of the panel, e.g turn off some of the lights when there's nothing there because it leaks so much it's otherwise terrible. This is a non-issue during day though.

 

I'm also not impressed with the comfort, but I'll buy the globular cluster comfort kit and hopefully it'll fix the issue.

 

 

 

These have been my two main beefs as well. With everyone raving about the local dimming, I was very shocked by how bad this halo effect was. I have a bunch of night missions that I used to play with my Quest 2, and in that the black levels aren't great, but you can easily see the stars and there's no glare around my instruments, etc. With the Quest Pro, it's a foggy mess. Like it literally looks like one of those London fog nights from Sherlock Holmes. It's the one thing that's making me think about returning it. I bought two, and they both had the same identical problems with the black levels. Everything else besides that is superior to the Quest 3, which I also bought (except maybe the passthrough, but I never use it). The lenses, clarity, colours, build quality, brightness, FOV, etc are all better on the Pro. Just not the black levels. 

Oh and my left controller is constantly randomly floating away into space. Anything I can do about that? I already tried cranking up the lighting, didn't help much...

[nikoel]

10 hours ago, FupDuck said:

These have been my two main beefs as well. With everyone raving about the local dimming, I was very shocked by how bad this halo effect was. I have a bunch of night missions that I used to play with my Quest 2, and in that the black levels aren't great, but you can easily see the stars and there's no glare around my instruments, etc. With the Quest Pro, it's a foggy mess. Like it literally looks like one of those London fog nights from Sherlock Holmes. It's the one thing that's making me think about returning it. I bought two, and they both had the same identical problems with the black levels. Everything else besides that is superior to the Quest 3, which I also bought (except maybe the passthrough, but I never use it). The lenses, clarity, colours, build quality, brightness, FOV, etc are all better on the Pro. Just not the black levels. 

Oh and my left controller is constantly randomly floating away into space. Anything I can do about that? I already tried cranking up the lighting, didn't help much...

Put cradle on desk. Plug cradle into power supply. Put Controller inside [on top?] cradle. Profit.

Edited November 3, 2023 by nikoel

[YoYo]

Today, at least for me, I received a firmware update (looks like, a slightly different icon, something like a loading BIOS at the beginning). I wonder what this update brought. For now, I have the impression that there are more arcetafacts that I didn't have before (flying pixels ) but I definitely need to test it more.

[halufpv]

On 11/2/2023 at 8:36 PM, FupDuck said:

These have been my two main beefs as well. With everyone raving about the local dimming, I was very shocked by how bad this halo effect was. I have a bunch of night missions that I used to play with my Quest 2, and in that the black levels aren't great, but you can easily see the stars and there's no glare around my instruments, etc. With the Quest Pro, it's a foggy mess. Like it literally looks like one of those London fog nights from Sherlock Holmes. It's the one thing that's making me think about returning it. I bought two, and they both had the same identical problems with the black levels. Everything else besides that is superior to the Quest 3, which I also bought (except maybe the passthrough, but I never use it). The lenses, clarity, colours, build quality, brightness, FOV, etc are all better on the Pro. Just not the black levels. 

Oh and my left controller is constantly randomly floating away into space. Anything I can do about that? I already tried cranking up the lighting, didn't help much...

You know sometimes reviewers talk crap without actually trying it, in this case the source of "the pro is great at night" is 1 youtube video so for all I know they were just "assuming" based on specs. For me it's not as bad as "london foggy night" though I definitely get you, it's like that only on the edges. I find adjusting the position of the headset changes it and being as close as possible to the lens almost gets rid of it, but it's not viable to wear the headset like that, because of the way it only grabs onto you on your forehead getting the lens really close involves tilting it downwards so the back part of it is not really where it's comfortable if you know what I mean, but you could wear it like that for a while if it's just a night mission here and then

Edited November 3, 2023 by halufpv

[Werewolf_fs]

I have been lucky enough to test almost all the vr devices on the market since 2017, (except Varjo) and this Quest Pro is the one with the best black on an LCD screen and the best night in DCS by far, it is not perfect, but it is the better than I've ever seen.

I don't see that foggy mess, neither do I nor several of my colleagues who also have the Pro, I hope it's a possible configuration problem, because it doesn't make sense. Although tit is true that VR  has a lot of subjective and physiological assessments that make the experience very different for each person.

[YoYo]

18 hours ago, YoYo said:

Today, at least for me, I received a firmware update (looks like, a slightly different icon, something like a loading BIOS at the beginning). I wonder what this update brought. For now, I have the impression that there are more arcetafacts that I didn't have before (flying pixels ) but I definitely need to test it more.

Looks like not only me noticed more rainbow’s pixels after the last update: https://communityforums.atmeta.com/t5/Get-Help/PTC-v56-57-Flashing-white-colored-pixel-artifact-problem/m-p/1098541/highlight/true#M240439 . 

Edited November 4, 2023 by YoYo

[sze5003]

Looks like not only me noticed more rainbow’s pixels after the last update: https://communityforums.atmeta.com/t5/Get-Help/PTC-v56-57-Flashing-white-colored-pixel-artifact-problem/m-p/1098541/highlight/true#M240439 . 

This is visible to me too on my quest pro using virtual desktop mostly. Not so much in link cable or air link.

[slughead]

6 minutes ago, sze5003 said:

12 minutes ago, YoYo said:

Looks like not only me noticed more rainbow’s pixels after the last update: https://communityforums.atmeta.com/t5/Get-Help/PTC-v56-57-Flashing-white-colored-pixel-artifact-problem/m-p/1098541/highlight/true#M240439 . 

This is visible to me too on my quest pro using virtual desktop mostly. Not so much in link cable or air link.

Yes, I have only seen this using virtual desktop. I thought I'd try VD, it's pants. I'm back on Oculus Link.

[sze5003]

Yes, I have only seen this using virtual desktop. I thought I'd try VD, it's pants. I'm back on Oculus Link.

Devs of virtual desktop said it's a meta bug from a software update introduced a while ago. It's also apparent on quest 3. If you use virtual desktop and use high settings on there vs god mode or ultra it should reduce the sparkles.

[slughead]

I'm sticking with Oculus Link.

[Werewolf_fs]

hace 22 minutos, YoYo dijo:

Parece que no solo yo noté más píxeles de arcoíris después de la última actualización:  https://communityforums.atmeta.com/t5/Get-Help/PTC-v56-57-Flashing-white-colored-pixel-artifact-problem/mp/ 1098541/resaltado/verdadero#M240439  . 

 

There are also more sound cuts than with the previous version.

[YoYo]

16 hours ago, sze5003 said:

16 hours ago, YoYo said:

Looks like not only me noticed more rainbow’s pixels after the last update: https://communityforums.atmeta.com/t5/Get-Help/PTC-v56-57-Flashing-white-colored-pixel-artifact-problem/m-p/1098541/highlight/true#M240439 . 

This is visible to me too on my quest pro using virtual desktop mostly. Not so much in link cable or air link.

I'm on Link only and while it was practically non-existent before, with this v.59 update there is more of it.

I think it's something to do with codeck or bitrate, I had 264, I'll try 265:

Edit: with H.265 I see black screen only, no any picture with LinkCable.

Edited November 5, 2023 by YoYo

[FupDuck]

On 11/3/2023 at 3:18 AM, nikoel said:

Put cradle on desk. Plug cradle into power supply. Put Controller inside [on top?] cradle. Profit.

 

My controllers are fully charged. Just took them out of [off of?] the cradle, which is plugged into the power supply. Sorry, no profit...

22 hours ago, halufpv said:

You know sometimes reviewers talk crap without actually trying it, in this case the source of "the pro is great at night" is 1 youtube video so for all I know they were just "assuming" based on specs. For me it's not as bad as "london foggy night" though I definitely get you, it's like that only on the edges. I find adjusting the position of the headset changes it and being as close as possible to the lens almost gets rid of it, but it's not viable to wear the headset like that, because of the way it only grabs onto you on your forehead getting the lens really close involves tilting it downwards so the back part of it is not really where it's comfortable if you know what I mean, but you could wear it like that for a while if it's just a night mission here and then

 

I have also noticed that the dark screen performance can be improved a lot by adjusting the position of the headset, and the best position is just as you describe it. But that mainly helps with the edge effects, rather than the glare around points of light. Anyways, I've decided to live with it. The mura in the Quest 3 on the other hand is intolerable so it's getting returned. 

[FupDuck]

6 hours ago, Werewolf_fs said:

There are also more sound cuts than with the previous version.

I also noticed a lot of sound cuts since the update to v59. I assumed it was something with my connection, but I guess not...

[halufpv]

2 hours ago, FupDuck said:

 

I have also noticed that the dark screen performance can be improved a lot by adjusting the position of the headset, and the best position is just as you describe it. But that mainly helps with the edge effects, rather than the glare around points of light. Anyways, I've decided to live with it. The mura in the Quest 3 on the other hand is intolerable so it's getting returned. 

That is just the nature of local dimming. The only way to get rid of that is an OLED panel which can turn on individual pixels instead of whole areas of the screen, or just disable local dimming if the effect is too disturbing, it'll basically have the same glare everywhere instead of just around bright elements as with the quest 2 or 3

Edited November 5, 2023 by halufpv

[nikoel]

6 hours ago, FupDuck said:

My controllers are fully charged. Just took them out of [off of?] the cradle, which is plugged into the power supply. Sorry, no profit...

I have also noticed that the dark screen performance can be improved a lot by adjusting the position of the headset, and the best position is just as you describe it. But that mainly helps with the edge effects, rather than the glare around points of light. Anyways, I've decided to live with it. The mura in the Quest 3 on the other hand is intolerable so it's getting returned. 

For them to no longer show up you need to put them back on the cradle. aka Charging

[some1]

For flying at night i suggest reducing the brightness to 3/4th of the max, or half way. That will considerably reduce the halo effect from local dimming. Your eyes will adapt quickly.

Edited November 5, 2023 by some1

[halufpv]

I finally had a long day to tinker with the quest pro. DLSS + QVF is absolute magic. The trick is that even in quality mode, DLSS is quite aggressive but you can actually get your own "in between the presets" setting by just changing the resolution in openXR toolkit. I went with a slight 10% upscale (though 5% a was already noticeably better) and results are indistinguishable from rendering at native resolution but with a significant performance boost, 10-25% more frames across the board. The other tweak I made was to change the QVF focus window size, which for some reason is overriden from the 0.35 default to 0.5 only for oculus users. I have to say 0.35 is "almost ok" but you do see the eye tracking more than default. 0.4 is almost as good as default, but you get another 5-10% boost. 

With these two combined I'm running the Quest pro at 1.5x 90hz with ASW and it stays at 45fps locked with a 3080Ti, hell I even saw 90fps when cruising on the F-16, it was surreal and magical. 45fps while playing close to the ground on Syria on the KA-50 was unimaginable just a month ago. All hail DLSS and eye tracking (and ofc @mbucchia), I'm over the moon!

[Slammin]

Just in case noone noticed, QP defaults to H.265 now as of a few weeks ago.  So if you are using a bitrate higher than 200 and not specifying H.264 in ODT, expect many issues.  Matter of fact, I don't even touch ODT anymore.  The defaults work best for me.

[mimamema]

On 11/1/2023 at 1:19 PM, sze5003 said:

I've tried unparking all my cores in an attempt to see if the microstutters that happen in MT DCS will go away.

Unfortunately this did not resolve anything for me. I still get a lot of intermittent microstutters and the only time I don't see them is when I'm only getting 90fps.

Even if ASW kicks in and I'm at 45fps as the perf fps built in chart of dcs shows, I still get microstutters so I'm wondering if having asw on could be the cause.

Question, I was suffering from the same problem and realized that the problem in my setup was the sharpening configured to Quality, in normal or disabled I stopped suffering from those micro stutters. Could you give it a try and see if that´s your problem as well?

 

[FupDuck]

6 hours ago, Slammin said:

Just in case noone noticed, QP defaults to H.265 now as of a few weeks ago.  So if you are using a bitrate higher than 200 and not specifying H.264 in ODT, expect many issues.  Matter of fact, I don't even touch ODT anymore.  The defaults work best for me.

Interesting. I have a Pro and a quest 3, and I've noticed its now stuttering only on the Pro. I can play the exact same flight in both headsets, and the Pro stutters while the 3 does not. Strangely the frametimes and framerate are rock solid at 72 fps, but the screen is stuttering/tearing. I'm on the road this week, but I'll look into this as soon as I get home! Thanks! 

4 hours ago, mimamema said:

Question, I was suffering from the same problem and realized that the problem in my setup was the sharpening configured to Quality, in normal or disabled I stopped suffering from those micro stutters. Could you give it a try and see if that´s your problem as well?

 

Interesting, I will look into this as well! 

[sze5003]

Question, I was suffering from the same problem and realized that the problem in my setup was the sharpening configured to Quality, in normal or disabled I stopped suffering from those micro stutters. Could you give it a try and see if that´s your problem as well?
 

Mine is set to Normal by default.

What I did do was download oculus tray tool, then in oculus home settings I set the headset to 72hz , set the slider to 1.0.

In oculus tray tool I set super sampling to 1.6, encode resolution width to 3905, and bit rate to 650.

I have pretty much all high settings in DCS, SSR to on, and terrain object shadows to flat. Visibility to extreme, clouds to ultra, water high, shadows high, civ traffic off, MSA x2.

I noticed less stutter but it's still there. CPU graph seems a bit better for some time but it randomly has spikes up along with the fps graph spiking at times too. Normally asw stays on when I'm low at 36fps and 72 when I'm up higher.

For the timea it's not having random stutters it looks great and feels smooth.

Also I noticed CPU 8 and CPU 10 constantly at 100% while other CPU's aren't helping much.

So I went ahead and disabled e cores in bios but then in resource monitor while dcs is on I only see CPU 11 and 16 working at 100% and others are not getting shared load. Not sure if they should be.

Sometimes if DCS freezes or drops fps drastically I have to go into affinity and disable CPU 8 and then it unfreezes.

Not sure what to make of all this but I think I'll just renable e cores and try installing quad views now. I don't think I'll ever get it running smoothly and I've tried just about everything.

[YoYo]

15 hours ago, Slammin said:

Just in case noone noticed, QP defaults to H.265 now as of a few weeks ago.  So if you are using a bitrate higher than 200 and not specifying H.264 in ODT, expect many issues.  Matter of fact, I don't even touch ODT anymore.  The defaults work best for me.

When I switch to H.265 I have black screen (LinkCable) however I have modified bitrate. Im using H.264.

[slughead]

20 hours ago, Slammin said:

Just in case noone noticed, QP defaults to H.265 now as of a few weeks ago.  So if you are using a bitrate higher than 200 and not specifying H.264 in ODT, expect many issues.  Matter of fact, I don't even touch ODT anymore.  The defaults work best for me.

Hmm. No, I hadn't noticed. Perhaps that is the cause of increased audio glitches. I shall change it back and see if it improves.

[sze5003]

My oculus debug tool says Default under the encoder I'm not seeing h265 selected. My headset just updated last night to v59 too.