Foveated Rendering Support for DCS

[mbucchia]

Please give us the full log from Quad-Views-Foveated 

[recoilfx]

Yep, here is a full copy and paste from the most up to date log file:

 

2023-07-21 15:01:08 -0400: XR_APILAYER_MBUCCHIA_quad_views_foveated layer (v1.0.1) is active
2023-07-21 15:01:09 -0400: Using layer: XR_APILAYER_MBUCCHIA_quad_views_foveated
2023-07-21 15:01:09 -0400: Using layer: XR_APILAYER_NOVENDOR_XRNeckSafer
2023-07-21 15:01:09 -0400: Cannot satisfy implicit extension request: XR_EXT_eye_gaze_interaction
2023-07-21 15:01:09 -0400: Requested extension: XR_KHR_D3D11_enable
2023-07-21 15:01:09 -0400: Requested extension: XR_KHR_visibility_mask
2023-07-21 15:01:09 -0400: Requested extension: XR_OCULUS_audio_device_guid
2023-07-21 15:01:09 -0400: Blocking extension: XR_VARJO_quad_views
2023-07-21 15:01:09 -0400: Requesting extension: XR_FB_eye_tracking_social
2023-07-21 15:01:09 -0400: Application: DCS World
2023-07-21 15:01:09 -0400: Using OpenXR runtime: Oculus 1.87.0
2023-07-21 15:01:09 -0400: Trying to locate configuration file at 'C:\Program Files\OpenXR-Quad-Views-Foveated\settings.cfg'...
2023-07-21 15:01:09 -0400:   Found option 'smoothen_focus_view_edges=0.2'
2023-07-21 15:01:09 -0400:   Found option 'sharpen_focus_view=0.7'
2023-07-21 15:01:09 -0400:   Found option 'peripheral_multiplier=0.4'
2023-07-21 15:01:09 -0400:   Found option 'focus_multiplier=1.1'
2023-07-21 15:01:09 -0400:   Found option 'horizontal_focus_section=0.5'
2023-07-21 15:01:09 -0400:   Found option 'vertical_focus_section=0.5'
2023-07-21 15:01:09 -0400:   Found option 'turbo_mode=1'
2023-07-21 15:01:09 -0400: Trying to locate configuration file at 'C:\Users\Zinj\AppData\Local\Quad-Views-Foveated\settings.cfg'...
2023-07-21 15:01:09 -0400:   Found option 'sharpen_focus_view=0'
2023-07-21 15:01:09 -0400:   Found option 'focus_multiplier=1'
2023-07-21 15:01:09 -0400:   Found option 'turbo_mode=0'
2023-07-21 15:01:09 -0400:   Found option 'peripheral_multiplier=0.4'
2023-07-21 15:01:09 -0400:   Found option 'horizontal_focus_section=0.45'
2023-07-21 15:01:09 -0400:   Found option 'vertical_focus_section=0.45'
2023-07-21 15:01:09 -0400: Using OpenXR system: Meta Quest Pro
2023-07-21 15:01:09 -0400: Eye tracking is supported
2023-07-21 15:01:09 -0400: Recommended peripheral resolution: 1012x1044 (0.400x density)
2023-07-21 15:01:09 -0400: Recommended focus resolution: 1138x1174 (1.000x density)
2023-07-21 15:01:09 -0400:   Stereo pixel count was: 13186048 (2528x2608)
2023-07-21 15:01:09 -0400:   Quad views pixel count is: 4785080
2023-07-21 15:01:09 -0400:   Savings: -63.7%
2023-07-21 15:01:17 -0400: Session is using quad views
2023-07-21 15:01:17 -0400: Edge smoothing: 0.20
2023-07-21 15:01:17 -0400: Sharpening: Disabled
2023-07-21 15:01:17 -0400: Turbo: Disabled

 

[mbucchia]

Can you try disabling all other software you have, like XRNS? Even if they are not running.

[recoilfx]

Yeah. I disabled XRNS, renamed export.lua to disable all the telemetry exports, and I even unplugged all my controllers, but the results are still the same. I'm stumpped.

 

 

Edited July 21, 2023 by recoilfx
picture order was messing up the text

[mbucchia]

very weird indeed. As you can see in the log file you are rendering 63% less pixels... so unclear why the game would be working harder. I've been adding all sorts of performance instrumentation in a new version (not published yet), once I release that you'll have to try again. I don't think anybody else has reported such issue so far, the only known performance issue is with OBSMirror and that tanks the CPU frame times, not GPU

[recoilfx]

Ok great. I'd be happy to test the new version when it comes out! As is, the 4090 can run DCS well without quad-views using moderate to high settings, but it'd be always nice to turn up the settings more. Again, thanks for all your work.

[edmuss]

5 hours ago, freehand said:

Your 3080ti runs the aero ok ?

It's holding it's own
Was just playing pretense and getting 75-80 fps in ka50, A10C gives me 80-90 fps normally.
I can't max settings but it's more than playable and far better than the G2.

[freehand]

33 minutes ago, edmuss said:

It's holding it's own
Was just playing pretense and getting 75-80 fps in ka50, A10C gives me 80-90 fps normally.
I can't max settings but it's more than playable and far better than the G2.

Interesting I love my quest pro BUT the Aero interests me for sure.

Thanks.

[edmuss]

The quest pro is easier to run due to the lower resolution, the lenses are also different/better than the aero (from an optical clarity point of view) but the aero is sharper.

[slughead]

Although the Quest Pro is awful in night missions. So much light bleed.

[freehand]

14 hours ago, slughead said:

Although the Quest Pro is awful in night missions. So much light bleed.

Light bleed ? 

Blacks are nice compared to other headsets I have owned.

Edited July 22, 2023 by freehand

[Tophatter14]

14 hours ago, slughead said:

Although the Quest Pro is awful in night missions. So much light bleed.

I've got bloom off with foveated rendering and it's really not noticeable to me.  YMMV.  

[Mr_sukebe]

On 7/22/2023 at 9:57 AM, slughead said:

Although the Quest Pro is awful in night missions. So much light bleed.

Do you mean physically around the headset, or from the lenses?

Im conscious that v56 apparently introduces local dimming, though I’ve not had it released to my headset as yet.

[slughead]

56 minutes ago, Mr_sukebe said:

Do you mean physically around the headset, or from the lenses?

Im conscious that v56 apparently introduces local dimming, though I’ve not had it released to my headset as yet.

The lenses. Local dimming was available in v54. The light bleed isn't improved by local dimming. This is something more widescale. Similar to the background light bleed of a television screen. As others have also described... a haze.

[nikoel]

I believe it’s because of the number of local dimming zones. It’s trying to light up the stars individually but as a result we get this kind of blooming/bleeding effect 

[slughead]

2 minutes ago, nikoel said:

I believe it’s because of the number of local dimming zones. It’s trying to light up the stars individually but as a result we get this kind of blooming/bleeding effect 

I'm not sure it is. Local dimming can be turned off in the ODT. I will try it later. If you google meta quest pro light bleed haze you'll find that this has been going on since launch (pre-local dimming) and there's been a lot of complaints about it. Meta is saying it's a feature, live with it.

[freehand]

I have not noticed this.

What nikoel said I have read about in the past but does not effect my dcs night missions.

Will take a longer fight later to night and see what others see.

Edit: mm yes I see it worse in DCS than in other black scenarios. 

Edited July 24, 2023 by freehand

[skywalker22]

@mbucchia so there is a new 1.0.1 version of Quad Views Foveated app?

And with this new version, we can enable DCS in the OpenXR Toolkit, based on the describtion on this website of yours? I just wanting to make sure, I got all correct (in v1.0.0. OpenXR Tooling DCS had to be disabled).

[zildac]

@mbucchia so there is a new 1.0.1 version of Quad Views Foveated app?
And with this new version, we can enable DCS in the OpenXR Toolkit, based on the describtion on this website of yours? I just wanting to make sure, I got all correct (in v1.0.0. OpenXR Tooling DCS had to be disabled).

This is correct.

[skywalker22]

One more question about re-installing app, quoted from the website:

"If unsure, uninstall then reinstall Quad-View-Foveated in order to establish the correct loading order."

Is this this app: OpenXR-Meta-Foveated

Do I unilstall it?

PS: I think this is it, 1st we need to uninstall OpenXR-Meta-Foveated (1.0.0 was named that way, 1.0.1 has different name).

Edited July 27, 2023 by skywalker22

[zildac]

Uninstall the old versions and install this:

https://github.com/mbucchia/Quad-Views-Foveated

 

[Mr_sukebe]

I was just having a play this evening with some settings, whilst flying the Apache over Vegas using the QP.

• It did appear that I was able to use what I'd consider to be fairly "aggressive" settings for the DFR using OpenXR Toolkit.  I had it down to 15% for the centre at x1 and whilst I could kind of sense the fuzziness, it seemed acceptable.  Definitely going to have to play with that some more
• Had another play with the ASW.  Using ASW seemed to induce regular judder.  Locking the framerate to 36hz seemed to me to work well

Anyone else?

One other question, within the Oculus page in the section where you can change the default framerate from 72 to 80 or 90hz, I couldn't help but notice that rendering resolution changed, depending upon the refresh rate, despite the multiplier staying at x1.  Why would that be?

 

[seven10]

Everything seems to be working great with the QP now and I'm able to hold 72fps in most places other than low and fast over cities. The only thing I'd like to figure out is why I'm getting a bit of a black flicker up towards the upper most center parts of each eye. I seem to notice it most when I'm looking straight forward or shift my eyes to look straight up. I thought it was due to their maybe not being enough resolution since I was using 90% scaling with NIS in the OpenXR Toolkit, but it still seems to happen with the resolution at 100%. Should I upscale further and then just adjust the size of my focus area? These are the settings I'm running for Quad View

smoothen_focus_view_edges=0.4
sharpen_focus_view=0.45

[Oculus]
peripheral_multiplier=0.5
focus_multiplier=1.1
horizontal_focus_section=0.5
vertical_focus_section=0.5
turbo_mode=1

[mbucchia]

1 hour ago, seven10 said:

Everything seems to be working great with the QP now and I'm able to hold 72fps in most places other than low and fast over cities. The only thing I'd like to figure out is why I'm getting a bit of a black flicker up towards the upper most center parts of each eye. I seem to notice it most when I'm looking straight forward or shift my eyes to look straight up. I thought it was due to their maybe not being enough resolution since I was using 90% scaling with NIS in the OpenXR Toolkit, but it still seems to happen with the resolution at 100%. Should I upscale further and then just adjust the size of my focus area? These are the settings I'm running for Quad View

smoothen_focus_view_edges=0.4
sharpen_focus_view=0.45

[Oculus]
peripheral_multiplier=0.5
focus_multiplier=1.1
horizontal_focus_section=0.5
vertical_focus_section=0.5
turbo_mode=1

`smoothen_focus_view_edges=0.4`??

That is ridiculous, you are making your focus region opaque only on a tiny portion at the center, meanwhile you are still rendering all of its pixels!!

focus_section=0.5/0.5 means 1/4th of the screen, then on top of it you are only leaving 0.2 of it opaque (0.4 out of 0.5), that means only 4% of your screen is at uncompromised full resolution!! You don't need to have such a big transition between the two regions, that transition is meant to make sure that you're not abruptly going from full resolution to half-resolution, but the smaller the better!

Use `debug_focus_view=1` to visualize the focus region only, this might help you visualize what these settings are doing.

[seven10]

8 hours ago, mbucchia said:

`smoothen_focus_view_edges=0.4`??

That is ridiculous, you are making your focus region opaque only on a tiny portion at the center, meanwhile you are still rendering all of its pixels!!

focus_section=0.5/0.5 means 1/4th of the screen, then on top of it you are only leaving 0.2 of it opaque (0.4 out of 0.5), that means only 4% of your screen is at uncompromised full resolution!! You don't need to have such a big transition between the two regions, that transition is meant to make sure that you're not abruptly going from full resolution to half-resolution, but the smaller the better!

Use `debug_focus_view=1` to visualize the focus region only, this might help you visualize what these settings are doing.

Sorry, I guess I was thinking that smoothen_focus_view_edges was applying something like a gaussian blur between the focused portion of the view and the lower resolution portions. What I'm trying to do is slightly smooth or improve the out of focus areas since the default settings make the lcd and mfd's in multiple airframes alias heavily and the sparkle is distracting to me. Would I instead just raise the value in peripheral_multiplier and bring the smoothen_focus_view_edges down to .1 or so?