Qcumber

Thanks for the correction.

The default setting for DLSS quality is a scaling of about 0.66 and preset E. With DLSS tweaks you can change the scaling and the preset. Preset F appears to be the best one for DCS. I find that a scaling of 0.9 gives identical quality to DLAA but slightly better performance. You can get away with 0.8 as well.

You already have a 4090 so combined with a 13600 you will not likely see much gain. QVFR works better when you have lots of CPU headroom. I see a big improvement with my setup.

The current advice is not to use OXRTK as it appears to cause a lot of issues for some people.

I've spent about 12-15 hours with the latest update and overall the performance in VR has improved. Not necessarily in terms of FPS but smoother and better visuals. DLSS seems to work a lot better. I have been using DLSS 3.7.20 and preset F in the previous DCS version so the only change is the DCS update. Has there been more DLSS optimisation? I have not tested all maps and modules yet but most are better. Unfortunately the F4 feels a bit worse in VR. I keep getting freezes which I think might be related to VRAM overflow as the VRAM usage maxes out then stays stuck until I close and restart DCS. I will try to attach a log tomorrow.

It has improved since the last update. I have found the worst presentation of DLSS smearing is with the Marianas Lagoon Patrol mission. Even with DLSS 3.7.20 and preset F there was still blurring. Since the last DCS update there is none. I did not know why except that perhaps DLSS optimisation within DCS has improved.

Thanks I'll give it a try. I could not find the setting you suggested but I did remove all openxr layers except QVFR. So far no freezing.

Thanks. Just wondered if I had missed any recent changes. You know how rapidly VR develops and new "tweaks" come along. I revisited DLSS recently after some time without any AA and have found that there is now minimal smearing with moving aircraft. The cockpit is as sharp as it can get. It all looks very good (preset F, quality scaling set 0.9).

I am getting an issue with QP since the last meta update and DCS update which sounds like it us the same as yours. As these were about the same time I am not sure if it relates to one or both. I get random periods when the headset loses tracking for 1-2 seconds and the image freezes. It happens with both VD and meta link. I disabled OXRTK and XRNS which seems to reduce the frequency of it happening, so I wonder if this is an open XR layer issue. I need to do some more experimenting. The first thing I will try is reordering the open XR layer. Then removing some of them completely. Are you using QVFR?

Is it necessary to edit the .ini file when DLSS tweaks allows you to change the presets and scaling from within the config tool? I have mine set to preset F.

Try adjusting the DLSS scaling in DLSStweaks. I use 0.9 and get good results.

It will shift some of the processing to the CPU so if you have enough CPU overhead QVFR will increase performance. If you are CPU limited it can make performance worse. In such a case the foveated rendering in OXRTK will be a better option. My post above links to mbucchia's guide for QVFR which is worth a read.

If you have not already done so then I suggest reading this thread on how to use QVFR and mbucchia's guide notes. https://github.com/mbucchia/Quad-Views-Foveated The recent changes in DCS just lets you toggle the QVFR openxr layer on or off in DCS and likewise the headset eye tracking (if available).

If you change sharpening in ODT to quality it will show as blank in OTT. All OTT does is edit the same files as ODT does. It's just a bit more user friendly and has other options. You can use both at the same time. I do. Thinking about this a bit more it does sound like your bitrate is variable for some reason. Try setting the bitrate to about 150 in OTT and see if it still happens. Also check your cable still has a decent bitrate. I had done issues with a cable which started to go bad.

Is it getting pixelated across the whole frame? What does the DCS fps/frametime chart look like? Is there any change in GPU usage as it happens? Are you seeing it in all missions or just some? Not sure if this will help but try resetting distortion curvature to default. You could also reduce the encode resolution as I don't think you need it that high for a Q2. You could disable the encode bitrate and set it manually. I have mine at 960 on the QP. It might although be worth checking your link cable to see if there are any issues with this. You can check this via the desktop app. Unrelated but have you tried setting sharpening to "quality" in Oculus Debug Tool? I find the normal sharpening a bit too harsh.

Duxford BoB? I missed that one unfortunately but I'm going to the end is season one this weekend. Nice shot of the Dragon Rapide cockpit. You must have been sat right at the front.

I use a 4070 with hevc so I would say yes.

With your setup I would suggest using QVFR. Slughead's high end setup does not need it but you might see a noticeable improvement.

I would advise posting your log file in a new thread in VR bugs. Then DCS devs can review it.

Here are my settings. QVFR config: # common settings for all headsets (unless overriden below). smoothen_focus_view_edges=0.1 sharpen_focus_view=0.3 horizontal_focus_section=0.3 vertical_focus_section=0.3 peripheral_multiplier=0.4 focus_multiplier=1.6 debug_eye_gaze=0 debug_focus_view=0 turbo_mode=0 # Fixed Foveated rendering settings for fallback when eye tracker is not available. horizontal_fixed_section=0.5 vertical_fixed_section=0.5 DCS settings: null I have just seen that you have a 4090 so I don't think you will get much from QVFR. I think you would need a more powerful CPU. The 5800x3d gives me lots of headroom with a 4070.

Just fly for a while and enjoy the experience. Then you can tweak things a bit more once you get a better feel for things.

I can get pretty clear cockpit visuals with VR. Not 4k but pretty crisp. The acid test is lean forward. The cockpit should match flat screen at close range.

I'll post my settings later.

Setting for VR is a very long trip. Be prepared for frequent tweaking. My experience over the last couple of years is that the DCS VR experience is getting better. But every update requires some retuning.

Good point. Should be 1.3 but the final resolution is the same.