Upgraded to Rift S = absolute train wreck

[killerquagmire]

So I was using the Rift CV1 no problems. I had nearly all the graphics set to high or medium with MSAA set to 2 and SSAA set to 1.5 and was getting very serviceable frame rates. So I decided to upgrade to the Rift s for a little better resolution.

BIG MISTAKE.

Micro stutter was immediately apparent, even if I lowered the settings.

At the time my rig=

AsRock Z68 Mobo

intel 3770k

Nvidia 980 ti

32 gb 3200 mhz ddr3 memory

So my initial thoughts were my cpu and graphics card are dated and simply can't handle the higher resolution of the Oculus S. So I upgraded to:

Asus Z490 Tuf mobo

intel 10600k

RTX 2080 super

32 gb 3200 mhz ddr4 memory

The upgrade had ZERO affect on performance. In fact, it had the opposite affect. The micro-stuttering is so bad the game is pretty much unplayable. I tried following then usual VR tips and even Thuds VR4DCS guide and found no joy. I'm hoping that someone out there with a similar setup might be able to share a good configuration with me that may help. Honestly, any help would be greatly appreciated. I'm at my wit's end.

[Svsmokey]

The greater resolution of the RiftS demands are largely offset by the 80hz refresh rate as opposed to the 90 hz of the CV1 . I could see the 6gb vram of the 980ti as possibly being problematic however .

 

While being far from satisfied with current DCS VR performance , I would not describe it as being unplayable , at least in SP . This leads me to think that you may have a configuration issue in your new system with Windows or your bios .

 

Windows game mode "off" ?

Windows power setting "max performance" ?

Windows USB settings ok ?

 

BIOS ram setting to "XMP" ?

 

Oh , and Nvidea power setting to "max performance" ? And Oculus setting to "performance" vs "quality" ?

Edited July 28, 2020 by Svsmokey

[VitS]

So I was using the Rift CV1 no problems. I had nearly all the graphics set to high or medium with MSAA set to 2 and SSAA set to 1.5 and was getting very serviceable frame rates. So I decided to upgrade to the Rift s for a little better resolution.

BIG MISTAKE.

Micro stutter was immediately apparent, even if I lowered the settings.

At the time my rig=

AsRock Z68 Mobo

intel 3770k

Nvidia 980 ti

32 gb 3200 mhz ddr3 memory

So my initial thoughts were my cpu and graphics card are dated and simply can't handle the higher resolution of the Oculus S. So I upgraded to:

Asus Z490 Tuf mobo

intel 10600k

RTX 2080 super

32 gb 3200 mhz ddr4 memory

The upgrade had ZERO affect on performance. In fact, it had the opposite affect. The micro-stuttering is so bad the game is pretty much unplayable. I tried following then usual VR tips and even Thuds VR4DCS guide and found no joy. I'm hoping that someone out there with a similar setup might be able to share a good configuration with me that may help. Honestly, any help would be greatly appreciated. I'm at my wit's end.

 

Do you still have SSAA on?

[flameoutme]

I'm sure you have done this, but temporarily drop all preferences in DCS to the low settings, and see how much that helps. If it helps a lot, bring them back in slowly to see if there are any in particular that are impacting the experience. I used to run a Rift S and it was smooth as long as I kept the settings on the lower side. My CPU was the i-9700k, but my graphics card is weaker than yours.

[eaglecash867]

What do you have your DCS PD set to? With the CV1, you were probably running that pretty high. If you run a higher resolution HMD like the Rift S at the same high PD setting, that could be your problem.

[VirusAM]

Upgraded to Rift S = absolute train wreck

 

SSAA has not to be used in VR.

Then surely the 980ti is not enough with the Rift S at high settings, but the 2080 super should be plenty.

Drop your pd to 1.0 in dcs and experiment with oculus tray tool settings.

I have most settings on the high side, pd set to 1.2 in oculus tray tool for dcs.exe and with the Rift S I have no issues.

[killerquagmire]

What do you have your DCS PD set to? With the CV1, you were probably running that pretty high. If you run a higher resolution HMD like the Rift S at the same high PD setting, that could be your problem.

 

This seems to be the culprit. I was running the PD at 1.5 (set inside DCS options) with CV1 and my 980ti. For whatever reason the Rift s and RTX Super can't handle it or perhaps there was a change in the way DCS handles it.

Anyway, i turned it down to 1.0 and then set the SS to 1.8 in the Oculus Tray Tool and that seems to have smoothed it out quite a bit.

Again, not sure why I was able to run higher graphical settings with CV1, 980 ti and an ancient cpu. Perhaps the game was just better optimized for that hardware. Then again, DCS seems to be a bit of a roller coaster when it comes to optimization every time they roll out a new update. But at least it's playable. Still, If anyone out there has a similar rig, I would like to see a screenshot of your graphic settings. I'm trying to squeeze the most quality out of this thing while still maintaining serviceable frame rates.

Thanks again for the help guys. Great community here.

[eaglecash867]

This seems to be the culprit. I was running the PD at 1.5 (set inside DCS options) with CV1 and my 980ti. For whatever reason the Rift s and RTX Super can't handle it or perhaps there was a change in the way DCS handles it.

Anyway, i turned it down to 1.0 and then set the SS to 1.8 in the Oculus Tray Tool and that seems to have smoothed it out quite a bit.

Again, not sure why I was able to run higher graphical settings with CV1, 980 ti and an ancient cpu. Perhaps the game was just better optimized for that hardware. Then again, DCS seems to be a bit of a roller coaster when it comes to optimization every time they roll out a new update. But at least it's playable. Still, If anyone out there has a similar rig, I would like to see a screenshot of your graphic settings. I'm trying to squeeze the most quality out of this thing while still maintaining serviceable frame rates.

Thanks again for the help guys. Great community here.

 

You were able to run the CV1 at higher settings because its significantly lower resolution than your Rift S. Your PD and SS act as multipliers to the native resolution of the HMD, so a higher resolution headset will tax the system a lot more. That's when you realize that you can back off on those multipliers and see better results in both visual quality and performance. I used to run my CV1 at 2.0 DCS PD, so when I got my Reverb and left that set at 2.0, it looked fantastic but was a slideshow. Backed it off to 1.0 PD and that solved all of my issues. :D

[Eldur]

Generally, the quote-unquote visual gain of AA, SS and PD > 1.0 simply isn't worth the MASSIVE performance drop anyway. The difference is hardly visible at all, yet it could force even a Cray to it's knees. On top of it in sims like DCS, all those methods incude some kind of blur that makes it a lot harder to spot things. It's literally like buying an i7 / i9 (G9+) for almost thrice the price tag of an i5 / i7 (G9+), just for being able to disabling the HT within the BIOS which is recommended literally everywhere. I never got why people kept doing that... if all those would have given the excess money to me instead, I'd literally have all my problems in life solved at once

[freehand]

Generally, the quote-unquote visual gain of AA, SS and PD > 1.0 simply isn't worth the MASSIVE performance drop anyway. The difference is hardly visible at all, yet it could force even a Cray to it's knees. On top of it in sims like DCS, all those methods incude some kind of blur that makes it a lot harder to spot things. It's literally like buying an i7 / i9 (G9+) for almost thrice the price tag of an i5 / i7 (G9+), just for being able to disabling the HT within the BIOS which is recommended literally everywhere. I never got why people kept doing that... if all those would have given the excess money to me instead, I'd literally have all my problems in life solved at once

 

Increasing PD in VR is a huge difference just from 1 to 1.4

[VirusAM]

Increasing PD in VR is a huge difference just from 1 to 1.4

 

 

 

I don’t see all this difference...i tried to go up to 1.7 but was too much. At 1.5 worked fine but some dips.

In the end I choose to set it at 1.2 and it seems good to me.

Even 1.0 is not so bad in the rift S

[freehand]

I don’t see all this difference...i tried to go up to 1.7 but was too much. At 1.5 worked fine but some dips.

In the end I choose to set it at 1.2 and it seems good to me.

Even 1.0 is not so bad in the rift S

 

Are you running PD in game at 1.2 or tray tool.

Edited July 29, 2020 by freehand

[VirusAM]

Are you running PD in game at 1.2 or tray tool.

 

 

 

Using oculus tray tool.

In game settings should be the same anyway as it is computed the same way (per axis) while for example steamvr supersampling is calculated on the total resolution

[freehand]

I used to run at 1.4 with the rifts I would not use PD of 1 big difference for me.