VR Quad Foveated Rendering Oculus Meta Quest 3

[edudix]

Hey guys!

I´m using the VR Quad Foveated Rendering Oculus Meta Quest 3 from: https://github.com/mbucchia/Quad-Views-Foveated/wiki

Some of you are probably using it. I have tested it and has improve my FPS and rendering performance significantlly.

However when facing the sun appears the "rectangle effect". Does anyone suffered it? I guess so. Any tip to remove it?

I´ve been playing with the script settings with no effect, do not know why.

Any suggestions will be more than welcome.   

Herewith a picture of the effect.

Edited March 8, 2024 by edudix

[speed-of-heat]

you can minimise it by turning of Camera Lens Effects, specifically Flare...  but it will still be there, ED needs to make changes to the code in order for this "not" to be a problem 

[speed-of-heat]

there is already a bug opened on this 

[edudix]

51 minutes ago, speed-of-heat said:

you can minimise it by turning of Camera Lens Effects, specifically Flare...  but it will still be there, ED needs to make changes to the code in order for this "not" to be a problem 

Yes it solves the problem. Is there another way to solve it by changing parameters in the script? I mean the settings-cfg.

[speed-of-heat]

6 minutes ago, edudix said:

Yes it solves the problem. Is there another way to solve it by changing parameters in the script? I mean the settings-cfg.

nope .. its something to do with the way DCS renders images as i understand it... and requires a change, you will still get it but itis much fainter, its worst at night landing on the carrier ... when you are on deck the runway lights appear like big bright squares ...

[edudix]

2 hours ago, speed-of-heat said:

nope .. its something to do with the way DCS renders images as i understand it... and requires a change, you will still get it but itis much fainter, its worst at night landing on the carrier ... when you are on deck the runway lights appear like big bright squares ...

I´ve to checked it at night. So is there topic for DCS to solve it?

[speed-of-heat]

there is damned if i can find it off the top of my head 

[speed-of-heat]

here you go 

[Madman3353]

On 3/8/2024 at 11:00 AM, edudix said:

Hey guys!

I´m using the VR Quad Foveated Rendering Oculus Meta Quest 3 from: https://github.com/mbucchia/Quad-Views-Foveated/wiki

Some of you are probably using it. I have tested it and has improve my FPS and rendering performance significantlly.

However when facing the sun appears the "rectangle effect". Does anyone suffered it? I guess so. Any tip to remove it?

I´ve been playing with the script settings with no effect, do not know why.

Any suggestions will be more than welcome.   

Herewith a picture of the effect.

 

How does foveated rendering work on the quest 3 if the quest 3 does not have eye tracking? The wiki link refers to the quest pro which has it and is different than the quest 3. I’m new to the DCS vr scene and interested in a better performance.

[diego999]

1 hour ago, Madman3353 said:

How does foveated rendering work on the quest 3 if the quest 3 does not have eye tracking? The wiki link refers to the quest pro which has it and is different than the quest 3. I’m new to the DCS vr scene and interested in a better performance.

It works on fixed mode, same as the 'fixed foveated rendering' in OpenXT Toolkit. That's what I use (I have a Quest 2).

You might want to try both and see which one works better for you.

 

[whitav8]

Just how much (percentage) roughly does quad-view foveated rendering improve performance for a Quest3 on a RTX3080ti running godlike resolution?

[Qcumber]

2 hours ago, whitav8 said:

Just how much (percentage) roughly does quad-view foveated rendering improve performance for a Quest3 on a RTX3080ti running godlike resolution?

That depends on the QVFR settings but it should be at least 30% at default. This also depends on how much your CPU is being used. 

[whitav8]

Thanks for the response Qcumber. I really should have asked how much roughly is QVFR faster than FFR from OpenXR toolkit since I already use that (but is it really active with Virtual Desktop - even though I see the appCPU/GPU timings??)

[Qcumber]

6 minutes ago, whitav8 said:

Thanks for the response Qcumber. I really should have asked how much roughly is QVFR faster than FFR from OpenXR toolkit since I already use that (but is it really active with Virtual Desktop - even though I see the appCPU/GPU timings??)

FFR in OXRTK is different from QVFR. I would try both. In many situations QVFR is better. 

[fastfed]

So I installed this and holy crap it looks amazing! 

 

That said I don't get my setting though,

I only see the option for Quad view in OpenXR while its in safe mode, if I take it out of safe mode it no longer shows up, I also noticed it only works using steamVR and I usually just use oculus and set  the oculus app as the open XR runtime.

I also always used FSR in openxr but it seems with this setup Im getting the same fps with it off, so I might as well leave it off?

 

what am I doing wrong here

Edited August 20, 2024 by fastfed

[Qcumber]

9 hours ago, fastfed said:

So I installed this and holy crap it looks amazing! 

 

That said I don't get my setting though,

I only see the option for Quad view in OpenXR while its in safe mode, if I take it out of safe mode it no longer shows up, I also noticed it only works using steamVR and I usually just use oculus and set  the oculus app as the open XR runtime.

I also always used FSR in openxr but it seems with this setup Im getting the same fps with it off, so I might as well leave it off?

 

what am I doing wrong here

 

Make sure you follow all the setup tasks in the guide. There is an additional step to enable eye tracking with meta. 

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

[Phantom711]

vor 10 Stunden schrieb fastfed:

I only see the option for Quad view in OpenXR while its in safe mode, if I take it out of safe mode it no longer shows up

First of all, you are probably talking about the OpenXR Toolkit Companion. This in itself is not OpenXR…it is just a toolkit. OpenXR is there regardless whether this toolkit is enabled or not.

Besides, I‘m not really sure what you mean by that statement. What „option for Quad View“ do you mean? 
 

If you have quadviews installed correctly, it should work also with Oculus Link and Oculus set as OXR runtime.

Check out the QVFR instructions if you want to play with the settings file a little bit.

Edited August 20, 2024 by Phantom711

[fastfed]

9 hours ago, Phantom711 said:

First of all, you are probably talking about the OpenXR Toolkit Companion. This in itself is not OpenXR…it is just a toolkit. OpenXR is there regardless whether this toolkit is enabled or not.

Besides, I‘m not really sure what you mean by that statement. What „option for Quad View“ do you mean? 
 

If you have quadviews installed correctly, it should work also with Oculus Link and Oculus set as OXR runtime.

Check out the QVFR instructions if you want to play with the settings file a little bit.

 

This is what I see with safe mode off

 

nulland with safe mode on you can see it shows the option to kill foveated rendering kill switch. It just looks as if its in safe mode its enabled and if its not in safe mode its not. 

That said I do see it working with it not in safe mode, just dont have an option to turn it off I  guess? at least not on the fly

 

also on a side note, no matter what resulution I se either in steam VR or render resolution in oculus per eye, nothing changes. I really hate doing settings for VR, its really a PITA EDIT** After reading ito this more, maybe its because Foveated takes over all these setttings? and if I want to change them I have to adjust the settings in the log file? 

 

I read the instructions but its very confusing, if I want to increase my super sampling a little, since I'm pretty much maxing out my FPS , how exactly would I do that and whats the deal with making a new file

 

null

Edited August 20, 2024 by fastfed

[Qcumber]

VR settings can be a pain but they are much easier these days. Keep it simple and start clean. Disable OXRTK and just use QVFR for supersampling and sharpening. You can edit the config file for settings or use this tool.

https://www.digitalcombatsimulator.com/en/files/3332882/

I set my centre resolution to 1.3 with size 0.4x0.3. periphery set to 0.4. 

 

 

[DD_Crash]

I will have to give this a try

[Gryzor]

What are the benefits of using QVFR over openxr toolkit options, in terms of graphic performane? Openxr toolkit has options to make a peripheral fov with less detail. This is not the same as using QVFR??

Of course, I´m talking about Quest 3 which not have eye tracking.

[Phantom711]

@Gryzor

The performance benefits of QVFR are a bit higher if your CPU is up to the task. It is a bit heavier on the CPU.
It is also more customizable with regards to the desired supersampling settings for the focus and peripheral area.

[sleighzy]

On 8/21/2024 at 6:21 PM, Qcumber said:

VR settings can be a pain but they are much easier these days. Keep it simple and start clean. Disable OXRTK and just use QVFR for supersampling and sharpening. You can edit the config file for settings or use this tool.

https://www.digitalcombatsimulator.com/en/files/3332882/

I set my centre resolution to 1.3 with size 0.4x0.3. periphery set to 0.4. 

 

 

Just a heads-up that you shouldn’t use that tool unless you’re using an eye-tracking headset, for fixed foveated custom config (which should be provided in your own custom file) this will be overwritten any time you click the apply button in that app. 

[sleighzy]

On 8/21/2024 at 6:21 PM, Qcumber said:

VR settings can be a pain but they are much easier these days. Keep it simple and start clean. Disable OXRTK and just use QVFR for supersampling and sharpening. You can edit the config file for settings or use this tool.

https://www.digitalcombatsimulator.com/en/files/3332882/

I set my centre resolution to 1.3 with size 0.4x0.3. periphery set to 0.4. 

 

 

Just a heads-up that you shouldn’t use that tool unless you’re using an eye-tracking headset, for fixed foveated custom config (which should be provided in your own custom file) this will be overwritten any time you click the apply button in that app.

The config docs also mentioning adding custom config to a section named [app:DCS World] if you only want them to apply to DCS. This is not accurate anymore based on my testing as DCS recently changed its process name from “DCS World” to “DCS” so would need to be [app:DCS] instead. Not a big deal, if like me, you’re are just config’ing “global” settings in the custom config file. 

[dureiken]

Hi, would someone have a good GPU limited track to test and compare FFR/QDVFR/nothing and share ?

 

thanks