Meta Quest Pro Settings

[markturner1960]

Out of interest, is this thread relevant to the current situation with the QP? I am assuming not as nothing along these lines has been mentioned in this thread or any other Quest Pro specific ones, but.....one or two QP users in that thread reported better performance. 

 

There was the point that using OTT is different to setting the mirror resolution within DCS...although, no idea why this should be? 

Edited August 29, 2023 by markturner1960

[Maksim Savelev]

Hello everyone!

Just recently got my Quest Pro. Coming from almost  everything that had been released (CV1, Rift S, HPreverb, Index, Pimax 8KX, HP G2, Varjo (what a piece of sh...), Pico4) found that Quest Pro is almost perfect. Add some resolution on top of all it has to offer and it would The Best and The only must have headset for flying.

Since all of you gentlemen  have quite of experience with this headset could you please help me with one thing I'm having troubles with. Its fun, but using Quad-view is causing some stutters and when I have it deleted/uninstalled everything is smooth. Did someone of you have anything like this? 

[biotech]

9 минут назад, Maksim Savelev сказал:

Hello everyone!

Just recently got my Quest Pro. Coming from almost  everything that had been released (CV1, Rift S, HPreverb, Index, Pimax 8KX, HP G2, Varjo (what a piece of sh...), Pico4) found that Quest Pro is almost perfect. Add some resolution on top of all it has to offer and it would The Best and The only must have headset for flying.

Since all of you gentlemen  have quite of experience with this headset could you please help me with one thing I'm having troubles with. Its fun, but using Quad-view is causing some stutters and when I have it deleted/uninstalled everything is smooth. Did someone of you have anything like this? 

MT or ST version of DCS?

if MT, try to unpark CPU cores (with ParkControl app for example). for me it completly removed stutters (mouse cursor movement caused) in MT version.

[Maksim Savelev]

Yes MT version. Thank you will try to dig in this direction 

[Maksim Savelev]

But MT version works fine without Quad-views installed

[YoYo]

41 minutes ago, Maksim Savelev said:

Hello everyone!

Just recently got my Quest Pro. Coming from almost  everything that had been released (CV1, Rift S, HPreverb, Index, Pimax 8KX, HP G2, Varjo (what a piece of sh...), Pico4) found that Quest Pro is almost perfect. Add some resolution on top of all it has to offer and it would The Best and The only must have headset for flying.

Good choice! 

[Maksim Savelev]

55 минут назад, biotech сказал:

MT or ST version of DCS?

if MT, try to unpark CPU cores (with ParkControl app for example). for me it completly removed stutters (mouse cursor movement caused) in MT version.

Unfortunately it did nothing to me. Seems like this technology sucking more performances out of my system than gives benefits, I'm just wondering why it happens. Have no clue at this moment(  

[obious]

1 hour ago, Maksim Savelev said:

Hello everyone!

Just recently got my Quest Pro. Coming from almost  everything that had been released (CV1, Rift S, HPreverb, Index, Pimax 8KX, HP G2, Varjo (what a piece of sh...), Pico4) found that Quest Pro is almost perfect. Add some resolution on top of all it has to offer and it would The Best and The only must have headset for flying.

Since all of you gentlemen  have quite of experience with this headset could you please help me with one thing I'm having troubles with. Its fun, but using Quad-view is causing some stutters and when I have it deleted/uninstalled everything is smooth. Did someone of you have anything like this? 

 

Try turning on Turbo Mode in OKRTK, that removed all the stutters I was having with MT and my QP

[Maksim Savelev]

6 минут назад, obious сказал:

 

Try turning on Turbo Mode in OKRTK, that removed all the stutters I was having with MT and my QP

I'm using Turbo Mode On 

[Bazz_Mulder]

18 minutes ago, Maksim Savelev said:

I'm using Turbo Mode On 

It will not help.

You are most likely CPU, not GPU limited with your frames. QVFR helps only when there is a clear GPU bottleneck. In case of CPU limit, it's causing stutters and lower fps, try to uninstall it and test same scenario with 72hz at res on 1.3x

For more, check vr4dcs discord for Quest Pro https://discord.com/channels/610534461456777257/1029725611662524566

and QVFR discord https://discord.com/channels/933220354401398785/947051902913376318

Edited August 30, 2023 by Bazz_Mulder

[Maksim Savelev]

Just wanted to clarify, I'm the only one person in here who are not pushing things from the limits. Using 4224*2128 with 72fps in Oculus software and having 1.0 multiplayer in OTT. At Rtx4090 and AMD5800X3d system. I really mean I have very smooth experience with stable 72fps in DCS running lowest settings than everyone has here. Problem is that installing Quad-Views cause these performance to drop significantly

  

Edited August 30, 2023 by Maksim Savelev

[Maksim Savelev]

Thank you. Unfortunately I can't reach these discords channel, I think I have to be invited to be able to see it

[recoilfx]

53 minutes ago, Maksim Savelev said:

Just wanted to clarify, I'm the only one person in here who are not pushing things from the limits. Using 4224*2128 with 72fps in Oculus software and having 1.0 multiplayer in OTT. At Rtx4090 and AMD5800X3d system. I really mean I have very smooth experience with stable 72fps in DCS running lowest settings than everyone has here. Problem is that installing Quad-Views cause these performance to drop significantly

  

 

Well, you are not the only person with the same issue - I also have 5800x3d with 4090. My experience has been that, when a scene is more complex, QVFR is worse, no matter what I do, it increases about ~3-5ms of frame time both CPU and GPU. But in less complex scenes (i.e. simple caucaus map missions), I can crank up the visuals without as much performance decrease. My only uneducated guess is that rendering 4 views instead of 2 gets really bad when object count goes up.

[nikoel]

11 minutes ago, recoilfx said:

Well, you are not the only person with the same issue - I also have 5800x3d with 4090. My experience has been that, when a scene is more complex, QVFR is worse, no matter what I do, it increases about ~3-5ms of frame time both CPU and GPU. But in less complex scenes (i.e. simple caucaus map missions), I can crank up the visuals without as much performance decrease. My only uneducated guess is that rendering 4 views instead of 2 gets really bad when object count goes up.

I have found this to be true as well

When it works, I have headroom of 100% and then all of a sudden BAM! -4ms 

I believe this is due to CPU utilisation. I also have a 4090 and 5800X3D

I haven't dug too deeply into it as I can just make the GPU work harder without DFR

[Maksim Savelev]

Thank you very much gentlemen! Now its clear for me that it gives an additional hit on performances and it's not just me. As I understood, people who appreciate this technology pushing theirs settings very high regardless of smoothness sake and then when they're getting themselves trapped  at the bottle neck they use this Quad-View to get some relieve. 

[Digitalvole]

Is Quad view the same as DFR?

[dburne]

1 hour ago, Digitalvole said:

Is Quad view the same as DFR?

Well they are tied together I believe as I understand one needs Quad View to have DFR. At least that is my impression. I am sure @mbucchia will clarify if different.

[Digitalvole]

2 minutes ago, dburne said:

Well they are tied together I believe as I understand one needs Quad View to have DFR. At least that is my impression. I am sure @mbucchia will clarify if different.

Ahh, ok. Thanks dburne. I really appreciate your answering my questions on stuff I’m sure you guys all squared away months ago.

[Digitalvole]

44 minutes ago, Bazz_Mulder said:

No, they are not the same. QVFR relies on eye movement tracking. DFR is fixed to the center of the screen. DFR should be turned OFF when using QVFR as stated per step in installation procedure which require to make all OpenXR setting back to default state, also on project wiki page:

 

• Be mindful of the settings you enable in OpenXR Toolkit! Several settings are incompatible and should not be used:

  • 'Foveated Rendering' - You are already doing this through Quad-Views-Foveated, and better!.
  • 'Field of view' override and 'Zoom'.
  • 'Turbo mode' may only be used if it is not already enabled through Quad-Views-Foveated's configuration.

Ah ok, I thought that was FFR (fixed foveated rendering) and DFR (Dynamic Foveated Rendering) is tracking where your eyes are?

If one is using DFR/Quad View does one have to use open XR? I ask because I really don’t like the motion smoothing in open XR where as the Oculus version is pretty good. 

[Sile]

vor 29 Minuten schrieb Digitalvole:

Ah ok, I thought that was FFR (fixed foveated rendering) and DFR (Dynamic Foveated Rendering) is tracking where your eyes are?

If one is using DFR/Quad View does one have to use open XR? I ask because I really don’t like the motion smoothing in open XR where as the Oculus version is pretty good. 

You are correct on FFR and DFR. The poster @Bazz_Mulder above somehow confuses DFR (DYNAMIC Foveated Rendering) with FFR (Fixed Foveated Rendering).
Quad Views is the technique that mbucchia uses to implement DFR for DCS and it only works with OpenXR.

Installing OpenXR Toolkit is optional and it should be installed before "Quad-Views-Foveated".
Some Settings (e.g. Foveated Rendering like posted above by Bazz_Mulder) are incompatible with Quad Views and should be avoided in OpenXR Toolkit. See Wiki: https://github.com/mbucchia/Quad-Views-Foveated/wiki

Your Oculus headset runtime will still use ASW even when running with OpenXR API.

Edited August 31, 2023 by Sile

[Digitalvole]

2 hours ago, Sile said:

You are correct on FFR and DFR. The poster @Bazz_Mulder above somehow confuses DFR (DYNAMIC Foveated Rendering) with FFR (Fixed Foveated Rendering).
Quad Views is the technique that mbucchia uses to implement DFR for DCS and it only works with OpenXR.

Installing OpenXR Toolkit is optional and it should be installed before "Quad-Views-Foveated".
Some Settings (e.g. Foveated Rendering like posted above by Bazz_Mulder) are incompatible with Quad Views and should be avoided in OpenXR Toolkit. See Wiki: https://github.com/mbucchia/Quad-Views-Foveated/wiki

Your Oculus headset runtime will still use ASW even when running with OpenXR API.

 

Thanks for clearing that up, so many terms it’s easy to get confused.

Fantastic news about ASW too, I’m warming up my right index finger, gonna be using it to hit the buy button tonight.

[biotech]

Made couple of tests and agree with @Maksim Savelev and @recoilfx

Quad-view rendering have noticable performance issues with multiple 3d objects in sight (airplanes on airfield for example), even at far distance.

 

[Maksim Savelev]

Gentlemen another question. As I understand when Quad-View is installed its already providing a fix which prevents DCS from crashing when headset is taken off, is there any method to prevent it without installing it? Overriding proximity sensor via  Oculus Debug Tool doesn't help. Any advices on this? Thank you

Edited August 31, 2023 by Maksim Savelev

[biotech]

5 часов назад, Maksim Savelev сказал:

Any advices on this? Thank you

turn off "Turbo mode" in OpenXR Toolkit. and wait for @mbucchia to update this tool.

[mbucchia]

(Deleted because I misread the message)

2 hours ago, biotech said:

turn off "Turbo mode" in OpenXR Toolkit. and wait for @mbucchia to update this tool.

I don't know what update you are talking about. If the user isn't using Quad Views, there's nothing I can do.

 

The bug in question is in the Oculus runtime, and I reported it to Meta.

Edited September 1, 2023 by mbucchia