nVidia driver hotfix for SteamVR released

[MA_Goblin]

So is this a correct understanding of SteamVR settings?

 

If I have Steam VR setting "resolution" to automatic with my Reverb G1 it translates to 118%.

So if I adjust the "per application" settings i add or subtract from the 118%?

 

Meaning if I set per application to 100% the automatic value of 118% is my rendering.

 

 

Edited March 17, 2021 by hakjar

[speed-of-heat]

40 minutes ago, hakjar said:

So is this a correct understanding of SteamVR settings?

 

If I have Steam VR setting "resolution" to automatic with my Reverb G1 it translates to 118%.

So if I adjust the "per application" settings i add or subtract from the 118%?

 

Meaning if I set per application to 100% the automatic value of 118% is my rendering.

 

 

 

in the context of steam VR, the number in the application at 100% is the same value as your number in "General" ... and this why percentages are always confusing ... I leave (or set) my headset general settings at 100% and then vary my individual application... to simplify the conversation .. but your understanding is correct   

[ShaunX]

Ok, well that was a damp squib.

 

I tested a number of hi AI activity scenarios with my original settings, and then with PD .5, SS 400%.

 

Absolutely no difference in clarity (The G2 with my rig is super clear anyway)

 

Zero performance improvement. If anything, slightly lower average FPS and CPU hitting red more often on the supercarrier

 

I'll be sticking to PD 1.0, SS 100%

[imacken]

To be honest, that is my advice, fwiw, for everyone. Stick to 1.0 and 100%. Life is too short!

[dburne]

5 hours ago, imacken said:

To be honest, that is my advice, fwiw, for everyone. Stick to 1.0 and 100%. Life is too short!

 

I tried .5 PD in DCS, and 400% SS in Steam VR.

Immediately on getting into the Hornet on the Stennis carrier it did not look as sharp to me.

So I went back to PD of 1 and 100% resolution in Steam VR for my G2.

[speed-of-heat]

yep same 

 

[Taz1004]

13 hours ago, ShaunX said:

I'm going to try the PD 0.5 trick this morning, though I'm pretty skeptical

 

I currently have DCS PD at 1.0. In steam VR, I run Global SS at 100%, DCS specific SS at 100% which SteamVR calculates for my rig to be 3164 x 3096 (catering for barrel distortion)

 

So, if PD is a linear dimension and as a multiplier I should use it as 0.5 * 0.5 * SteamVR SS, then increasing SteamVR DCS SS to 400% should give a similar resulting resolution ? (Am I right up to now ?)

 

If I increase SteamVR DCS SS to 400% it calculates that to be 6332 * 6196 for my rig, which is pretty much exactly double to the 100% figures above ( err, shouldn't it be 4 times ? I'm confused now.)

 

Anyway, with my original settings, if I  jump in the Hornet on a hot start on a very busy supercarrier deck (which always stresses my rig so that I'm barely maintaining 45 FPS) , monitor the FPSVR figures, then quit the mission and save the track. Then replay the the track with the new settings and monitor FPSVR again, does that sound like a reasonable comparison ?

 

If you want to test, keep the numbers simple.  Forget SteamVR % number.  Pretend it doesn't exist.  Just set the slider so the Per App resolution is close to your headset's native resolution.  1440x1600 in my case.  100% most likely is NOT your native resolution.  Now set DCS PD to 2.  This will make final render resolution close to 2880x3200.  Test it.

 

Then bring DCS PD back down to 1.  Set SteamVR resolution close to 2880x3200.  Test it.

 

If you want to test PD 0.5, then set SteamVR resolution to 5760x6400.  Set DCS PD to 0.5.  Test it.

 

It is all same on my end.  Again, numbers I used in this example is based on my headset.  Apply your own headset's native resolution.

Edited March 17, 2021 by Taz1004