Qcumber

I bought a dedicated wifi 6 router from Amazon and it works well for me. I have it next to my PC, connected to my main router via a power line adapter. Deal: Mercusys AX1800 Dual-Band Wi-Fi 6 Router, WiFi Speed up to 1201Mbps/5GHz+574Mbps/2.4GHz, 3 Gigabit LAN Ports, Ideal for Gaming Xbox/PS4/Steam & 4K (MR70X), Black https://amzn.eu/d/0e3Yylyt

Get a used Quest Pro if you can. I got mine for £300 on eBay and have never looked back. It has eye tracking so using QVFR massively reduces GPU load. Pico 4 is also a good choice and a bargain price. I have a lot of experience with both of these. I can't really comment on Q3 other than second hand.

I've had enough with meta. VD is the way forward. @mbucchia Is there any update if meta will allow third parties (i.e. VD) to use link cable?

I'm not sure why you are getting a blurry scene. What are your VD settings? Can you post a screenshot of your in game overlay so we can see your latencies etc?

Why are you using a rate lock? Try running full 90Hz and max out your frame rate. Your other latencies look good so if you can manage a 10ms game latency you're winning.

If VD is optimised the differences to link cable are very subtle in terms of quality and performance. It really depends on how good your wifi connection is and that your latencies are well controlled.

I've given up on meta and am now using VD all the time. Quality and performance are very good.

The F-4 is not too bad. It depends on the map and setting. For meiIt has about 10% more GPU use compared to the F-16 but a bit less than the F-14.

I can’t run ASW with turbo on otherwise it freezes when I remove my headset. I can use turbo with SSW and VD but it does not really do anything.

ASW is smooth as long as the fps does not drop below half the refresh rate. If fps drops below 36 for me (72Hz) then it becomes very stuttery with ASW but less so with SSW.

With your ODT settings you have a very high level of supersampling (as has been said earlier in this thread). What is the output from the meta app? Do you have this set to 1 or maxed out at 1.7. Base resolution of QP is 1800x1920 per eye. If this is set at x1 in the meta app then this would give you 3600x3840. If you are set to x1.7 then IDT x2 will give you 6120x6528. I suspect you are running meta at x1. If you compare this to VD at godlike (3072x3216), you need to add a multiplier of 1.2 to get you to the same resolution as with meta. I would suggest doing this in QVFR. You also have sharpening set to "normal". Try it set to "off" and see how that looks. As Slug says, make sure you are using compatible codecs. Try HEVC 10 bit at 150 mbps then check your latencies. If your decide latency is too high (above about 13-14) switch to h274+ at about 300 Mbps. Make sure you are connected to your wifi 6 dedicated router by cable (to your PC) and that your connection speed is at least 870mbps. My router cost me £45 and works really well.

That's the bug when using turbo on meta. It freezes most of the time when you remove your headset. Even for a few seconds.

As I said above have you tried comparing VD and link cable like for like? If you match resolution, sharpening and optimise bitrate, the difference is very subtle.

Yes. But I understand that this is more a case of integrating QVFR into VD rather than VD being able to utilize QVFR as a separate tool. Please could I ask @mbucchia to comment to make sure I have this right?

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.