Meta Quest Pro Settings

[slughead]

4 minutes ago, skywalker22 said:

There are no those artifacts when being in the main menu. As soon as I go and start Rift Cable app, in side there I start seeing them, and also in games later on (AC, ACC, DCS). No clue why. At least I know there is nothing wrong with Quest pro (or its lenses), since it works perfectly fine in main menu.

I did some, but I think I returned them back to default. I think, not so sure. Would you share default ones?

This is how I have now in ODT:

Those are pretty much the default. I'd leave the distortion curve to default too. I can't see the point in changing it from default.

Are you using the Oculus Tool Tray app too?

[skywalker22]

1 minute ago, slughead said:

Those are pretty much the default. I'd leave the distortion curve to default too. I can't see the point in changing it from default.

Are you using the Oculus Tool Tray app too?

No, just this. 

So you have any clue what's causing those artifacts? I noticed them yesterday.

[slughead]

4 minutes ago, skywalker22 said:

No, just this. 

So you have any clue what's causing those artifacts? I noticed them yesterday.

I have heard you may be able to solve this by changing the "sliced encoding" to 1. I haven't tried it myself and I haven't seen this problem recently. But I am now on v54 of the Oculus software as of today so I might be seeing it soon. You are also on v54.

[YoYo]

2 hours ago, skywalker22 said:

But wha'ts puzzling about me mostly about this ODT app, is that even if I change some parameter it reverts back after a while!!! 

 

I wrote about it. After reboot, they return to the default settings (the upper part especially), so it is necessary to use OTT.

[jnr4817]

I use OTT only, haven't had any problems. I occasionally check with ODT, for giggles, but OTT remains consistent.

[Dentedend10]

Took a couple comparison shots to see if it is worth going with the higher resolution in Oculus app. To me it seems that there is minor difference inside the cockpit between 4864*2448 vs 5408*2736 and basically no difference when I look outside. There is quite the performance difference though. This makes me want to stick with the lower res.

What is other people's perception?

 

[slughead]

1 hour ago, Dentedend10 said:

Took a couple comparison shots to see if it is worth going with the higher resolution in Oculus app. To me it seems that there is minor difference inside the cockpit between 4864*2448 vs 5408*2736 and basically no difference when I look outside. There is quite the performance difference though. This makes me want to stick with the lower res.

What is other people's perception?

 

Totally agree. I said this a long time ago. Pushing highest render resolutions gives diminishing returns and lower performance. I prefer to be at the “just enough” setting and get more headroom so less dropping down into ASW/motion reprojection. I still have all settings in DCS maxed out though.

Edited June 11, 2023 by slughead

[diego999]

4 hours ago, Dentedend10 said:

Took a couple comparison shots to see if it is worth going with the higher resolution in Oculus app. To me it seems that there is minor difference inside the cockpit between 4864*2448 vs 5408*2736 and basically no difference when I look outside. There is quite the performance difference though. This makes me want to stick with the lower res.

What is other people's perception?

 

True. There's a sweet spot for resolution/performance, depending on your particular combination of headset/GPU/CPU/RAM, where cranking up the res past that point doesn't offer any noticeable visual improvements, but can tank your framerate. 

For me it's around 1.25 super sampling in OTT. Maybe better headsets can take advantage of higher resolutions, but with my Quest 2 I can't tell the difference if that setting is higher.

 

[Blue73]

On 6/8/2023 at 8:40 PM, skywalker22 said:

I think I know what I changed yesterday, it was resolution in Oculus app and in ODT.

Now I went back to what it was, and artifacts are GONE

So this is my current state (and works ok):

Have to play with different settings, to find what exactly is causing those artifacts. Thx mate for pointing me into the right direction, really appreciate it.

Hi Skywalker, you need to disable the sliced encoder setting in ODT. Then you can chose what gfx setting you like. Very minor impact on latency, in the ms. 

[DirtyMike0330]

29 minutes ago, Blue73 said:

Hi Skywalker, you need to disable the sliced encoder setting in ODT. Then you can chose what gfx setting you like. Very minor impact on latency, in the ms. 

What does the enabling/disabling sliced encoding (as opposed to leaving it at default) do? I just did a cursory google, but I'm not seeing much on what the function of sliced encoding. I've just had mine on default since having the QP. 

[ODBU_Mongoose]

19 hours ago, slughead said:

Totally agree. I said this a long time ago. Pushing highest render resolutions gives diminishing returns and lower performance. I prefer to be at the “just enough” setting and get more headroom so less dropping down into ASW/motion reprojection. I still have all settings in DCS maxed out though.

 

Hi Slughead so thats in the oculus app, not OTT right?

[slughead]

1 hour ago, ODBU_Mongoose said:

Hi Slughead so thats in the oculus app, not OTT right?

Render resolution?

 

Ok, once again.....

 

Render resolution is the resolution the rendering app (DCS in this case) is told to render its image at. This can be done in the Oculus App in Devices > Meta Quest Pro and Meta Quest Pro Touch > Graphics Preferences.

 

Or... Leave the render resolution in the Oculus App at 1x, and set PD in the Oculus Debug Tool.... or in the Oculus Tray Tool... or heck, even in DCS. PD is the same as the multiplier in the render resolution config in the Oculus app.

But.... it would not be sensible to set the render resolution to anything other than 1.0x in the Oculus app and then set the PD anywhere else. Just change the render resolution in one place only.

[freehand]

4 minutes ago, slughead said:

Render resolution?

 

Ok, once again.....

 

2,3,4 lol.

[actually_fred]

3 hours ago, DirtyMike0330 said:

What does the enabling/disabling sliced encoding (as opposed to leaving it at default) do? I just did a cursory google, but I'm not seeing much on what the function of sliced encoding. I've just had mine on default since having the QP. 

To make the math easy, let's pretend the resolution was 3000x1000 and there's 3 slices:

Sliced encoding on: it encodes 3 1000x1000 pictures per frame
Sliced encoding off: it encodes 1 3000x1000 picture per frame

Sliced encoding generally reduces latency, but - for a given bitrate - slightly reduces quality.

The quality reduction is *very* slight - unless you're having driver or hardware issues, you almost always want it on. "Default" is probably along the lines of "on for nvidia cards and most others, off for cards that are known to have issues"

Edited June 12, 2023 by actually_fred

[DirtyMike0330]

3 hours ago, actually_fred said:

To make the math easy, let's pretend the resolution was 3000x1000 and there's 3 slices:

Sliced encoding on: it encodes 3 1000x1000 pictures per frame
Sliced encoding off: it encodes 1 3000x1000 picture per frame

Sliced encoding generally reduces latency, but - for a given bitrate - slightly reduces quality.

The quality reduction is *very* slight - unless you're having driver or hardware issues, you almost always want it on. "Default" is probably along the lines of "on for nvidia cards and most others, off for cards that are known to have issues"

 

Thanks!

[markturner1960]

On 6/11/2023 at 5:47 PM, slughead said:

Totally agree. I said this a long time ago. Pushing highest render resolutions gives diminishing returns and lower performance. I prefer to be at the “just enough” setting and get more headroom so less dropping down into ASW/motion reprojection. I still have all settings in DCS maxed out though.

 

So, you may have noticed my thread on shimmering. I have tracked the cause to the headset resolution…….although changes like you mention do not have a big effect in the cockpit, they are very noticeable at mid and longer distance. I maxed the resolution in oculus and set 1.3 on OTT ( this at Tepnox’s suggestion, thx mate) and the shimmer is nearly gone. So while it may not affect the cockpit so noticeably, it does elsewhere. In my case I have had to make some other compromises in settings to run at this resolution, BUT……for me the visual clarity is worth it, the shimmering and jaggies were driving me mad……

[nikoel]

Interesting video released by Lukas. Explains really well why some headsets have "useless" pixels. Good to see that QP and the like are using technologies that are less wasteful in both physical world and compute

 

[slughead]

2 hours ago, nikoel said:

Interesting video released by Lukas. Explains really well why some headsets have "useless" pixels. Good to see that QP and the like are using technologies that are less wasteful in both physical world and compute

 

Nice find. 

[some1]

Even with Quest Pro, I still have a lot of unused screen area that I can't normally see, which I can disable using OTT FOV multiplier adjustment without any adverse effects. This partially depends on how close to the face you move the lenses, but also on your individual anatomical features. Like how tall is your forehead, how deep are your eyes sockets, etc.

FOV tweak is really worth trying, free performance gains.

Edited June 18, 2023 by some1

[slughead]

11 hours ago, markturner1960 said:

So, you may have noticed my thread on shimmering. I have tracked the cause to the headset resolution…….although changes like you mention do not have a big effect in the cockpit, they are very noticeable at mid and longer distance. I maxed the resolution in oculus and set 1.3 on OTT ( this at Tepnox’s suggestion, thx mate) and the shimmer is nearly gone. So while it may not affect the cockpit so noticeably, it does elsewhere. In my case I have had to make some other compromises in settings to run at this resolution, BUT……for me the visual clarity is worth it, the shimmering and jaggies were driving me mad……

I can't concur. I don't see a difference in the shimmer of the roofs of buildings with the sun on them at distance with the render resolution maxed out. Are you running with MSAA at all? I am running with MSAAx4.

[diego999]

2 hours ago, some1 said:

Even with Quest Pro, I still have a lot of unused screen area that I can't normally see, which I can disable using OTT FOV multiplier adjustment without any adverse effects. This partially depends on how close to the face you move the lenses, but also on your individual anatomical features. Like how tall is your forehead, how deep are your eyes sockets, etc.

FOV tweak is really worth trying, free performance gains.

 

 

This. Reducing the fov was the setting that gave me the most gains in performance.

[YoYo]

5 hours ago, nikoel said:

Interesting video released by Lukas. Explains really well why some headsets have "useless" pixels. Good to see that QP and the like are using technologies that are less wasteful in both physical world and compute

 

Interesting, thx for video!

[Hippo]

 

[dburne]

34 minutes ago, Hippo said:

 

 

You Quest Pro users are in for a real treat with this, it works beautifully with the Aero and DCS. Talk about a performance gain with literally no impact on obvservable image quality. 

[slughead]

5 minutes ago, dburne said:

 

You Quest Pro users are in for a real treat with this, it works beautifully with the Aero and DCS. Talk about a performance gain with literally no impact on obvservable image quality. 

Excellent! When I asked about this I got the distinct impression he was very passed off with meta and wouldn’t waste any more time on the Quest. I wonder what changed