DCS VR Mod Comparisons with IC Version

There’s a few versions of the VR Mod and what I was interested in was ‘How much performance would I lose using this with Integrity Check (IC) working?’.

My setup is a i9 @ 5GHz, a 2080 overclocked, 32GB and DCS with quite light settings (no MSAA etc). I am also using the PD 0.5 / 500% SteamVR SS.

I’m using the F/A-18C Free Flight from the Caucasus Map, just letting it fly straight. I’ll use milliseconds on rendering a frame, as I’m just more interested in comparing them rather than getting pure FPS numbers (they’ll differ between us all anyway).

VR Mods are from this post:

Results:

  1. The standard mod + Taz1004 texture fixes.

Average VR update rate when looking around for 5 minutes is 11.3ms. GPU usage about 50%.

  1. No VR mod at all, so clean install.

Same sort of looking around 15.2ms, with peeks into 16ms when looking down into the cockpit. GPU usage about 80%.

  1. The Integrity Check Pass version of this MOD.

Average of 13.1ms over 5 min run. GPU seemed into 70% plus.

So the answer is the IC version is still better but it’s about midway between the non-IC version.

I tend to use reprojection in DCS because I’m not under 11ms anyway (which would be a native 90 FPS) so in some ways it’s really just creating headroom for when DCS gets busier, i.e. anything AI in view or things going boom (not many of them with me driving).

To break reprojection would be renders taking about 18-20ms (it needs some headroom), and DCS is pretty uneven when it takes a hit, as in something like the carrier will go LOD loco up close and drop down to 30ms (stopping reprojection with a judder) until it all loads in. The pauses and crawls seem to be just the CPU backing up and I’m not sure any mod would help.

Seeing the results I guess it depends on how close you are to the magic values needed for either pure 90 FPS (11ms) or reprojection (< 22ms). I might trying my settings up a bit, and if I sometimes forget to put the mod on then it’s not really a disaster.

7 Likes