community advice Dynamic Foveated Rendering - Everything in one page

[gonvise]

Just now, Panzerlang said:

You've lost me. I have 2.0 (two point zero) in the headset. Plus 0.5 in PD, that's a total of 2.5.

Please, only supersampling in one place, preferably on the VR googles tool itself!  And just as he tells you, 2x0'5...

[slughead]

Just now, Panzerlang said:

You've lost me. I have 2.0 (two point zero) in the headset. Plus 0.5 in PD, that's a total of 2.5.

You multiply, not add. The headset will provide the application with a resolution in pixels, i.e., the headset's native resolution multiplied by the headset PD. The application takes that and multiplies it by the application PD.

[Panzerlang]

16 minutes ago, slughead said:

You multiply, not add. The headset will provide the application with a resolution in pixels, i.e., the headset's native resolution multiplied by the headset PD. The application takes that and multiplies it by the application PD.

I was lost before, now I've had a blindfold put on too. Lol.

I just ran it at 1.0 and 1.0. I can't find "Render Resolution" in the log, so I'm putting it here. I'm now clueless how to best set these two values in regard to each other. 

Which is the least taxing on the CPU?

dcs.log

Edited December 12, 2024 by Panzerlang

[slughead]

2 minutes ago, Panzerlang said:

I was lost before, now I've had a blindfold put on too. Lol.

I just ran it at 1.0 and 1.0. I can't find "Render Resolution" in the log, so I'm putting it here. I'm now clueless how to best set these two values in regard to each other. 

Which is the least taxing on the CPU?

dcs.log 90.49 kB · 1 download

Neither is least taxing. The are combined to produce a single render resolution that the app draws its images at.

[Panzerlang]

4 minutes ago, slughead said:

Neither is least taxing. The are combined to produce a single render resolution that the app draws its images at.

Thanks Slug. In the VR preset, with 1.0 and 1.0, I still see the two Migs taxiing past jerking a little but the red message that intermittently flashes up in the FPS window is "Main Thread", not "Rendering Thread". I'm beginning to wonder if maybe my CPU is broken.

Edited December 12, 2024 by Panzerlang

[slughead]

I think we are heading off topic now.

[slughead]

28 minutes ago, Panzerlang said:

I was lost before, now I've had a blindfold put on too. Lol.

I just ran it at 1.0 and 1.0. I can't find "Render Resolution" in the log, so I'm putting it here. I'm now clueless how to best set these two values in regard to each other. 

Which is the least taxing on the CPU?

dcs.log 90.49 kB · 1 download

I’m assuming you are using QVFR hence four resolutions are shown.

[Panzerlang]

Yes, QV DFR.

I love ChatGPT. So Pimax 1.0 is 100% native resolution.

I've switched off everything that hits the CPU but still the two Migs have issues. I don't know how many other AI entities are doing stuff in the Cold Start mission but if a 13900k 15 P-Core CPU at 5.5ghz can't handle basic-level DCS without tripping over its shoelaces I think I'll take up Solitaire. Lol.

Thanks Slug.

[slughead]

5 minutes ago, Panzerlang said:

So Pimax 1.0 is 100% native resolution

Yes, I’m sure I said that.

Off topic so start a new thread if you want help on performance of your machine. Check you are running xmp profile for your RAM. Check you are not running intel defaults for CPU, check CPU is not thermal throttling.

[zacsac]

Are people still playing with PD in DCS?! Just leave it at one and config DFR and the PPD in whatever vendor tool you are using (Varjo Base, Pimax etc).

How do you do this with a Quest Pro? I’ve been out of VR for a while and trying to get back into. However, I am finding it hard to get an up to date guide on A) how do I enable Quadviews and Dynamic Foveated rendering, B) how and where (as in what tools) do I use to optimize it and lastly C) do I even need Quadviews now that DCS has this setting natively in the current build.





Sent from my iPhone using Tapatalk

[slughead]

3 minutes ago, zacsac said:

How do you do this with a Quest Pro?

It's all explained in the first post of this thread.

3 minutes ago, zacsac said:

do I even need Quadviews now that DCS has this setting natively in the current build.

Yes. DCS does not include the code for quad view foveated rendering. Just the means to enable/disable it.

[mbucchia]

1 hour ago, slughead said:

It's all explained in the first post of this thread.

Yes. DCS does not include the code for quad view foveated rendering. Just the means to enable/disable it.

The guide is now a little out of date. Could someone do me a favor and send me a screenshot of the setting in DCS to enable QV? I will amend the wiki guide with it. Thanks!

Edited December 26, 2024 by mbucchia

[WipeUout]

46 minutes ago, mbucchia said:

Could someone do me a favor and send me a screenshot of the setting in DCS to enable QV? I will amend the wiki guide with it. Thanks!

nullYou have to scroll all the way down, it is in VR section.

[mbucchia]

1 hour ago, WipeUout said:

nullYou have to scroll all the way down, it is in VR section.

Thanks. What does the eye tracking option does?

[zildac]

3 hours ago, mbucchia said:

The guide is now a little out of date. Could someone do me a favor and send me a screenshot of the setting in DCS to enable QV? I will amend the wiki guide with it. Thanks!

Welcome back! You've been sorely missed

[mbucchia]

1 hour ago, zildac said:

Welcome back! You've been sorely missed

I've always been posting here and there. I'll update the documentation, but won't be working on any code.

[Qcumber]

9 hours ago, mbucchia said:

I've always been posting here and there. I'll update the documentation, but won't be working on any code.

Any news on QVFR being integrated into VD? If I remember correctly it was a possibility but there were some issues.

[WipeUout]

12 hours ago, mbucchia said:

Thanks. What does the eye tracking option does?

Not sure if it is just indicating active or not active state, I don't have this feature in my 8KX...

[mbucchia]

8 hours ago, Qcumber said:

Any news on QVFR being integrated into VD? If I remember correctly it was a possibility but there were some issues.

I'm not working on any code anymore. That project was nearly completed but will never be released.

[Qcumber]

37 minutes ago, mbucchia said:

I'm not working on any code anymore. That project was nearly completed but will never be released.

That's a shame but thanks for all your effort. DCS would be unplayable for me without QVFR. 

[toni]

Hi all, after the latest update I see some pixelated clouds when using Quest Pro, was not happening before.

You see the same ?

[slughead]

19 hours ago, toni said:

Hi all, after the latest update I see some pixelated clouds when using Quest Pro, was not happening before.

You see the same ?

Does this happen with QVFR turned off?

[speed-of-heat]

22 hours ago, toni said:

Hi all, after the latest update I see some pixelated clouds when using Quest Pro, was not happening before.

You see the same ?

there is a known issue that impacts one of the cloud presets that came in in the release before the this one 

[FupDuck]

On 12/26/2024 at 4:01 PM, mbucchia said:

Thanks. What does the eye tracking option does?

To answer your question @mbucchia, the eye tracking check box doesn't seem to do anything. I have a Quest Pro, and eye tracking stays enabled whether this box is checked or not (as long as it's enabled in the headset and link software). I tested it using the debug feature, and just by looking at the sun in game. It's very easy to tell when eye tracking is enabled.

 

The other box for QVFR must be checked in order for your software to work. Without this checked, it's the same as if QVFR is not installed. I hope this is helpful info for your edits to the wiki.

 

While I have you here, is it possible to use the QVFR tool only for turbo mode? I've heard you can disable it for certain programs using the config file, but this doesn't work for DCS. It's that still the case?

Thanks!

[sleighzy]

On 12/13/2024 at 10:43 AM, sleighzy said:

Just a heads-up that the horizontal and vertical focal sizes can't be controlled via the Companion app for folk on non-eye tracked headsets. Those settings need to be updated for the "horizontal_fixed_section" and "vertical_fixed_section" directly within the settings.cfg file itself. In addition to this anything saved in the Companion app will overwrite those settings. So for a non-eye tracked headset that app is good for the initial creation of the default settings.cfg file, but after that you should tweak directly within the file.

Update to my earlier comment: The Quad Views Companion app v1.0.14 added support for configuring the height and width of the focal area for fixed foveated rendering (non-eye tracked headsets) a few days ago.

https://github.com/TallyMouse/QuadViewsCompanion/releases