Foveated Rendering Support for DCS

[mbucchia]

1 hour ago, Gun Jam said:

sorry if I missed this but cant seem to find an answer.

I have the G2 and its my understanding that openxr should support fixed foveated rendering. I have found it mentioned in several locations but have not been able to figure out how to implement it in real life. I see no options for FFR in "openxr tools for windows mixed reality" im assuming it probably uses some other app that ive forgotten about or dont have.

any links or quick explanation of how to enable this?

Thanks

 

https://mbucchia.github.io/OpenXR-Toolkit/

[Gun Jam]

Awesome I got it no worries. Good instructions too!

my initial observation is that it makes less difference than I would have expected. I set a custom FFR with 1/16th outer ring resolution and then set the outer ring to dominate the FOV until the clear spot was about the size of a fist held out at arms lenght I would expect this setting to provide the most boost in FPS as it provided a notable degradation in image quality as expected. with setting off I had a gpu frame time of about 18ms with the setting on it was about 16.8 with a change of FPS from 55 to about 61

I have a 4090 with a 13900k and 64gb of ram.

I will play with this more.

Thank you for all your work and all you've done to help with DCS and our VR adventures!

 

[VirusAM]

oh OK then it sounds like that problem instead: 
Not quite sure this is something in my control - I don't do anything at all about tracking.

I don't know, I have the guardian enabled.
Anyway on a reddit post I found a suggestion to delete guardian history for this issue, and rebuild guardian borders. for now it seems to be working

[mbucchia]

1 hour ago, Gun Jam said:

I have a 4090

You're GPU is pretty fast already, so VRS-style Foveated Rendering isn't going to help that much.

[biotech]

hello, @mbucchia!

is there any chances to see DFR compatible with OXRTK in future? i miss image adjustment options, such as contrast, saturation, sunglasses, e.t.c.

[nikoel]

9 hours ago, VirusAM said:

I don't know, I have the guardian enabled.
Anyway on a reddit post I found a suggestion to delete guardian history for this issue, and rebuild guardian borders. for now it seems to be working

I've had the same issues. The only consistency of this bug is that it seems to happen right when I am lining up the pipper on target, or about to trap on a carrier

I'm giving DCS a miss for a while, F16 and F/A-18's A2A gun targeting is completely broken now and they are my favourite planes to fly

[mbucchia]

6 hours ago, biotech said:

hello, @mbucchia!

is there any chances to see DFR compatible with OXRTK in future? i miss image adjustment options, such as contrast, saturation, sunglasses, e.t.c.

Can you try it today?

1) you want to make sure Meta-Foveated was installed AFTER OpenXR Toolkit. If you are unsure, just reinstall Meta-Foveated. 

2) enable OpenXR Toolkit and toggle Safe mode.

3) start DCS... it should work and not crash.

4) in the OpenXR Toolkit menu, go to the Menu tab and choose Restore defaults.

5) disable Safe mode and restart DCS.

Now if this works, you should have both programs working at the same time, but there are some options in OpenXR Toolkit that you really need to avoid, like the Foveated Rendering, the FOV adjustment, the Zoom... some of these options will either cause crashes or just produce incorrect visuals...

Let me know if that works.

[Werewolf_fs]

 

hace 46 minutos, mbucchia dijo:

¿Puedes probarlo hoy?

1) desea asegurarse de que Meta-Foveated se instaló DESPUÉS de OpenXR Toolkit. Si no está seguro, simplemente reinstale Meta-Foveated. 

2) habilite OpenXR Toolkit y cambie el modo seguro.

3) inicie DCS...  debería funcionar y no bloquearse.

4) en el menú OpenXR Toolkit, vaya a la pestaña Menú y elija Restaurar valores predeterminados.

5) deshabilite el modo seguro y reinicie DCS.

Ahora bien, si esto funciona, debería tener ambos programas funcionando al mismo tiempo, pero hay algunas opciones en OpenXR Toolkit que realmente necesita evitar, como el renderizado Foveated, el ajuste FOV, el zoom... algunas de estas opciones ya sea causar bloqueos o simplemente producir imágenes incorrectas...

Déjame saber si eso funciona.

I have both working fine, but it causes a 2-4 MS increase in CPU and GPU usage, compared to just DFR

[biotech]

1 час назад, mbucchia сказал:

Let me know if that works.

it's working!

thank you very much!

[MHAce75]

vor 20 Stunden schrieb mbucchia:

Can you try it today?

1) you want to make sure Meta-Foveated was installed AFTER OpenXR Toolkit. If you are unsure, just reinstall Meta-Foveated. 

2) enable OpenXR Toolkit and toggle Safe mode.

3) start DCS... it should work and not crash.

4) in the OpenXR Toolkit menu, go to the Menu tab and choose Restore defaults.

5) disable Safe mode and restart DCS.

Now if this works, you should have both programs working at the same time, but there are some options in OpenXR Toolkit that you really need to avoid, like the Foveated Rendering, the FOV adjustment, the Zoom... some of these options will either cause crashes or just produce incorrect visuals...

Let me know if that works.

Interesting finding. I set OXRTK to safe mode, and after I installed Meta-Foveated I see the OXRTK in both eyes.

[mbucchia]

4 hours ago, MHAce75 said:

Interesting finding. I set OXRTK to safe mode, and after I installed Meta-Foveated I see the OXRTK in both eyes.

Don't worry about that, it's just the way the menu is drawn in safe mode to make sure it'll be visible. You're only going to be in safe mode for like 30 seconds, just to go get this Restore defaults, then you'll leave Safe mode.

[MHAce75]

vor 2 Stunden schrieb mbucchia:

Don't worry about that, it's just the way the menu is drawn in safe mode to make sure it'll be visible. You're only going to be in safe mode for like 30 seconds, just to go get this Restore defaults, then you'll leave Safe mode.

oic.

[slughead]

On 7/11/2023 at 3:26 PM, nikoel said:

I've had the same issues. The only consistency of this bug is that it seems to happen right when I am lining up the pipper on target, or about to trap on a carrier

I'm giving DCS a miss for a while, F16 and F/A-18's A2A gun targeting is completely broken now and they are my favourite planes to fly

I'm still having issues. So far not dropped to 3DOF but goes black screen with a warning message that tracking is lost. I think this is a headset bug. I have performed a factory reset and as part of that the guardian is recreated. Will monitor.

[DayGlow]

@mbucchia I have found that the improved dot mod 

Isn't compatible with foveated rendering. Just wondering if there could be a simple solution to this. If not I probably will choose to go with the foveated rendering with dot labels, just hoping this can be fixed somehow.

Edited July 16, 2023 by DayGlow

[zildac]

@mbucchia I have found that the improved dot mod 
Isn't compatible with foveated rendering. Just wondering if there could be a simple solution to this. If not I probably will choose to go with the foveated rendering with dot labels, just hoping this can be fixed somehow.

What are you experiencing when you say "not compatible"? I'm running both and haven't noticed any detrimental effect.

[DayGlow]

31 minutes ago, zildac said:

36 minutes ago, DayGlow said:

@mbucchia I have found that the improved dot mod 
Isn't compatible with foveated rendering. Just wondering if there could be a simple solution to this. If not I probably will choose to go with the foveated rendering with dot labels, just hoping this can be fixed somehow.

What are you experiencing when you say "not compatible"? I'm running both and haven't noticed any detrimental effect.

dots aren't visible. I uninstalled the foveated rendering and could see the dots again. doing it back to back and there is a clear difference. Very easy to see if you edit the dot size to something ridiculously large. Very easy to see when DFR is uninstalled, but disappears when I install it again. 

edit

I've messed around a bit more and it does work somewhat. It seems to have some weird behavior. I found that any supersampling of the focus area at all makes the dots go away for the most part. By increasing the dot size to something huge I've found that the foveated area shows the huge dots, but the center area doesn't with any supersampling introduced. I was running with 1.5 for the center area, which made the dots disappear completely.

When I go back to regular-sized dots they are definitely harder to see with no supersampling compared to removing the DFR layer. 

Edited July 16, 2023 by DayGlow

[mbucchia]

That sounds like issues you need to report to the author of the mod. Please remember that my DFR support isn't really doing much at the game level, it's doing thing at the OpenXR/platform level. So this type of "visuals aren't correct" are bugs of the content (game or mods).

[DayGlow]

Sorry, I didn't expect you to fix anything, just wondering if you would have an insight on what would be going on that would affect the mod as a starting point in finding a solution. I understand that you would have no way in changing the mod. 

Edited July 16, 2023 by DayGlow

[Whistler_RIO]

Just a headsup and thanks to Mbuccia , but a new revision for this was released today.  v1.0.1 - works just as well for me as before. 

https://github.com/mbucchia/Quad-Views-Foveated/releases/tag/1.0.1

 

[recoilfx]

  Hi @mbucchia,

First of all, thanks for all your work on the OpenXR front!

As for Quad-Views-Foveated, after some testing, I noticed that I am actually getting performance decrease when it's enabled. I know the eye tracking works as I can see the the blurry spots at times (and also during loading screen when everything freezes and you can see the frozen low res regions.) The performance drop is up to 3-4ms, which is huge.

My system is a 5800x3d/4090(driver version 536.67)/Win11 running at 1.3x@72hz resolution on the Oculus App. I've tried everything from disabling turbo mode, lowering the peripheral and focus multipliers, and while these help a little (.5-1ms decrease), it never catches up to the vanilla setup while looking worse. I don't have any other OpenXR layers running other than XRNeckSafer. OXRTK is uninstalled. I've tried disabling hardware GPU scheduling and ran at 1x resolution and still getting worse performance.

Any idea as to what's happening?

Here is the my log:

2023-07-21 12:49:50 -0400: XR_APILAYER_MBUCCHIA_quad_views_foveated layer (v1.0.1) is active
2023-07-21 12:49:50 -0400: Using layer: XR_APILAYER_MBUCCHIA_quad_views_foveated
2023-07-21 12:49:50 -0400: Using layer: XR_APILAYER_NOVENDOR_XRNeckSafer
2023-07-21 12:49:50 -0400: Cannot satisfy implicit extension request: XR_EXT_eye_gaze_interaction
2023-07-21 12:49:50 -0400: Requested extension: XR_KHR_D3D11_enable
2023-07-21 12:49:50 -0400: Requested extension: XR_KHR_visibility_mask
2023-07-21 12:49:50 -0400: Requested extension: XR_OCULUS_audio_device_guid
2023-07-21 12:49:50 -0400: Blocking extension: XR_VARJO_quad_views
2023-07-21 12:49:50 -0400: Requesting extension: XR_FB_eye_tracking_social
2023-07-21 12:49:50 -0400: Application: DCS World
2023-07-21 12:49:50 -0400: Using OpenXR runtime: Oculus 1.87.0
2023-07-21 12:49:50 -0400: Trying to locate configuration file at 'C:\Program Files\OpenXR-Quad-Views-Foveated\settings.cfg'...
2023-07-21 12:49:50 -0400:   Found option 'smoothen_focus_view_edges=0.2'
2023-07-21 12:49:50 -0400:   Found option 'sharpen_focus_view=0.7'
2023-07-21 12:49:50 -0400:   Found option 'peripheral_multiplier=0.4'
2023-07-21 12:49:50 -0400:   Found option 'focus_multiplier=1.1'
2023-07-21 12:49:50 -0400:   Found option 'horizontal_focus_section=0.5'
2023-07-21 12:49:50 -0400:   Found option 'vertical_focus_section=0.5'
2023-07-21 12:49:50 -0400:   Found option 'turbo_mode=1'
2023-07-21 12:49:50 -0400: Trying to locate configuration file at 'C:\Users\Zinj\AppData\Local\Quad-Views-Foveated\settings.cfg'...
2023-07-21 12:49:50 -0400:   Found option 'sharpen_focus_view=0'
2023-07-21 12:49:50 -0400:   Found option 'focus_multiplier=1'
2023-07-21 12:49:50 -0400:   Found option 'turbo_mode=0'
2023-07-21 12:49:50 -0400:   Found option 'peripheral_multiplier=0.4'
2023-07-21 12:49:50 -0400:   Found option 'horizontal_focus_section=0.45'
2023-07-21 12:49:50 -0400:   Found option 'vertical_focus_section=0.45'
2023-07-21 12:49:50 -0400: Using OpenXR system: Meta Quest Pro
2023-07-21 12:49:50 -0400: Eye tracking is supported
2023-07-21 12:49:50 -0400: Recommended peripheral resolution: 960x986 (0.400x density)
2023-07-21 12:49:50 -0400: Recommended focus resolution: 1080x1108 (1.000x density)
2023-07-21 12:49:50 -0400:   Stereo pixel count was: 11827200 (2400x2464)
2023-07-21 12:49:50 -0400:   Quad views pixel count is: 4286400
2023-07-21 12:49:50 -0400:   Savings: -63.8%
2023-07-21 12:49:59 -0400: Session is using quad views
2023-07-21 12:49:59 -0400: Edge smoothing: 0.20
2023-07-21 12:49:59 -0400: Sharpening: Disabled
2023-07-21 12:49:59 -0400: Turbo: Disabled

Again, thank you for all your work!

[mbucchia]

5 minutes ago, recoilfx said:

Any idea as to what's happening?

You are likely CPU-limited. Foveated Rendering only helps with GPU performance, if your CPU is the bottleneck, Foveated Rendering will not help, and actually Quad Views will increase your CPU load, and make your performance worse.

Use the DCS performance graph to see where you are - but everything you said is pointing to you being utterly CPU-limited.

[edmuss]

@recoilfx what actual FPS/appGPU frametimes are you getting?

Running 35ppd in the aero and mostly high DCS settings I typically get between 75 and 90 fps. To the best of my knowledge the performance between varjo foveated and QVFR is pretty much the same.

[freehand]

10 minutes ago, edmuss said:

@recoilfx what actual FPS/appGPU frametimes are you getting?

Running 35ppd in the aero and mostly high DCS settings I typically get between 75 and 90 fps. To the best of my knowledge the performance between varjo foveated and QVFR is pretty much the same.

Your 3080ti runs the aero ok ?

[recoilfx]

1 hour ago, mbucchia said:

You are likely CPU-limited. Foveated Rendering only helps with GPU performance, if your CPU is the bottleneck, Foveated Rendering will not help, and actually Quad Views will increase your CPU load, and make your performance worse.

Use the DCS performance graph to see where you are - but everything you said is pointing to you being utterly CPU-limited.

 

15 minutes ago, edmuss said:

@recoilfx what actual FPS/appGPU frametimes are you getting?

Running 35ppd in the aero and mostly high DCS settings I typically get between 75 and 90 fps. To the best of my knowledge the performance between varjo foveated and QVFR is pretty much the same.

I don't think I am limited by my CPU. Please see the attached screenshots. With quad-views, I am getting around 16ms, and without, ~12ms. Both DCS and Oculus performance graphs are saying I am GPU bound. Turbo and ASW are turned off to get more accurate readings.

Here is my settings.cfg for quad-views-foveated

sharpen_focus_view=0

focus_multiplier=1
turbo_mode=0
peripheral_multiplier=0.4
horizontal_focus_section=0.45
vertical_focus_section=0.45

The Quest Pro is currently running at 90hz, 5408x2736 (1.5x render resolution).

[recoilfx]

Also, here is my DCS graphics settings in case it makes any difference - I think they are pretty reasonable for a 5800x3d/4090 build.