MPK

Thank you so much for the time you have put in to make this more realistic! We really appreciate it :)

VR must render additional pixels to compensate for the barrel distortion near the edges caused by using fresnel lenses, so 100% in steam VR is always higher than the number of pixels on the headset LCD. Virtual pixels get squished at the edge of the screen and stretched near the centre. 100% in steam VR is approximately what is required to have 1:1 pixel mapping near the centre of the view. I had a link to an old video from a Valve presentation at the game developers conference several years ago that had a good explanation for this but I am struggling to find it at the moment. If you go less than 100% in steam VR (e.g. try to match the Steam VR resolution to the headset LCD resolution) then the middle of your view will be under sampled (is that the term for the opposite of "super sampled"?)

Thank you for this thread. The CPU graph in the multiplayer section says it all (around 12:15 in the vid). No amount of GPU upgrades will ever make DCS run well in VR:

Even worse though is the INSANELY loud obnoxious static sound with the jester menu. Can we please get a way to disable this sound?

Awesome, that would be much appreciated!

It sounds like others have the same issue: https://forums.eagle.ru/showthread.php?t=274761

I thought the same thing when I first got into VR. After several experiments involving unplugging monitors and so on, I have concluded that it has no negative impact at all.

Better than before, but nowhere near 2.5.5 performance. The CPU spikes make multiplayer unplayable in VR for me. The Supercarrier is also a big frame rate hog

Especially in VR ... Any chance of having a way to disable this?

This is still happening in today's patch (2.5.6.49314). I just had it happen immediately after a phoenix launch on the PGAW server.

See title.

I was thinking the same thing. You would think that arriving at the same result using a better source image would give better visual results. I honestly didn't notice much difference in the headset though.

I just realised I miscalculated one of the tests, PD 0.5: 0.5 x 0.5 x 1.5 x 4.0 = 1.5 That explains why that test ran better and looked worse.

When you reduce image quality it runs smoother? This could be the breakthrough we've been looking for!!! :megalol::megalol::megalol::megalol:

This made absolutely no difference for me: This is the F-14 take off instant action mission. The numbers are taken while in the cockpit just before hitting "Fly". The headset was on the desk to make sure the camera position was identical each time. The numbers are from the Steam VR advanced timing graph. Frame time rounded to the nearest ms. Steam VR only lets you set SS to an even number, so there are slight variations in the total SS level for each test. The first one (DCS PD of 0.5) looked promising because the GPU frame time was so much lower, but in the headset it was obvious from the poor image quality that SS 400% was not actually being applied. The other 4 options all looked about identical in the headset. The slight difference in GPU times match the slight difference in total supersampling.

I have always told numb nuts to select the current steerpoint first, then steerpoint from map second. I haven't had an issue so far, and I can watch the HSI and see the direction/distance change as the coords are entered. The only issue that I have ever seen is that doing it during the alignment has caused alignment issues on occasion. I haven't nailed down the exact circumstances that lead to a bad alignment.

It gets rebuilt in the saved games folder (either fxo or metacache, I don't recall which).

I am still on windows 10 version 1903 and I had massive FPS drops with 2.5.6. The issue is 2.5.6.

Thank you! Worked online first try for me last night

Part of the problem is definitely 2.5.6. which has much, MUCH worse performance for me. I am back to 2.5.5. for now. Try starting with every possible setting on the minimum and if the performance is acceptable start slowly increasing things. My settings for VR are pretty close to the minimums and I barely maintain 40fps most of the time. On a monitor I can run everything maxed and get 70 fps in the tomcat.

Yes, I reinstalled 2.5.5 ;)

Hi, is this version 2.5.6.43827 released today? Or with the initial version 2.5.6.43435 released last week? I had a massive reduction in frame rate with the initial 2.5.6, but I haven't tried today's patch.

I think this is a 2.5.6. bug. I had this issue even without the shaders mod.

I did this before each test. I think it is actually a requirement when enabling/disabling the shaders mod.

Thank you! i9900K, RTX2080 Super, 64 Gb DDR4 3200 Ram. CPU and GPU both have a mild overclock.