Pnguin9999

You my friend are a super genius. I have been doing this for several years and never thought of renaming the folder. I don't know what was in the old config but I loaded just the input config for the A-10a back in one category at a time in the controls page and took it for a spin from Batumi. I'm floored, solid 72 fps with Virtual Desktop spacewarp on and Ultra graphics. In game textures to high, shadows flat, clouds standard, distance high, everything else low or off. I would go to the stable version but a lot of multiplayer servers require the latest Open Beta. Thank you.

The following may sound like a rant but there are valid points here. After weeks of searching for solutions to VR performance issues after each update and days implementing them. The sun was shining and birds were singing, DCS MT was running smooth at 35-45 fps in VR, with the Oculus runtime, launched direct from Virtual Desktop. Then I installed the latest Open Beta, 2.8.4.39731. Now from Virtual Desktop in Oculus runtime, I am sitting in the hanger with a distorted 3D image of the hanger aircraft, no menu and the background music is playing. So I start DCS with the force enable VR same issue with Steam VR runtime alone, add open xr same issue. Then I try the .exe straight from the bin folders, both MT and non MT, they only load 2D. Why do we have to go through this every single update? Does no one at ED test the updates with the most popular (by sales numbers) VR headset in the world, the Quest 2, before releasing them? And before we go through the whole did you do this and that bull that we do every time. Yes I deleted the contents of FXO and Metashaders2 folders, yes, I ran slow repair, no mods are installed, drivers are up to date, Steam is up to date and files have been verified, yada, yada yada. I love DCS and have a ton of money invested in aircraft and maps and was really enjoying Normandy 2.0, but am sick and tired of spending more time researching and fixing issues than flying. Come on ED, VR is the future of flight simulators, just ask the Military, who are retiring the full motion simulators and moving to the NOR engine VR sims. I was ready to buy the new F-15 module and the C-101 but I put my wallet back in my pocket. I'll be over at VTOL VR flying cartoon planes that work until your customers once again figure out a work around. Edit Reverted back to the previous version that was working now it has the same issues.

Works well for me, but I am realistic with the settings based on my middle of the road PC (specs in signature). Textures high, distance high, MSAA 4, all shadows off, everything else low. This gets me smooth 35 to 45 fps in a UH-1 low level London and Paris and 45-50 fps in a jeep driving around in both cities (fantastic ground level details in this map), reprojection off.

Works great, thanks.

You could install to the main directory DCSOpenbeta>Mods folder but this mod over writes some of the original files and if you add the snowless winter that changes some of the mod files, toss in Taz's better trees mod (highly recommended) and that changes more stuff. Easiest way to install this or any mod is to get OVGME. Link and explanation here, thanks Hoggit. https://wiki.hoggitworld.com/view/OVGME , great what, how, why video here Thanks 122nd Composr. If you join a multiplayer server and some of your mods don't pass the integrity check, you can just disable them in OVGME with two clicks and then enable them when you want with two clicks.

Barthek you are a super genius! Caucasus has always been my favorite map, now it looks better than any of the others with no FPS drop. Throw in Taz's better trees and just WOW. Thanks for all the hard work I know went into this. Edit. In VR the terrain is much sharper.

Update. I have tried a few new things and they worked. Now getting 35-45 smooth FPS in Caucasus even when dropping a pair of CBU-97s. I removed MSI Afterburner and Riva Statistics, turns out the Zotac 3060 TI OC card standard advertised boost clock of 1695 MHz will actually go to 1920 if well cooled (65-75C) using a program called fan control to run the GPU fans on a custom curve. 75 % RPM at 70C, I'd rather buy fans than cook my card. The Zotac will boost until it hits the voltage limits in the VBIOS. Second, I use Process Lasso and set CPU priority always for DCS, Virtual Desktop and Steam to high. Probalance and high performance on. Restricted DCS to physical cores only. Panjno on Youtube has great videos on how to set this up. Finally two things I got from posts in this thread. Turned off audio streaming in Virtual Desktop and used separate headphones from the PC and changed the registry " Set HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1\ActiveRuntime to None" thanks Hillman! So starting DCS from the VD tray icon using bin_mt.exe starts in Oculus runtime now, no Steam VR.

I only have 16 total cores so I don't have to disable SMT but I just tried two other things mentioned in this thread and they worked, I just played through a demanding mission 4 times with only one lockup. It happened when I double tapped the Pico passthrough to see where my drink was, LOL. All credit to the two people who posted these. 1. I shut of the audio streaming in VD and used separate headphones for audio from the PC. 2. I changed the registry entry to None, now MT starts in Oculus runtime if started from the VD tray icon, bin_MT. I'm now getting smooth 35-45 FPS. No problems even when I dropped a pair of CBU-97s. VD reprojection is turned off, it causes too much ghosting for me. Finally I can play until the next update when we will have to figure out work arounds for the new "improvements". All in all though, I think ED is moving in the right direction and have high hopes for the Vulkan engine. Although I wish they would check out the Unreal 4 engine, Assetto Corsa runs great in VR even loaded down with Reshade and Pure weather and its as old as DCS.

I am having good luck with restricting DCS to physical cores only (all even numbered cores except zero). I have also set CPU priority always to high for DCS, Virtual Desktop and Steam. Probalance and high performance modes on. I have an AMD Ryzen 7 5700x, 8 physical cores. Strange thing though, running OpenVR benchmark I get 14% CPU usage but running DCS it goes to 34%. Still lots of headroom. But I have frequent crashes of DCS or Virtual Desktop even starting non MT from the VD streamer/ Oculus runtime. I am trying the registry change in a few minutes. Hopefully that will work.

Also make sure to enable USB debugging in Pico settings. Go to setings>general>about>click on software version 7 times and developer mode is enabled>developer tab>set USB debugging on.

You can also try Process Lasso to control CPU usage. I have DCS, Steam VR and Virtual Desktop CPU priority set to high priority always and DCS restricted to physical (even numbered cores) only. https://bitsum.com/

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

Me too, Virtual Desktop crashes but the game continues on the monitor. Report with full specs, logs, example video link etc. posted to MT VR bug topic. I even have Process Lasso running Virtual Desktop CPU real time priority, DCS and Steam running high priority, ultra power plan and tried restricting DCS to physical cores only. Non MT same issue since version 2.7. , same issue with Pico and Quest 2. I thought it was the Oculus runtime on both, fighting OpenXR but I see a lot of reports of people running the same setup with much improvement. MT runs great when I switch to a triple screen display with plenty of head room on my 3060Ti. In VR the GPU is at 95%, undervolted on a curve at 0.975V and 30 GHz below the VR benchmark max.

Thanks, glad to know it's not just me.

Hello, I can't change the blank avatar profile picture. I did a search of the forum and tried the solution found. Go to profile, click on avatar and nothing happens. Is it a time thing? I have only been a member of the forum for two days.

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