Search the Community

The latest version of Pico Connect has a trick up its sleeve. It is now possible to stream OpenXR apps such as DCS World directly to the Pico headsets without going through SteamVR, a capability that was up to now exclusive to Virtual Desktop. This is clearly an experimental feature. The trick is to run the Pico-provided batch file add_runtime.bat located in one of the sub-folders of the Pico Connect application (see windows explorer screenshot, attached) with administrator privileges. It modifies the registry to install Pico Connect's own OpenXR runtime PicoStreamingXR instead of the default SteamVR OpenXR runtime (see SteamVR settings screenshot). It works well with DCS. Performance is quite close to that of Virtual Desktop at comparable resolution. Colors with Pico Connect are more vivid / saturated. It works through Wi-Fi but also directly through USB 3 connection without need of gnireteht or any other shenanigans. Credits for this find go to a user in the Virtualnull Desktop Discord. It is not clear at this stage if this runtime is an original effort by Pico or if they borrowed code from another project. Curious about how this will evolve.

Worse performance in VR than before the update with the stand alone MT version (Minus 15-25 FPS), also MT only runs in OpenXR with Steam VR. Here are all of the ways I have tried to start DCS MT and non-MT. Non-MT started directly from the Virtual Desktop tray icon uses the Oculus runtime and gets me between 35-54 FPS, no jitters. I have attached all of the logs and screen shots Big Newy asked for. The short mission recording is too big so here is a link to it on my YouTube channel. The key here for Oculus and Pico users (the two most affordable headsets) and there are more of us than you think. 15 million Quest 2 and 590,000 Pico 4 sold, is that these headsets perform horribly with DCS in Steam/OpenXR. But ONLY with DCS, I run MSFS 2022, VTOL VR, Assetto Corsa Competizione, Project Cars 2, F1 2020 and the list goes on at high or ultra settings in Steam VR with no issues. Don't get me wrong, I think DCS is the best combat flight simulator in public access at this time. On triple screens with Opentrack, I have no performance issues with most settings maxed out. However, the depth perception and immersion in VR gives me a huge advantage low level in the A-10 and helicopters, simply because I know exactly how far my wing tips/rotors are from the trees I am flying between. I have gotten several kills on MIG 29s by making them come down to my playground to get a shot at me. My better half remarked the other day that I spend more hours trying to get DCS to work reliably in VR than I do flying. But in spite of all of that, I really am pulling for the DCS Team because there is nothing out there with combat aircraft that is as real as DCS. Please for us Oculus runtime folks, don't force us to go to Steam VR/ OpenXR. The attached game video is actually the best it has done yet, until the enemy and friendlies activate, then FPS tanks, down around 12 FPS. Enemy strength is only 4 BTRs and 40 infantry with AKs. Blue force is 3 APCs, one M60 tank and 40 infantry. The only aircraft are us four UH-1s. EDIT Forgot to include the computer specs. System Specs, MOBO=ASRock X570 Pro4 CPU=AMD Ryzen 7 5700X, 8 core GPU=Zotac RTX 3060 Ti 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.In game network latency never above 3 MS. Newest versions of Pico 4 software, Virtual Desktop, NVIDIA driver (GeForce Experience not installed). Fresh Windows 10 install with all updates. VR benchmark = 97. MSI Afterburner undervolted at 0.975/1995 MHz on a curve, power @110%, Fan Control Program (CPU and GPU temps never above 65, because of the Corsair air flow case with 4 chassis fans and a massive Assasin CPU air cooler). Edit I have run repair and clean and have deleted the contents of the FXO and Metashaders folders. Still the same. Launch procedure Start Pico 4 headset. Start Virtual Desktop App in Pico 4 (Virtual Desktop streamer already running on PC). Right click on Virtual Desktop tray icon. Click on launch game, file explorer window opens, navigate to F:\DCS World OpenBeta\bin\DCS.exe Double click on .exe DCS launches without starting Steam or Steam VR, in Oculus runtime (runtime shown in VD performance display in headset), Log shows this 2023-03-10 22:39:38.250 INFO APP (8372): Command line: "F:\DCS World OpenBeta\bin\DCS.exe" 2023-03-10 22:39:38.250 INFO APP (8372): DCS/2.8.3.37556 (x86_64; Windows NT 10.0.19045) 2023-03-10 22:40:02.109 INFO VISUALIZER (8372): VRG skip, ask for support if you own VRG helmet 2023-03-10 22:40:02.367 INFO VISUALIZER (8372): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S Same process with MT Log shows this and DCS starts Steam VR, runtime now shown as Openvr, main menu screen is below my vision level but keyboard down arrow re-centers view. Loading screen super jittery, takes a long time to load, progress bars do not show, just Steam VR "Waiting on DCS". Performance drop, average FPS 25-35 with Spacewarp (reprojection) disabled, unplayable with it on, ghosting everywhere. Stuttering, random short freezes (1-2 seconds). 2023-03-11 00:22:39.856 INFO APP (12060): Command line: "F:\DCS World OpenBeta\bin-mt\DCS.exe" 2023-03-11 00:22:39.856 INFO APP (12060): DCS/2.8.3.37556 (x86_64; MT; Windows NT 10.0.19045) 2023-03-11 00:23:04.436 INFO VISUALIZER (12060): LAUNCH IN VR OpenXR: SteamVR/OpenXR : oculus Launched directly from modified shortcut on desktop with this command line and OpenXR Toolkit running, F:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR, runtime shows as OpenXR Still launches Steam VR, same symptoms as with F:\DCS World OpenBeta\bin-mt\DCS.exe, slightly better performance, I think because of OpenXR Toolkit. Log shows this 2023-03-10 20:46:20.932 INFO APP (Main): Command line: "F:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR 2023-03-10 20:46:20.932 INFO APP (Main): DCS/2.8.3.37556 (x86_64; MT; Windows NT 10.0.19045) 2023-03-10 20:46:52.517 INFO VISUALIZER (Main): LAUNCH IN VR OpenXR: SteamVR/OpenXR : oculus dcs.log_3_12_2023_1811.txt DxDiag.txt

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