SS and same default resolution comparable?

[ironk79]

does rendered SS resolution translate to native HMD resolution performance wise? What i mean, at the moment i play on my CV1 with OTT SS @ 1.2, giving me 16ish x 19ish SS resolution. I just try to get a feeling about possible performance of a future HMD with better native resolution.

[dburne]

I would think a native resolution would perform a little better than an equivalent SS resolution.

[ironk79]

Thanks dburne, thats what i suspect too, less rendering would indicate that. Maybe someone has 1:1 case from a similar upgrade.

[dburne]

There have been reports from some Reverb users over on the DCS forums where they were surprised that they were getting better performance with Reverb versus older tech headsets with higher SS numbers.

[ironk79]

Sounds promising!

[SCG_Fenris_Wolf]

Sorry, this may be a bit off-topic, but maybe interesting for ironk to get a good picture, if he plans to upgrade his Rift:

 

7 hours ago, dburne said:

There have been reports from some Reverb users over on the DCS forums where they were surprised that they were getting better performance with Reverb versus older tech headsets with higher SS numbers.

May be because SteamVR tanks their resolution if they exceed the cap. It shows as 3k * 3K, but the max it gives is 2048 * 2K. Even Windows Mixed Reality for SteamVR, the app that's supposed to solve this, fails every other month again because of SteamVR patches. 

 

People get Index resolutions with their Reverbs, or pixelated images on their Pimax, and spit pest and fire: A good example. 

 

They don't know that Valve sets the default limiter, and the fallback if you exceed the 4096 limit.

 

Look into the spoiler, here's a possible solution for Reverb guys (copy 'n paste from my sticky thread cf Pimax settings).

Spoiler

If you select wide FOV for the Pimax, you may have noticed a sharp loss in clarity. No matter what you do, the picture stays pixelated. SteamVR may recognize a Pimax correctly, but applies a horizontal limit to the maximum resolution of 4096. That's fine for the 2880 pixels of an Index, but a 5K+ in wide FOV needs 5120 - without any Supersampling applied yet. We can remove this limit, but depending on your installation, SteamVR release, Beta, version, etc; the config file we seek has been all over the place sometimes. Fortunately, Steam wants to know how to find its own files.

 

Step by step guide to bump this up to 8192:

 

1. Open Windows' Command Prompt / Powershell / Bash

2. Change directory to your Steam folder, and in there to \steamapps\common\SteamVR\bin\win32

3. Execute vrpathreg.exe

4. It will print the config path for you

5. Go to the Config Path and backup steamvr.vrsettings , then open it with Notepad++

6. Now scroll down, and inside "steamvr" : {      you change or add the line       "maxRecommendedResolution" : 8192,  

7. Do not put it higher than 8192, the compositor doesn't like it.

8. Save and exit. Make sure no entries are in there two times. Make sure you didn't accidentally delete or overwrote anything else. 

9. Enjoy full clarity in IL-2 with wide FOV!

 

Edited January 3, 2020 by SCG_Fenris_Wolf