Search the Community

I recently switched from Meta Link to Virtual Desktop but haven't been entirely happy with the performance until now. My PC is no slouch of a machine: Intel i9-13900k @ 5GHz Asus Nvidia 4090 64GB RAM @ XMP setting NVMe drive for Windows NVMe drive for DCS Windows 11 Pro Quest Pro headset Meta Link and DCS Configuration: Meta Link x1.0 @ 72Hz. DCS PD 1.5 Most, if not all, settings in DCS are maxed out (the configuration can be seen in the attached screenshots). DLSS enabled. Performance Test: I judged performance by flying the instant action, Persian Gulf, ready on-ramp mission with an F-16. It's not a scientific test, but it was a rough guide to see if a patch or driver update had broken something. The goal of the test is to remain out of ASW. Take off, climb to 1200ft. Turn right to the coast, maintaining speed at 450-500kts. When the Burj Khalifa building is almost at my 3 o'clock, pull hard right towards it. Then, I took another hard right again as I passed the building. A well-performing system would make both turns and maintain 72 fps, staying out of ASW. On the switch to VD, my settings were: Godlike resoluton @ 72Hz. DCS settings are the same except for PD. Any PD over 1.0 would cause a drop to ASW with the above test flight on the hard turns. The image quality was identical/similar, but I was unhappy with the performance. I realised that with the Meta Link, I had been using Oculus Tool Tray and had set the FOV to 90%, as some of us found that this gave a performance boost without affecting image quality. Effectively, it reduced the image size that was drawn but just about within the FOV, which was limited by the frame of the lenses. Any more than 90%, and you could start to see the edge of the image as a black rectangle. When I turned off the 90% FOV in Meta Link, the performance was similar to Virtual Desktop. So, to get the performance in VD that I had with Meta Link, I started making some adjustments using the OpenXR Toolkit. OpenXR Toolkit has a FOV setting in the System tab. I set that to 90% but still had lower performance. Then, I looked at the render resolution in the dcs.log and found that it hadn't changed despite a reduced FOV. To change this, I adjusted the display resolution, which was also in the System tab of OpenXR Toolkit. I lowered it to match the resolution created with Meta Link at a FOV of 90% and PD of 1.5. For me, that was 2904x3041. With that change, the performance was back, and I am now fully converted to Virtual Desktop. Yes, Virtual Desktop is more expensive because it requires a dedicated gaming router. You can get cheap ones and expensive ones. Either appears to work. Be sure to pick one from the list of tested routers. Yes, the bit rate is lower with VD. However, that's not an issue if you use one of the newer, more efficient encoders. I am using the HEVC 10-bit encoder, and I can't see a difference compared to H.264 @ 500 Mbps. Yes, Meta Link can run up to 960Mbps (not without distorting the audio via the link). Some say they notice a difference, but I don't. For me, Virtual Desktop offers the peace of mind that Meta won't break DCS by changing their implementation of OpenXR on the Meta Link. It also allows you to see and interact with the Windows desktop, unlike Meta Link, where you have to peek under the headset to launch DCS. All in all, it is a better experience. To top it off, I am now wireless, which makes a huge difference. No more cable tethered to the PC! To maintain the charge of the headset, I use a power bank battery attached to a belt or in my pocket. Yes, there is a cable. I barely notice it. In summary, if you want to get the boost you had with 90% FOV using Meta Link: Find your DCS render resolution for your setup with Meta Link from the dcs.log file. If you are running DLSS, look for "DLSS successfully initialised". Mine is now: "DLSS successfully initialised, 1936x2032 -> 2904x3044". Set the FOV to 90% in OpenXR Toolkit. Adjust the "Display resolution (per eye)" in OpenXR ToolKit to match your old render resolution. Enjoy the performance boost. If you want a sharper image, you must sacrifice high CPU options such as shadows for higher resolution/increased PD.

I finally got MT working relatively smoothly at around 30 fps in the UH-1 Marianas which before would crash Virtual Desktop and Steam VR. 40-50 fps in the NTTR in an A-10A. System Specs, MOBO=ASRock X570 Pro4 CPU=AMD Ryzen 7 5700X, 8 core GPU=Zotac RTX 3060 Ti OC edition, no overclocking, will try under volting and report back. RAM=TEAMGROUP T-Force Vulcan Z DDR4 32GB Kit (2x16GB) 3200MHz (PC4-25600) CL16 Desktop Memory Module DCS Openbeta on a dedicated 2TB NVMe M.2 drive Headset=Pico 4, CAT 8 Ethernet direct from a dedicated 5G router to an Ethernet to USB C adapter, steady 1200 MBPs. For a 3060 card use Nvidia driver 522.25, it has issues with newer drivers. Follow the instructions in these videos. Follow the instructions in this video to install Process Lasso and tune it to control your CPU processes. Set DCS, Steam VR, and Virtual Desktop Priority to high. Set DCS to only use physical cores. https://www.youtube.com/watch?v=M2TEEq5tIGM&ab_channel=Panjno My DCS settings except shadows are on flat, picture attached, VR pixel at 1.0. Steam VR resolution 100%. Nvidia control panel pictures attached. DCS Open Beta 2.8.3.38090. Verify Steam VR files, two were missing from mine. Use a shortcut to the DCS.exe in bin_MT with --force_enable_VR --force_OpenXR at the end of the target. I hope this helps. All credit to Panjno for his how to videos and whoever came up with the force VR shortcut. null

I am using pico 4 with virtual desktop and openxr toolkit and am having consistent crashes when trying to use MT and sometimes with ST. I had some similar issues with a rift s but less frequent. I have deleted shaders etc several times and have done a slow repair. I have also tried running with and without "force VR" etc., and through "injecting" the game in VD. I have attached the last three logs and would appreciate if anyone could offer any advice. 5600x/rx6700/64Gb 3200 RAM/Pico 4/virtual desktop/openxr toolkit. dcs.log-20230402-183248.zip dcs.log-20230402-183139.zip dcs.log-20230402-182258.zip