Qcumber

That's a good point. Maybe I should just roll back and wait. I would agree that SSW has had the issue that when rolling there was a horrible jumping and ghosting. However, when I tried again earlier this week I did not see this so I had presumed SSW had been updates. I can't see anything in the logs though, a maybe it's something has changed in DCS or something I've done!? I run at 72Hz and SSW set to auto. This is a nice balance so that most situations I have a steady 72 FPS and it only drops when I am low over a city or similar. In high altitude combat I get a fluid 72 FPS with none of the movement artefacts of motion reproduction. Low over a city I have smooth ground movement. It's not perfect as there are some jitters in the transition. ASW is great until your FPS drops below 36 fps (or 45 if you are running at 90), then it is a stutterfest. VD is better at this. ASW also allows you to keyboard toggle through the different modes (via OTT) but VD only allows this via the menu. ASW kicks in as soon as the fps drops below 36/45 but SSW appears to have a more dynamic process so is not constantly switching. I would love to see some significant improvements in both ASW and SSW but not sure what priority is being given by meta or VD. QVFR also appears to break v68. You are not the only one. However, I don't think this is part of Meta's agenda. They want standalone headsets. We really do need an affordable DP headset with eye tracking.

Wow! Great pics. I'm in North Wales on holiday this week so hoping to go to the Mach loop The last one looks like you are on an intercept!

LOL. And that's why it is so difficult to share settings.

Good point. Another thing to consider is link sharpening. Set at the default settings it is way too sharp. I find that off or quality setting works best. This might make meta look artificially "better" than VD. This also depends on AA method. MSAA needs less sharpening, DLAA/DLSS needs more, a lot more. For the best comparison turn off meta sharpening and apply the same sharpening for both meta and VD. For example in game at 0.5.

I agree that meta still has the edge with the encoding. However, the issue is that meta keeps breaking for DCS. V68 does not work with QVFR. With each version if VD the quality gets closer to meta cable. To compare VD and meta cable you need to do a like for like comparison. I have previously spent a lot of time comparing each at the same resolution and with the same QVFR settings. The image quality difference is very subtle but in favour of meta. However, there are other factors to consider. VD is better optimised for QVFR and this is likely to get better still. Meta used to have better motion reproduction but on my last test (2 days ago) VD is now about equal. VD works with turbo mode but this causes meta to crash (at least for me and others on this forum). If meta worked consistently and there was evidence of continued support and development for pc games, then I would be happy. Unfortunately this does not appear to be on their agenda. Once the v68 issue is resolved I will do another like for like comparison but until then I will stick with VD. For a long term solution I think VD will be the only sensible option. I just wish meta would allow access to cable link so that VD could have this option.

VD does not have integrated eye tracking. It still relies on QVFR. Check your QVFR config file and overall resolution. You need to make sure you are comparing like for like. Make sure the overall resolution is the same with VD as for your meta settings.

The only issue with quoting multipliers is when there are several layers. It's then difficult to know what the final resolution will be. OXRTK has a useful function which shows you the overall Res when set to NIS or FSR (without scaling applied). It's easy to over supersample without realising.

If you use QVFR the aircraft appears as a blurred blob in your peripheral vision. I think this would fit your idea. Our eyes are set up to have high acuity at the fovea (centre of the retina) for lots of detail. Our peripheral vision is lower Res but is better at picking up moving targets etc. "I saw it out of the corner of my eye". This would suggest that this might be the realistic option. However, it would depend on how "blobby" objects in the peripheral vision are.

The spotting system looks a lot better since the last update. I can see distant aircraft as a dot rather than a blob and you start to notice details at a more realistic range. Zooming in is also more realistic than it was. The only issue is with QVFR. The lower Res areas still display a blurry blob rather than defined pixels.

I have not noticed any performance hit. In fact I have been able to maintain a better FPS over built up areas than I used to. No benchmarks. Just running some of my standard instant missions for comparison. If you have not already done so maybe clear the shader caches and check there are no mods interfering.

I would advise 72 Hz rather than 90. A scaling of 2 (in OTT?) would only be necessary if your base resolution is unmodified in the meta app. Overall aim for about 4000 pixels. This is equivalent to Godlike x1.3. See below for QVFR settings. SSW is better than it used to be but generally not quite as good as ASW. The bitrate of link cable is better than anything you can get through WiFi but if you have a good, dedicated router you can get 400 Mbps with h264+. However, you don't need it. I run mine at about 200 Mbps as the latency is much better. QVFR Is better optimised for VD, as per the post above. Less noticeable transition and faster tracking. I use centre 1.3 (boosting Godlike), edges 0.4, size 0.4x0.3. I don't really use OXRTK anymore other than contrast tweaks. It would be nice if VD had more nuanced colour and contrast adjustments.

I'll keep my fingers crossed.

Any update on if/when QVFR will be included in VD?

OK. Since I updated to 3.7.20 DLSSTweaks has stopped working. I've updated Nvidia drivers and reinstalled DLSSTweaks but no joy. Any ideas?

I've given up with meta software. I tried VD again since the v68 update and it's running very well. I am fed up with meta constantly breaking things.

Future updates for VD aim to integrate QVFR. At least according to some posts on Discord by mbucchia a few weeks ago. This should make integration of QVFR much better. Welcome to the QP. It is still an amazing headset and often overlooked now.

Unfortunately no fix for the meta v68 problem. I am using QVFR without OXRTK and it crashes every time.

Yes, to change the DLSS presets you need to use DLSStweaks. First install the latest version of DLSS (3.7.20) then use DLSStweaks to change the presets and the scaling (if you want to).

Just to clarify, is this with VD?

I use these settings when I use MSAA and it works pretty well. That can be several things. Some instant action scenarios are still set with the old clouds. Updating to the newer weather helps. Setting clouds to "ultra" can help too. I also find that MSAA makes the clouds look more shimmery. My current DLSS settings use manually installed DLSS 3.7.10 with DLSStweaks to change the preset to F and alter the scaling. I have scaling at 0.9 so it is indistinguishable from DLAA but better fps. You can get away with dropping it to .7 without much noticable difference in quality. I find that DLSS or DLAA are best for antialiasing. MSAA is really jaggy at times. But is sharper than DLSS. I switch between MSAA and DLSS depending on what mission I am playing.

Happy to help. What specific setup information are you looking for?

It doesn't really matter too much where you supersample. The usual recommendation though is to do so in oculus rather than PD in DCS. Overall you need to aim for about 3200 pixels. Things have moved on quite a bit since the post you quoted. The latest version of DLSS (3.7.10) is a lot better. Sharper (but not as sharp as MSAA) with minimal blurring and very good antialiasing.

I have only just updated to using the latest version of DLSS (manual install). This looks quite a lot better than the previous version. Sharper and less movement blur. I'm not sure if it is the DLSS update, the DCS update or both. Has anyone noticed any improvements?

Same issue for me but not all the time. Quest Pro and cable link. Running light scenarios which don't stress my GPU too much I have no issues but if the GPU is maxed out and the max frame rate drops below 72fps then I get terrible jitters. I'll turn off QVFR and wait for the fix.

I've not used it for a few weeks.