101st Lonestar AUT

*** V1.1 modified  on 01.02.2023 ***
Ok, will just summarize for you  - as a kind of X-MAS present 😉 - this is for my WIN10 setup at least:
(It took me about 6 weeks to get DCS running smooth and stable, so I do know the pain...)
First of all:
DCS-Settings have the biggest impact to your performance, so start on low settings and after all get higher step by step.
(Texture Settings cannot be set to high, if you dont have a graphics card with 12GB or more!!)
Before starting DCS restart your PC and be sure no other applications than needed are running in the background!
(also check your autostart and disable any unnecessary apps in Windows-Taskmanager, than restart again and doublecheck).
Be sure to use a VR-Ready USB-Port for your Link-cable, or at least the fastest one you can find on your PC. I am using an external powered USB3.1-Hub to really get safe in terms of voltage supply... 
Delete the two shader folders of DCS itself before first time starting in DCS-VR (wherever your game files are located e.g. C:\Games\Eagle Dynamics\DCS World OpenBeta\Config" --> "fxo" and "metashaders2" folders)!
My Rig:
- AMD Ryzen 3700X
- Nvidia 3060ti
- 64GB Ram
- WIN10Pro
Installed software:
- MSI Gaming App (in my case: for VR-Ready USB support)
- latest Nvidia Drivers
- latest Oculus-HMD Update installed (WLAN needed)
- latest WIN10-Updates
- Oculus Tray Tool (or Debug Tool)
- ProcessLasso (for managing your processes permanently)

Configuration:
1. DCS ingame graphics settings (see screenshot below)
2. edit graphics.lua (can be found in C:\Users\username\Saved Games\DCS.openbeta\Config\) - search for following lines:
   maxfps = 40;
Precaching =   {   around_camera = 42500;   around_objects = 7500;
} (40 maxfps comes from Oculus Home App --> e.g. 80Hz == 40fps for each eye, around_camera is my TGP max render distance and should be same as ingame. Due to 2.8 you can either write an autoexec.bat or change these settings manually after each update, tutorials can be found in DCS forums)

3. Nvidia settings --> I am using Anisotropic Filtering by Nvidia and turned it off ingame, skip FXAA and Antialiasing for the beginning (see screenshots below)
4. Oculus settings --> start with 1.0 resolution, you can get up to max resolution at 80Hz and even higher with small impacts to your performance (see                   screenshot)
5. Oculus Tray Tool OTT settings (see screenshot)
6. ProcessLasso settings (DCS needs 2-3 permanent cores, OVRServer needs at least 2 - try to get DCS and any other 3rd party app on different cores with this      tool permanently or via taskmanager each time you start DCS) + set priority HIGH for DCS.exe and OVRServer_x64.exe or to real time
7. Windows Energy settings --> use optimum performance profile & check if USB-powersafe is deactivated (see screenshot)
8. Windows Graphics settings --> deactivate hardware based GPU scheduling
9. Windows System Properties, Performance --> use processor time scheduling FOR background apps (this is priority for OVR Server Link-App) 
10. HINT: if you own a NVIDIA card you can AUTOTUNE your card via the Alt+Z (enable in game overlay first) menu and use this profile in afterburner to get some        extra power

Startup routine:
0. Be sure ProcessLasso is running in the background
1. Check if your USB is ready for using VR (in my case: in MSI Gaming APP it has to be activated)
2. Start Oculus Home
3. Start Oculus Tray Tool (minimize and do not close it)
4. Start your Quest2 (and define your Guaridian area - for me: desktop, fixed)
4.1 At the very first start: test USB-voltage & bandwith within the Oculus Home App (should be around 2.8 GBit/s on USB 3)
5. In the Q2 go to your Link-App (usually in the quick settings bar left) and connect with your PC
6. As soon as the Link is established and the App is running start DCS directly from your PC Desktop (first time seems to be important)

For more Details I will post the Screenshots in saperate as following:

^^ Clouds can be left on "standard" after the new updates to AA.


^^ take ALL the values out of the () for your config and finally use "pre-rendered VR Frames Value: 1-2"
 



^^you can try lower Encode Bitrate and Resolution here as well - depends on your cable and USB-Device
 
Screenshot out of Windows Energy-Management (edit your Power-Plan):

 

 
 

 
Hope this helps a lot of you guys and safes your X-mas holidays!
BR LSR