Quad-Views-Foveated causes a significant drop in frame rate.

[EX_AI]

Thanks very much for the Quad-Views-Foveated plugin, but I seem to be in big trouble right now.

 

I used to use Quad-Views-Foveated on my 4060ti 16G graphics card. With ultra settings and 120% center resolution, it brought about a 20% performance boost, and this plugin was a great help to me at that time.

 

However, when I upgraded to the 5070ti graphics card, the results brought by Quad-Views-Foveated were terrible. Enabling it actually caused the frame rate to drop—by an average of 25% with the default configuration. Moreover, Quad-Views-Foveated itself caused blurring in the center of the view (as mentioned in a post), which led to a decline in image quality. In the end, I got very disappointing results: with Quad-Views-Foveated enabled, both the image quality and frame rate significantly decreased. There was zero positive gain, only a complete negative gain.

 

I have tried many methods and spent a lot of time attempting to fix this, including reinstalling the game, reinstalling the plugin, and even reinstalling the system, but nothing worked—the problem persists...

 

I sincerely request help...

 

Below are my settings screenshots and log files. The test scenario was: cold start of the AH64D in the Persian Gulf.nullnullnullnull

Quad-Views-Foveated.log dcs.log

Edited Friday at 01:57 PM by EX_AI

[Phantom711]

As far as I know QV can have a negative impact in scenarios that are more CPU intense.

other than that, I would suggest not to use DLSS or at least not at the „performance“ setting since it will have a negative impact on image quality.

[Qcumber]

With QVFR you need to have plenty of headroom with your CPU. What are you using? With a 5070ti you need a pretty beefy CPU to make best use of QVFR. 

If you have not done so already try adjusting the QVFR settings. Keep the periphery as low as possible (about 0.4) and a narrow foveated region (about 0.25x0.25). With DLSS set the foveated region to at least 1.5 to counter the ghosting. 

[EX_AI]

6小时前，Phantom711说：

As far as I know QV can have a negative impact in scenarios that are more CPU intense.

other than that, I would suggest not to use DLSS or at least not at the „performance“ setting since it will have a negative impact on image quality.

But, the current issue is that there seems to be "negative impact" everywhere: My CPU is 14600KF, and it can stably run at 80 frames per second in the AH64D - Persian Gulf cold start mission without QVFR enabled; but once QVFR is turned on, the frame rate drops to 57 - 60 frames per second right from the start of the mission.

And,I haven't tested the frame rate with DLSS turned off, but isn't DLSS supposed to bring significant performance improvements? So why not keep it on....?

Edited yesterday at 12:55 AM by EX_AI

[EX_AI]

5小时前，Qcumber说：

With QVFR you need to have plenty of headroom with your CPU. What are you using? With a 5070ti you need a pretty beefy CPU to make best use of QVFR. 

If you have not done so already try adjusting the QVFR settings. Keep the periphery as low as possible (about 0.4) and a narrow foveated region (about 0.25x0.25). With DLSS set the foveated region to at least 1.5 to counter the ghosting. 

My CPU is 14600KF, which should have considerable headroom. Because before I upgraded my configuration, I was using just a combination of 12400KF + 4060Ti 16GB, but back then QVFR could work normally and deliver excellent performance.

[EX_AI]

It would be great if VR could have a universal driver-level frame generation feature like Smooth Motion...

[mrsylvestre]

7 hours ago, EX_AI said:

It would be great if VR could have a universal driver-level frame generation feature like Smooth Motion...

Most VR solutions do. It's called retroprojection / ASW / SSW. It generates a fake frame every second frame AND takes into account your head movements as reported by the virtual headset for that (something that 2D solutions like smooth motion obviously cannot do as these don't have access to the headset accelerometers data). Like other solutions, it is not perfect (ghosting when looking sideways, artefacts when looking through the prop in MSFS, some also experience motion sickness). In the end, there is only so much that upscalers, frame generators and others can do.

[EX_AI]

1小时前，mrsylvestre说：

Most VR solutions do. It's called retroprojection / ASW / SSW. It generates a fake frame every second frame AND takes into account your head movements as reported by the virtual headset for that (something that 2D solutions like smooth motion obviously cannot do as these don't have access to the headset accelerometers data). Like other solutions, it is not perfect (ghosting when looking sideways, artefacts when looking through the prop in MSFS, some also experience motion sickness). In the end, there is only so much that upscalers, frame generators and others can do.

The SSW function of VD doesn't work well. It often causes ghosting which leads to dizziness. When piloting rotorcraft such as the Apache, it creates severe "jelly effect" on the areas swept by the rotors as well as the subtitles/HMD display in those areas, making the game unplayable.

[Phantom711]

vor 12 Stunden schrieb EX_AI:

And,I haven't tested the frame rate with DLSS turned off, but isn't DLSS supposed to bring significant performance improvements?

Yes, but you also reported poor image quality, hence my suggestion to try with DLSS off or at least set to Quality. In order to rule out DLSS as the cause of your perceived loss in image quality.

What headset are you using actually? You also alluded to the fact that you are using VD?

Right now I don‘t have a solution to your problem. QVFR works fine to me with a QuestPro. I don‘t fly helicopters though…

[EX_AI]

3小时前，Phantom711说：

是的，但您也报告了图像质量较差，因此我建议尝试关闭 DLSS 或至少设置为质量。以排除 DLSS 是您感知到图像质量损失的原因。

您实际上使用什么耳机？你还提到你正在使用 VD 的事实？

现在我没有解决你的问题的方法。QVFR 对我来说使用 QuestPro 工作得很好。不过我不开直升机......

No, you misunderstood what I meant. What I mean is: When QVFR is turned on, the picture in VR becomes blurrier than when it's off, and this isn't an isolated case. As for DLSS, I've always had a positive attitude towards it. Apart from some motion blur, it hasn't brought me any negative changes.

 

I use a Quest 3. When I was using the 4060Ti 16G, QVFR worked really well. This problem only started to occur some time after I upgraded to the 5070Ti.

Edited yesterday at 04:08 PM by EX_AI

[Qcumber]

16 hours ago, EX_AI said:

No, you misunderstood what I meant. What I mean is: When QVFR is turned on, the picture in VR becomes blurrier than when it's off, and this isn't an isolated case. As for DLSS, I've always had a positive attitude towards it. Apart from some motion blur, it hasn't brought me any negative changes.

 

I use a Quest 3. When I was using the 4060Ti 16G, QVFR worked really well. This problem only started to occur some time after I upgraded to the 5070Ti.

The image is more blurred when QVFR is enabled for me too if I leave it set at x1. I push the foveated region up to x2 with VD godlike. This gives me very sharp images and no ghosting with DLSS quality. However I have a Quest Pro so can get away with a smaller foveated region due to eye tracking. With centre at x2, 0.25x0.25 and periphery at 0.5 I still get a good performance boost over no QVFR at Godlike. 

[Phantom711]

@EX_AI

What you could try, is to set your FPS limit higher…or to the maximum actually. I just read in another thread, that FPS limits interfere with the turbo mode of QVFR.