Hey Guys,
I been doing some testing last week or so and came to some good conclusions.. My Specs are in the sig but that is really not all important for setting an optimal experience as everybodys rig specs and hardware will be different..
I have a Odyssey+ VR Headset and been flying DCS in VR for almost a year.. I also used a program called fpsVR but it is not needed for DCS but a good FPS and Frametime counter able to display in VR Headsets..
What I found out the Frametimes are very important in maintaining a smooth experience and basically you would want o keep the FrameTimes under 20ms for a WMR Headset.. WMR uses SteamVR and Steam Mixed Reality programs to work with DCS..
Now it would probally be best tested on a Multiplayer server or mission with alot of objects but not overkill. I just used Beachead Interdiction for the AJS 37.. I may end up tweaking a bit more but the few MP servers I went on the results where very good..
here is a readout from fpsVR to give you an idea:
fpsVR(<
https://store.steampowered.com/app/908520>) Report:
```App: DCS HMD: Samsung Windows Mixed Reality 800ZBA0 (90.002 Hz, IPD 65.9)
GPU: NVIDIA GeForce GTX 1080 (26.21.14.3648) CPU: Intel(R) Core(TM) i5-7600K CPU @ 4.80GHz
Delivered fps: 44.84 Duration: 7.5min.
GPU Frametimes:
Median: 15.4 ms
99th percentile: 19 ms
99.9th percentile: >30 ms
frametime <11.1ms(vsync): 2.5%
CPU frametime:
Median: 13 ms
99th percentile: 19.3 ms
99.9th percentile: 29.3 ms
frametime <11.1ms(vsync): 23%
Max. SteamVR SS: 150%
Render resolution per eye: 1772x2212(by SteamVR settings, Max.) (HMD driver recommended: 1447x1806)```
Now I guess you could end up with different settings in DCS according to your specs and SS settings.. so I am not going to post them up.. the thing to keep in mind is I have Motion Reprojection on Auto and use 150%SS in SteamVR.. you must keep your GPU FrameTimes under 20ms. the optimal Frametime is 11ms but nearly impossible in DCS could depend on the mission as well..
So basically I used Beachead interdiction AJS37 and set from there.. it had a few objects and 3 planes flying and low level.. I figured a good base mission to try it with.. I did keep the PD in DCS @1.0 as I used SteamVR SS 150%..
just remeber no matter the setting just keep your GPU FrameTimes under 20ms the closer to 11ms the better.. if you run fpsVR you will see the 99.9Percentile but that was a blip like when I enabled the EP-13 Maverick display and such.. when using fpsVR you get the readouts live so it is easier to make sure you maintaiin under 20ms that is the key.
I guess the best hope we have for VR in DCS is Vulkan.. I hope this helps you guys that use VR a bit..
OK I have done some more testing and added my Specs in the sig that where removed for some wierd reason?? Anyhow I OC my CPU to 5.00GHZ Up from 4.8 it was at before on the last test.. In DCS A high OC helps really well.
I also tried setting my MSCONFIG too a very bare minimum of Microsft services to run, I am still trying to figure if this helps any but initial testing says it did not.. Altho my CPU Utilization was lower and RAM usage was down a bit along with less processes running.. I will have to test this again with the new clock speed..
This run I plan on setting a log again for the Beachead Interdiction mission to see if there was a improvemnt or not.. Once I run that test I can compare with this run to see if any difference.. So barring that test I will report back in about hour..
here are the results:
fpsVR Report:
App: DCS HMD: Samsung Windows Mixed Reality 800ZBA0 (90.002 Hz, IPD 67.1)
GPU: NVIDIA GeForce GTX 1080 (26.21.14.3648) CPU: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz
Delivered fps: 45.13 Duration: 15min.
GPU Frametimes:
Median: 14 ms
99th percentile: 21.6 ms
99.9th percentile: >30 ms
frametime <11.1ms(vsync): 2.3%
CPU frametime:
Median: 11.8 ms
99th percentile: 19 ms
99.9th percentile: 26.2 ms
frametime <11.1ms(vsync): 40.4%
Max. SteamVR SS: 150%
Render resolution per eye: 1772x2212(by SteamVR settings, Max.) (HMD driver recommended: 1447x1806)