Meta Quest Pro Settings

[slughead]

1 hour ago, Digitalvole said:

turbo mode is set to off in quad view settings by default

It's on by default and can only be changed via the config file, not the OXRTK. It's probably best to read through the quad-view wiki instructions as there are a couple of things if you miss, will give you a sub-optimal experience.

[Digitalvole]

59 minutes ago, slughead said:

It's on by default and can only be changed via the config file, not the OXRTK. It's probably best to read through the quad-view wiki instructions as there are a couple of things if you miss, will give you a sub-optimal experience.

Right, sorry. First time I’ve touched it in a week or so. Must have it all backwards in my head. I made sure to read the wiki, but can’t hurt todo so again.

Im going to test my usb port speeds as well. I’m sure the muddy/blurry textures are as a result of link cable shinanagins. Looks gorgeous in the cockpit though!

[Digitalvole]

Apologies if I’m just being dense, but how are you guys reading your frame times? I’ve tried all of the performance hud overlays in odt and I still can’t work out what my cpu/gpu frame time are. 

[slughead]

1 minute ago, Digitalvole said:

Apologies if I’m just being dense, but how are you guys reading your frame times? I’ve tried all of the performance hud overlays in odt and I still can’t work out what my cpu/gpu frame time are. 

I generally use OXRTK for this. Often also have the inbuilt FPS meter open too. You can get frame times out of that as well.

[Digitalvole]

19 hours ago, slughead said:

I generally use OXRTK for this. Often also have the inbuilt FPS meter open too. You can get frame times out of that as well.

I’m having zero Google luck, what’s the shortcut for the inbuilt fps meter? All I can find from google is the performance hud overlay, which for the life of me I can’t find the gpu/cpu frametimes.

Anyway I’ll keep googling, rarely get near my pc now anyway.

[Werewolf_fs]

hace 2 horas, Digitalvole dijo:

No tengo suerte con Google, ¿cuál es el atajo para el medidor de fps incorporado? Todo lo que puedo encontrar en Google es la superposición de hud de rendimiento, que por mi vida no puedo encontrar los tiempos de fotogramas de gpu/cpu.

De todos modos, seguiré buscando en Google, de todos modos rara vez me acerco a mi PC.

In OpenXR tool: https://mbucchia.github.io/OpenXR-Toolkit/  in performance

In Oculus Tray tool: https://www.apollyonvr.com/oculus-tray-tool option VISUAL HUD ---> APPLICATION RENDER TIME

In Oculus Debug tool: https://developer.oculus.com/documentation/native/pc/dg-debug-tool/ option Visible HUD ---> APPLICATION RENDER TIME

With subtitles why is it in Spanish

Edited September 23, 2023 by Werewolf_fs

[slughead]

On 9/23/2023 at 2:47 PM, Digitalvole said:

I’m having zero Google luck, what’s the shortcut for the inbuilt fps meter? All I can find from google is the performance hud overlay, which for the life of me I can’t find the gpu/cpu frametimes.

Anyway I’ll keep googling, rarely get near my pc now anyway.

You'll need to check how yours is configured in the UI Layer settings as I have changed mine.

 

null

[Digitalvole]

Thanks chaps, like a doofus I had turbo mode on so wasn’t getting proper readings, what a plonker!

With turbo mode off I noticed that despite being below 13.9ms for both gpu and cpu I’m dropping below 72fps (For example gpu 11ms cpu 10ms.)  When this happens I notice “app missed submit count” is red and the count is going up. I’m busy trying to find out what on earth that means haha.

I’m getting a shadow/dark patch at the top centre of the screen which is something to do with the quad views, and some odd things happen when flying at night, something is up there but I’m going to look into that at a latter date.  

Other than that and the comfort of the QP on me noggin I’m very impressed.

I want to be flying in the mudhen right now but instead I’m training my wife/kids new puppy. Groan.

 

Edited September 25, 2023 by Digitalvole

[slughead]

5 hours ago, Digitalvole said:

Other than that and the comfort of the QP on me noggin I’m very impressed.

Get yourself a Globular Cluster Comfort Kit for the Quest Pro. Massive improvement in comfort. There is a version two of the kit, so try to get that. If not, they will send you a free upgrade.

[Digitalvole]

1 hour ago, slughead said:

Get yourself a Globular Cluster Comfort Kit for the Quest Pro. Massive improvement in comfort. There is a version two of the kit, so try to get that. If not, they will send you a free upgrade.

Will do, have to be next month though. I’ll muddle on till then.

Any idea what “app missed submit count” is all about? *looks suspiciously at link cable.* I can’t find much info on it other than:

“Increments each time the application fails to submit a new set of layers using ovr_EndFrame before the compositor is executed and before each V-Sync (Vertical Synchronization).”
 

The other thing I’m tinkering about with is bitrate because the default setting is bringing up some very noticeable compression, big blurry blobs where there should be trees etc.

[slughead]

58 minutes ago, Digitalvole said:

Will do, have to be next month though. I’ll muddle on till then.

Any idea what “app missed submit count” is all about? *looks suspiciously at link cable.* I can’t find much info on it other than:

“Increments each time the application fails to submit a new set of layers using ovr_EndFrame before the compositor is executed and before each V-Sync (Vertical Synchronization).”
 

The other thing I’m tinkering about with is bitrate because the default setting is bringing up some very noticeable compression, big blurry blobs where there should be trees etc.

App missed submit count would be the number of times the applications (DCS) failed to submit a frame in time to meet the 72fps frame timing. This would probably cause Oculus to dip into ASW. Either lower your render resolution or turn down some settings in DCS if you want to remain in 72fps and out of ASW.

If the encoder bitrate is too low, you will see compression artefacts. Mine is set to default plus a 50 offset. I don't think I notice any compression artefacts. You can also get nasty compression artefacts in areas of similar colour (sky and sea) when in ASW. I expect this is what you are seeing rather than having a low bitrate. Leave the bitrate at default and don't try running at max render resolution.

You don't say what your system specifications are or what your DCS / Oculus settings are so it is difficult to advise further.

[mbucchia]

Heads up for folks using Quad-Views-Foveated on Pro - there is an upcoming update that will enable Virtual Desktop brand new eye tracking support. I'll post about it when it's out.

[Steel Jaw]

Great thread good info

[slughead]

Does anyone use virtual desktop with the Quest Pro? I don't know what it offers. It's not needed to run DCS with the Quest Pro.

[Steel Jaw]

46 minutes ago, slughead said:

Does anyone use virtual desktop with the Quest Pro? I don't know what it offers. It's not needed to run DCS with the Quest Pro.

I'd like to know how to disable the Oculus 2 Virtual Desktop, might give me a performance boost.

[mbucchia]

7 hours ago, mbucchia said:

Heads up for folks using Quad-Views-Foveated on Pro - there is an upcoming update that will enable Virtual Desktop brand new eye tracking support. I'll post about it when it's out.

Said tool is out now:

Home · mbucchia/OpenXR-Eye-Trackers Wiki (github.com)

Install side-by-side with Quad-Views-Foveated (current version works with it).

Yes this is spread in two tools, because eye tracking support isn't specific to Quad Views, and some people may want to use eye tracking for other stuff.

[Digitalvole]

On 9/25/2023 at 6:12 PM, slughead said:

App missed submit count would be the number of times the applications (DCS) failed to submit a frame in time to meet the 72fps frame timing. This would probably cause Oculus to dip into ASW. Either lower your render resolution or turn down some settings in DCS if you want to remain in 72fps and out of ASW.

If the encoder bitrate is too low, you will see compression artefacts. Mine is set to default plus a 50 offset. I don't think I notice any compression artefacts. You can also get nasty compression artefacts in areas of similar colour (sky and sea) when in ASW. I expect this is what you are seeing rather than having a low bitrate. Leave the bitrate at default and don't try running at max render resolution.

You don't say what your system specifications are or what your DCS / Oculus settings are so it is difficult to advise further.

Settings are pretty much the ones you recommended. Anyway it’s all good, I’m just used to thinking “gpu/cpu” now I need to factor in link cable too. 

Thanks for all your help, just flew the mossie on the Normandy map and it was ace so I can’t complain.

[Andrew u.k.]

Just like to say thankyou Slughead. 
I had been getting jittery/ tearing. Went back to your settings you've just gone through with Digitalvole using ODT and OTT and all working well again.
Thanks again.  

[slughead]

12 hours ago, Andrew u.k. said:

Just like to say thankyou Slughead. 
I had been getting jittery/ tearing. Went back to your settings you've just gone through with Digitalvole using ODT and OTT and all working well again.
Thanks again.  

You're very welcome! I'm a big fan of the K.I.S.S. principle. Keep it simple stupid.

[VirusAM]

On 9/27/2023 at 8:01 PM, mbucchia said:

Heads up for folks using Quad-Views-Foveated on Pro - there is an upcoming update that will enable Virtual Desktop brand new eye tracking support. I'll post about it when it's out.

Thanks...does that mean that we can use eye tracking in DCS with Virtual Desktop?

[mbucchia]

46 minutes ago, VirusAM said:

Thanks...does that mean that we can use eye tracking in DCS with Virtual Desktop?

Yes. There is instructions on the wiki for that.

[P999]

On 9/28/2023 at 1:09 PM, Digitalvole said:

Settings are pretty much the ones you recommended. Anyway it’s all good, I’m just used to thinking “gpu/cpu” now I need to factor in link cable too. 

Thanks for all your help, just flew the mossie on the Normandy map and it was ace so I can’t complain.

Just about to take the plunge and buy a quest pro, having “done” all the essential YouTube videos. However this thread has been unbelievably helpful in unpacking the good and the bad and how the hell to get all the different components talking. (Never having tried VR before). Thank you so much Digitalvote for asking all the questions I wanted answers for . Thanks also to all the contributors- your amazing background help is what makes the whole DCS experience so good. I love flying WW2 birds 2D on the newer maps, (even if I am regularly destroyed in MP) - here’s hoping 3D is as good as it sounds! 

[Digitalvole]

1 hour ago, P999 said:

Just about to take the plunge and buy a quest pro, having “done” all the essential YouTube videos. However this thread has been unbelievably helpful in unpacking the good and the bad and how the hell to get all the different components talking. (Never having tried VR before). Thank you so much Digitalvote for asking all the questions I wanted answers for . Thanks also to all the contributors- your amazing background help is what makes the whole DCS experience so good. I love flying WW2 birds 2D on the newer maps, (even if I am regularly destroyed in MP) - here’s hoping 3D is as good as it sounds! 

Hehe my pleasure, but like you say isn’t it amazing to have such clever people here willing to help others.

If your about to take the VR plunge and are coming from TrackIr, may I just say that it’s like the planes we fly in the sim, none of them are perfect at everything. I suppose what im trying to say is the ability to compromise is essential, VR is not perfect. It’s bloody great but you have to be willing to spend a butt tonne of money and be ok with less than stellar visuals. 

I always wonder what DCS would be like with TrackIR, I bet it looks amazing! But as tempting as those beautiful visuals are DCS in VR is the only thing in my life where once I put that headset on, my mind is completely clear of anything except being in a cockpit and living a childhood (and adulthood) dream.

It’s not perfect though, compromise is required.
 

[slughead]

4 minutes ago, Digitalvole said:

none of them are perfect at everything. I suppose what im trying to say is the ability to compromise is essential, VR is not perfect

100%. For me, the feeling of sitting in the cockpit outweighs our compromises.

As for trackir, I could never really get along with it. But VR, for me, is total immersion bar g-forces or reality.

[P999]

14 minutes ago, Digitalvole said:

Hehe my pleasure, but like you say isn’t it amazing to have such clever people here willing to help others.

If your about to take the VR plunge and are coming from TrackIr, may I just say that it’s like the planes we fly in the sim, none of them are perfect at everything. I suppose what im trying to say is the ability to compromise is essential, VR is not perfect. It’s bloody great but you have to be willing to spend a butt tonne of money and be ok with less than stellar visuals. 

I always wonder what DCS would be like with TrackIR, I bet it looks amazing! But as tempting as those beautiful visuals are DCS in VR is the only thing in my life where once I put that headset on, my mind is completely clear of anything except being in a cockpit and living a childhood (and adulthood) dream.

It’s not perfect though, compromise is required.
 

Yep, compromise is definitely king! Coming from a background of sailing and campervans - I have yet to find a perfect one….

As for trackir visuals- they certainly can be amazing. Last night, flying over the Normandy map, heavy cloud and rain - then there was a break in the clouds, sun came through and a rainbow formed ahead of me. I was truly caught out by how stunningly good the programmers have become. 

Can be a bit of an addictive, financially draining hobby. And I was introduced to it because it was “free” - ha ha indeed.

However I haven’t heard of many that have gone back to 2D from VR!

Cheers