Jive

There can be a lot of tweaking to find the performance you want and some personal preferences My advice is to open the Meta link software and increase the resolution slider to max and set 72hz Depending on if you're using a link cable, wireless via Meta Link or wireless via Virtual Desktop there'll be different bitrate settings available to you. Higher is sharper although may introduce some latency. I couldn't see your config, sorry I can't be more specific with settings but I like DLAA (DLSS is a little too blurry imo but it's viable) and then being as modest as possible with other settings to save performance. Another option is using OpenXR Toolkit to add some simple fixed foveated rendering or using Quadviews which works in a similar way with finer control. With Quadviews you can choose to downsample the edges of your view and increase the resolution of the middle, if you wanted to. Quadviews is more CPU intensive than FFR in OpenXR toolkit iirc.

Instead of increasing PD in DCS I've seen a lot of advice to increase the PD slider to max in the Meta Link software. Mine stays there for everything. You can save some GPU perf by lowering the textures option and seeing if you notice a difference. Another option is using OpenXR Toolkit to add some simple fixed foveated rendering or using Quadviews which works in a similar way with finer control. With Quadviews you can choose to downsample the edges of your view and increase the resolution of the middle, if you wanted to. As above I also like 72hz with DLAA

In the payload list there is a preset for 4x AGM-12C which has the full four. However, trying to manually select AGM on those pylons only offers AGM-12A, AGM-12B or AGM-45A

QVFR can offer you more control over your fixed foveated rendering on Q3. You can fully tweak which resolution multiplier you'd like in the outer area and also choose to super sample the inner area if you like. QVFR will however add some load to your CPU. OXRTK has much less ability to customise to your liking but won't add the CPU load that QVFR does.

Go to your DCS install folder - Mods - campaigns - F-4 MIG Killers You'll see the full list of mission files and you can open whichever portion of the event you like

I wish I could help more. I'd recommend trying on the VD discord, they're active and helpful

I use a 3080ti with VDXR h264+ too, also thought AV1 was a 40 series thing Is the VD performance overlay giving any clues? Any of the different latency indicators spiking when you lose frames?

When you say v68/v69 are you on the PTC or are you saying you've tried both? Someone on the VD discord had a kind of similar thing and it fixed when he disabled the allow remote connection option on the VD Streamer PC app, might be worth a try.

Thanks. I've fully moved over to Virtual Desktop now and I prefer it but good to know. Appreciate your help

Might be a silly question but after doing this fix will be there be any steps required to allow the software update to v69 when it does release?

With Quadviews you have more control over your settings. You can tweak supersample the foveated area for example. QuadViews does add load to your CPU though. OpenXR Toolkit's FFR doesn't give you the option to supersample the central point and limited options for resolutions in the outer area but it's quick and simple. I used OXRTK FFR when I was using my G2 and found it helpful.

FPS wise not necessarily. To me it feels smoother in VD, maybe it's the video buffering feature, I'm not sure. I also prefer VD's SSW to Link's ASW. The h264+ codec with VDXR is nice, even with a bitrate of 200. I also like that you can change the headset refresh rate and the bitrate on the fly if you like, useful when you're experiementing with settings. If you're already happy with Link then I wouldn't sweat it too much but if you have the money to spare for the VD app or you have other uses for it then it's great imo. Just keep in mind that the data is over wireless and not wired so if you think you may suffer network latency and/or aren't using a dedicated router then again maybe just stick with Link.

You don't need OpenXR Toolkit to run QuadViews but you can still use it for things like adjust contrast, brightness, saturation etc.

I just read through this thread in a oner. I love how you started out with "dipping a toe into VR" and now you have a new GPU and CPU

Yes please, thanks!

I have VD running DCS really nicely at the moment so I shouldn't really mess with it but I'm curious if anyone knows where QuadViews takes it's config info from for VD? I made my QV adjustments in the companion app with a pretty aggressive 5% render in the non-foveated region which appears to be the case with Link. For example if I take a screenshot the image is super blurred. When I do the same in VD the image is maybe 25-30% res instead so it seems that it's maybe taking stock config info, which again actually plays really nice but you know, tinkering. @mbucchia am I way off or is it a different config file?

I recently went from my G2 to a Quest Pro (found a sealed one on eBay for the same price as a Q3). I'm very happy now but at first impressions I was a little bit disappointed. I had my G2 in a place where it was running quite nicely at 60hz with DFR. As you know the Quests run via Link (wired or AirLink) or they can run wirelessly with Virtual Desktop (paid app on the Meta store and free desktop app required). Now, everyone has their preferences with how to run their VR setup and I'm not calling anyone wrong or right but personally I wasn't too impressed with the Link experience. I found that the eyetracking wasn't fast enough, I'd often notice the blurry non-foveated region in my peripheral, which ofc you can mitigate with less aggressive settings but it wasn't what I hoped for. I've also tried flying with ASW which I understand a lot of people like but I found it very 'wobbly' like the scenery ripples at times. Contrary to this flying in Virtual Desktop is a night and day improvement for me. With h264+ and VDXR selected even with a bitrate of 200 it's a really nice experience. In Link you can set up to 960 as a bitrate if you have a GPU for it (with a 3080ti I get sound stutters if I crank it that high) and it's worth noting that bitrate x with h264/h265 in Link isn't a direct comparison to bitrate y with h264+ or other codecs available in VD. Again, personal preference but VD's reprojection SSW is nicer to my eyes than ASW in DCS. Eye tracking seems way faster, I rarely catch it out. Overall everything feels much smoother. Getting the best out of VD does require WiFi6. However you can get a decent, cheap router to use as dedicated VR router to get the stability you'd want. I currently don't have a dedicated router but I'm looking at that now since I'm so much happier with VD. Either the Quest 3 or Quest Pro are good options imo. The lenses are great. Just consider the requirement for a $50 router, some money to improve comfort on either model, battery pack is likely too. You'll want the supersampling cranked up to the right in the Meta app. This makes it look great across the lens yet the G2 is still sharper in the sweet spot, especially when looking further away but the benefits of edge to edge clarity with the Quests are a fair trade off. TLDR - Glad I moved from G2 to Quest Pro, I think 3 would be a great choice too. - For me VD > Link by a decent margin - Consider additional costs for comfort, battery, WiFi6

I gave this a test the other day, I didn't spend a lot time with it. The TLDR is that with h264+ I was finding 150-200 to be the max bitrate before latency became an issue. I didn't try any other codecs. A reddit user suggested they often need to restart their PC between uses otherwise latency goes high. YMMV if you're interested enough to try. Instructions are reasonably clear on https://github.com/Genymobile/gnirehtet I'm not technically inclined enough to offer any troubleshooting but others here may be able to. Short version of the instructions Download and isntall Java https://www.oracle.com/java/technologies/downloads/#jdk22-windows Download gnirehtet (Java, not Rust) https://github.com/Genymobile/gnirehtet/releases/download/v2.5.1/gnirehtet-java-v2.5.1.zip Download adb platform-tools and extract to your gnirehtet folder https://dl.google.com/android/repository/platform-tools-latest-windows.zip Double click gnirehtet-run.cmd from your gnirehtet folder. It will open a cmd window on your PC and in the headset you'll see an option to allow a connection request. This is first time only. The cmd box from gnirehtet-run.cmd needs to be running, then you can open VirtualDesktop as you would normally (although I had my Quest wifi turned off). The PC connection will say it isn't on the same network but it will still connect. Done I expected network latency to read zero, it doesn't and it does change with the codec/bitrate. As above I found it to top out at 150ish before latency became an issue with h264+ so it's not super attractive to me at the moment but I thought it might be worth sharing in case anyone with different network circumstances finds it useful.

I used your guide yesterday, worked perfectly. Thanks for writing it!

A few ideas: Make sure OpenXR is set as the default runtime in the Meta Link app. Do you use QuadViews for FFR? That may be stopping DCS from running. There is a known incompatibility with OpenXR Toolkit and QuadViews with Meta version v68 Lastly, double check you're launching in VR with the enable VR headset in the VR options or the launcher option. Although I'm sure you've already looked at that.

Could you share the details on how to do this please? I'd like to stop it from updating too.

I suppose it's that trade off between clarity of Link and local dimming, faster eye tracking in VD. I'm not firm on either option ATM, still trying to find some balance

I used VD for some DCS earlier but I had some networking issues at the time so I switched back to Link via cable and the eye tracking was noticably faster in VD than Link. Eyetracking/Quadviews was my main reason for choosing the QPro over the Q3 and I had been slightly dissapointed with how often I could see the blurring of the non-foveated area off my periphery, mainly with clouds. Increasing the size of the foveated area helps yet this of course reduces the performance gains. I find this much less obvious in VD, which I'm delighted with. With VD providing local dimming, faster eye tracking and a more optimal runtime with VDXR it's all looking very bright. Thanks for all you dedicated work @mbucchia I would have given up VR in DCS without the progress you've brought to the table. Perhaps counter-inuitive for the most part but do you know if we'll ever see a wired option for Virtual Desktop in the future?

Am I crazy or does the eyetracking with QuadViews seem much faster in VDXR? I notice it way more in Link than in VD