Not to derail this Reverb thread, but have you tried turning all shadows off, and use that as a base to start optimizing? Shadows are a real FPS killer I find.
I run the Rift S with low shadows, flat terrain shadows and PD 1.4, on my i7 8800k, with a plain GTX1080, and it only very rarely dips below 40 FPS (ASW)
2 Likes
On low settings it definitely works. The 2070S is roughly on par with the 2080, I can confirm your observations.
I use similar settings (will check when I am at home tomorrow and post in the other thread) and it does run fine with PD 1.4
As for the Reverb: It has roughly 2.5 times the pixels of the Rift S. So thatās quite a lot more stuff to render.
I donāt know how well the thing that WMR uses instead of Oculusā ASW works, but judging by the fact that I cannot reach 80 frames per second in the Rift S even if I set DCSW to potato quality it better be good, because I will never reach 80 frames per second.
1 Like
ASW is on for me even with a 2080Ti, an i7 9800X and 32Gb of RAM. Of course I have my settings cranked up quite a bit.
Ah, so with high settings not even the mighty 2080Ti can do that? Interesting.
Do you see any differenceā¦?
I donāt, so my PD is at 1.0 in DCS.
I can definitely see a difference between 1.0 and 1.4
Below 1.4ā¦ not much. And 1.6 looks really good but it stutters too much for me.
Key things to look at for improved clarity are panel labels in the A-10 or Hornet for example.
1 Like
Ok. With the Rift CV1, increasing the PD did a lot for the picture clarity. But with the S @ 1.0 I have a better picture than the CV1 @ 1.5, so I guess Iām happy with that. And, I canāt say I see much improvment when I increase the PD. I guess there must be, if you look for it.
1 Like
Keep in mind that PD is essentially super sampling which takes quite a bit of processing power. With the Reverb offering more pixels you donāt need as much PD to get the clear image so the PC power to run it isnāt necessarily as high.
1 Like
Sure.
Unfortunately I am too bad at math to do this correctly, but isnāt the Reverbās resolution around 1.5-1.6 times the one of the Rift S? So I would guess that rendering a picture for the Reverb would be comparable to running a Rift S with PD set to 1.6
Thatās where my doubts came from, because when I set the PD to 1.6 I can basically turn everything else to low and it will still stutter a bit. And thatās with a faster graphics card.
I really want the Reverb to be an option. But has anyone even dared to test it with a graphics card other than the 2080Ti (which is almost as expensive as my whole PC)?
1 Like
I mostly fly Russian aircraft with Russian panel labelsā¦and I donāt speak Russian soā¦
3 Likes
For you Reverb owners with fast display adapters, any negatives in enabling motion reprojection and the mode indicator? Maybe the big question is given all of the available settings, what seems to be the best? This is what Iām running. Open to suggestions/criticisms.
DCS
VR preset
MSAA 2x
PD: 1.0
WMR for SteamVR config
motion reprojection: auto
mr indicator: enabled
SteamVR settings:
I have a Reverb and my graphics card is an Rtx2070 on my 9700k@5ghz. I get fine performance in dcs and il-2 ( frames at 70-90) but I generally run with motion reprojection
1 Like
Yes, of you use WMR for Steam VR Beta (versus non-Beta) you shoud have everything at 100% to get the native resolution.
1 Like
This is why, after trying very hard to like my O+ headset last year, I ended up going back to Oculus. The headset might not have the highest resolution out there, but it simply works, and works well. I donāt think the headsets are the problem, itās the platform.
Welcome to Mudspike @Wardaddy59!
1 Like
So question hereā¦ I have BOTH SteamVR and WMR for SteamVR beta runningā¦ is this right? Are they conflicting with each other?
I just have the Mixed Reality Portal and SteamVR running.
You say you are running win 10 build 1903 but you donāt tell us that you have ALL of the latest KB fixes some of which had to do with Reverb clarity. Your mention of needing 188% SS has us baffled since 100% is plenty to get 2160x2160 . Just which version of Steamvr do you have ? Should be like 1.8.19. Also there have been several WMR portal updates. Also maybe your graphic card settings could be wrong. You should run application controlled . Also your mention of VR.ini is confusing when the correct filename is default.vrsettings for reprojection. Are you running at 90 hz? Hopefully not at 60hz. What about needing glasses for long distance vision. Unfortunately all these issues must be addressed. Reverb should be almost monitor like
Hey thereā¦thanks so much for the reply. Okā¦ so as far as Windows 10 buildā¦ I updated to latest Windows 10 a couple days agoā¦ 1903. Not sure of all KB fixes as you mention. I assumed those would all be updated when I did latest windows update. As far as 188%ā¦ this has to do with WMR for Steam VR app I believeā¦ however, as Thudās notes stated, when go to the Beta version, You should keep it at 100% for 2160x2160 for native resolution. As far as WMR portal updatesā¦ not sure about those. My system simply installed WMR when I plugged in headset, installing drivers and such. Figured all was updated to latest at that point. I meant default.vrsettings for reporjection earlier, not VR.iniā¦ I did go in that file and removed // as noted. Yes, Iām running at 90hz in WMR. Maybe Iām not up to date with KB fixes as you mentioned. What are the latest? Also WMR Portal updatesā¦ how do I check those? Thanks again for your assistance! I really donāt want to have to return this headset.
Okā¦ but in Thudās file you linked, he said to install WMR Portal, WMR for SteamVR (beta), AND Steam VR releaseā¦ but you say you only have WMR Portal and SteamVR?
Alsoā¦ you mentioned graphics card settingsā¦ I just installed a new EVGA 2080 Tiā¦ havenāt really touched the settings, other than to update latest Nvidea driver. Do I need to go into windows display settings to check on display connector settings? Manā¦ I feel like such a noob at thisā¦but Iām not! Iāve been using VR headsets (Oculus) for quite some timeā¦ WMR is a new world and quite confusing!