HP's Reverb VR Pro Headset

[Eaglewings]

250% supersampling is insane

It is insane indeed, that is why I am surprised. I can manage 38fps and sometines 40ish fps in the sky.

[speed-of-heat]

whilst a high super sampling level was required for the O+ to make it anywhere near readable, frankly the base resolution of the Reverb is more than enough to get a readable and clear cockpit... you will find that 100% is steam is fairly close to native resolution (per eye) of the reverb, and that for me is good enough...

 

YMMV

[Wicked.-]

Why the hell is it cross eyed for me?! Lol. Can anyone tell me why the Reverb is perfectly clear in both the WMR house and the SteamVR cliff house but is totally FUBAR once I load into DCS? I’ve gone through and removed any previous settings, files and hacks that could possibly effect it. It can’t be an IPD setting because it looks great outside of DCS. I still have 27 days to send it back but I’d like to get it working. I spent a good 10 hours editing the file created by openVR debug tool so that’s not going to help. It’s like DCS is off center.

Edited January 3, 2020 by Wicked.-

[oz555]

Why the hell is it cross eyed for me?! Lol. Can anyone tell me why the Reverb is perfectly clear in both the WMR house and the SteamVR cliff house but is totally FUBAR once I load into DCS? I’ve gone through and removed any previous settings, files and hacks that could possibly effect it. It can’t be an IPD setting because it looks great outside of DCS. I still have 27 days to send it back but I’d like to get it working. I spent a good 10 hours editing the file created by openVR debug tool so that’s not going to help. It’s like DCS is off center.

 

 

Did you run the debug tool vertically?

 

 

If like me you had no joy horizontally, try it verically. This sorted it for me.

 

 

Reset the tool to default and swap the top/bottom screen edge values for both eyes.

Edited January 3, 2020 by oz555

[speed-of-heat]

the only thing I can think of, and I am sure you must of tried it is delete mixed reality lua files () in your saved games folder (the ones for cross eyed ness). if that doesnt work create a new one with the left and right eye identical, my right eye is dominant so I use my right eye settings...

 

I'm also technically outside of the scope of the allowed IPD (but at the other end to you)on the Reverb...

 

other than that i'm out of airspeed altitude and ideas!

[Gregkar]

whilst a high super sampling level was required for the O+ to make it anywhere near readable, frankly the base resolution of the Reverb is more than enough to get a readable and clear cockpit... you will find that 100% is steam is fairly close to native resolution (per eye) of the reverb, and that for me is good enough...

 

YMMV

 

i clicked on your signature "My DCS VR Settings" but the link doesn't work. can you share them? Thank you!

[speed-of-heat]

try now :) privacy was set to "shields up" :)

[Gregkar]

thanx, will try them tonight. i left steam setting in AUTO and only changed windows setting to ultra (beta), is this wrong?

[speed-of-heat]

the one thing I am super sure about regarding VR is there is no "universal wrong" only what is wrong for you... there are so many variables, software, hardware, the physiology of the person, their eyesight etc that the best you can hope for is someone else's settings gets you close, and then you tune.

 

I also changed my Head Set display settings to "Very high (beta)".

 

I changed my settings from auto in Steam VR, mostly because of a legacy thing where it was setting the wrong resolution, but also it means I "know" what resolution the game is set to just by looking.

[Fisu_MAD]

[speed-of-heat]

Well, I'm testing reverbs and a normal 1080. I'm still not convinced to keep them. I have to put everything to a minimum in dcs by overclocking the GPU (clock and memory) with the refresh rate at 60 Hz with the ASW and the active motionvector. On missions with few units run smooth. But when the thing is loaded the fps go down and the ss chart on SteamVR turns red orange. The worst of all this is that the GPU and the CPU are at 50% usage. If 30% more of the resources will be used, it would not have to be doing three-track circuses. Any with a magic wand for this case? ������

 

I'm not sure I have a magic bullet per-say, but, I notice you have an i7, which one what spec(?). But try turning off hyper threading, in the BIOS/UEFI (DCS will only use 2 processors so you will only really ever see about 1/2 to 1/3 of them used and its not very good with hyper threading)

 

Set the refresh rate to 90 and leave motion vector enabled, (there is no ASW per-say on WMR thats for Oculus). I get a fairy solid 45FPS on my settings as per my sig.

[Fisu_MAD]

I'm not sure I have a magic bullet per-say, but, I notice you have an i7, which one what spec(?). But try turning off hyper threading, in the BIOS/UEFI (DCS will only use 2 processors so you will only really ever see about 1/2 to 1/3 of them used and its not very good with hyper threading)

 

Set the refresh rate to 90 and leave motion vector enabled, (there is no ASW per-say on WMR thats for Oculus). I get a fairy solid 45FPS on my settings as per my sig.

You have a ti, not normal 1080. All my cores are working at the same time with the same load. I test 90 Hz, but in 60 Hz the fps are more.

[speed-of-heat]

You have a ti, not normal 1080. All my cores are working at the same time with the same load. I test 90 Hz, but in 60 Hz the fps are more.

 

the TI gives me a smidge more performance and a bit more memory... your CPU should give you an edge in terms of performance as DCS is more likely to be CPU bound than GPU bound (as your own numbers show, the GPU is not being fed enough to take it above 50% utilisation)

 

Whilst the cores might look like they are all working at the same level at the same time, this is not the case... what you are seeing is an artefact of the processor switching the load between multiple cores to maintain (amongst other things) temp, it does it faster than the resolution of most of the tools that can display processor workloads so it all looks the same.

 

If you have motionvector on, and you are running at 60hz your will be locked at maximum of 30FPS; if you are running at 90hz with motionvector on it will lock at a maximum of 45FPS... so something is not right. I'd set it back to 90, make sure motion vector is enabled in default.vrsettings, and restart your PC. YMMV but my experience on a lesser processor is that you are CPU bound try turning off hyper threading, you can always turn it back on if it makes no difference...

 

If you havent already seen it try here https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/

[Kirin]

Any news on the native Reverb support Wags hinted at a while ago?

[imacken]

Any news on the native Reverb support Wags hinted at a while ago?

Been asked several times recently, but we don't get any response, so I guess the answer is no!

[speed-of-heat]

Been asked several times recently, but we don't get any response, so I guess the answer is no!

 

I'm curious to what it would even mean, it seems at odds with ED's normal approach which isn't to support specific bits of hardware, unless its at the LUA level...

[Kirin]

<sad VR noises>

[dburne]

I'm curious to what it would even mean, it seems at odds with ED's normal approach which isn't to support specific bits of hardware, unless its at the LUA level...

 

Well they support Oculus natively.

Would seem to make sense to support WMR natively as that encompasses more headsets than just Reverb.

[TOYKILLA]

Yep,that would be great.

 

Gesendet von meinem SM-G973F mit Tapatalk

[speed-of-heat]

Well they support Oculus natively.

Would seem to make sense to support WMR natively as that encompasses more headsets than just Reverb.

OK yes it would make sense to do native WMR support ...

[MA_Goblin]

ED has stated that native WMR is on to do list

[Wicked.-]

Did you run the debug tool vertically?

 

 

If like me you had no joy horizontally, try it verically. This sorted it for me.

 

 

Reset the tool to default and swap the top/bottom screen edge values for both eyes.

 

 

 

 

lol, bro I spent ten hours trying EVERY possible setting, vertical, horizontal, outside, inside... et al. Moving the left lens to the left got it clearer, same for the right lens but it didn't take as much movement. I have to move the lenses farther left than the sliders in the app allow for and therefore I've edited the file itself. I can see improvement but not enough to get rid of the cross eyed vision and yes, I'm moving both lenses. My bigger question is, why do I have to do this at all? Outside of DCS everything is great, it's not till DCS is loaded that the image goes to shit.

[eaglecash867]

Well they support Oculus natively.

Would seem to make sense to support WMR natively as that encompasses more headsets than just Reverb.

 

If anyone is planning on using SuperSampling of any kind, I think native support would leave us with just the DCS PD setting. From my experimentation, DCS PD seems to be less efficient for some reason.

[Wicked.-]

If anyone is planning on using SuperSampling of any kind, I think native support would leave us with just the DCS PD setting. From my experimentation, DCS PD seems to be less efficient for some reason.

 

You can use Oculus Tray Tool to set SS instead of PD even though Oculus API is native.. I would expect that to be the case if WMR became native as well. One would hope anyway.

[speed-of-heat]

I don’t believe that’s true of WMR today