HP's Reverb VR Pro Headset

I consider that good news since there is the possibility the clarity might improve even more although using the Reverb my gut is saying this is really clear now. :shocking:

I asked that Microsoft guy on Reddit if every Reverb on 1903 is affected which it seems. Hopefully, he gives me a response.

With as clear as my Reverb is I don't see the need for a workaround and will just wait for the update at this point unless it is really simple. ;-)

Here's the official confirmation of the Win10 1903 WMR VR renderTargetScale bug that impacts the Reverb, Odyssey and other WMR headsets. Hopefully quiets the 'flat earthers' on this, as it was getting tiresome to being told that it didn't exist, especially when trying to help them.

 

https://steamcommunity.com/app/719950/discussions/0/1644292361960505688/

 

"A number of users have reported issues with blurriness after upgrading to Windows 1903. Unfortunately we didn't see this in insider flighting and in our private testing.

 

We have investigated and the underlying issue here is part of the Windows release, and not contained in the WMR for SteamVR package. We've tracked down the issue and have a fix ready, and are working on getting it released as a Windows update. Doing this means it takes a few weeks as Windows updates ship on a regular schedule.

 

If you have already updated to 1903, please know that we are actively looking into workarounds to address the issues here.

 

If you haven't updated to 1903 just yet, you may want to wait for this to be fixed."

 

You can also discuss the bug and possible workarounds with them here:

 

I was doing a little checking with having received now two Microsoft updates on 1903. ...

The VRSettings file has RenderTargetScale set a 2.0 and I have not touched that.

The current WMR bug on 1903 is essentially that the renderTargetScale in that file is forced to be 1.0 and that the maximum buffer size is limited, meaning it upscales a blurrier image. It seems to have about a 10% impact on the Reverb, but a 21% degradation on the Odyssey Plus (so much more obvious). Hopefully a fix or workaround is coming soon. The Reverb number of pixels is so high it's not like a showstopper, but for the O+ it will be nice to be able to move to 1903.

Thanks. I'll take a 10% jump in clarity any day of the week. I do keep reading the posts where the Odyssey Plus folks are noticing the blur.

I was trying to get the red indicator to come on for re-projection with multiple planes and lots of things going on but so far re-projection seems to stay on with only the light and dark blues. Strange because my hardware (although overclocked) seems slightly less than some of the others with the ti version of the 2080. Must be Settings or the ti doesn't make much difference in this regard.

The current WMR bug on 1903 is essentially that the renderTargetScale in that file is forced to be 1.0 and that the maximum buffer size is limited, meaning it upscales a blurrier image. It seems to have about a 10% impact on the Reverb, but a 21% degradation on the Odyssey Plus (so much more obvious). Hopefully a fix or workaround is coming soon. The Reverb number of pixels is so high it's not like a showstopper, but for the O+ it will be nice to be able to move to 1903.

@secoda - I don't get the red indicator often. Only has happened once in a week. I was looking at two f18s (players with custom skins) on the Al Bateen runway running up for takeoff. Other than that, its been great. I have my steam ss value up to 212% or ~2000x2500 to see how things may run with the Reverb. So far so good.

And on 1903 - decided to wait to patch up until the issue is resolved with confirmation.

The Steam SS setting may be a lot of the difference if there is any. I see the performance degrade as I adjust it up.

Steam sees the Reverb as VR1000-2xxx. lol

@secoda - I don't get the red indicator often. Only has happened once in a week. I was looking at two f18s (players with custom skins) on the Al Bateen runway running up for takeoff. Other than that, its been great. I have my steam ss value up to 212% or ~2000x2500 to see how things may run with the Reverb. So far so good.

 

And on 1903 - decided to wait to patch up until the issue is resolved with confirmation.

Looks like the shop BLT dates have slipped again, most were on 6/21, now only one warehouse showing that, new dates of 7/12...

Hi all,

I'm thinking on getting this VR glasses, and at the same time build a new system... how does the RTX 2080 perform? Or is it recommended a 2080Ti for this resolution?

I'm also planning on i7 9700K, 32GB RAM, SSD NVMe M.2, ...

Thanks!

The Steam SS setting may be a lot of the difference if there is any. I see the performance degrade as I adjust it up.

 

Steam sees the Reverb as VR1000-2xxx. lol

 

 

 

I pumped it already up to 250%. :D

Hi all,

 

I'm thinking on getting this VR glasses, and at the same time build a new system... how does the RTX 2080 perform? Or is it recommended a 2080Ti for this resolution?

 

I'm also planning on i7 9700K, 32GB RAM, SSD NVMe M.2, ...

 

Thanks!

That system begs for a 2080 Ti...

:smilewink:

O.M.G. Reverb is INCREDIBLY clear. I mean I got used to clarity because of Pimax5K+. I thought *that* was a step up from Rfit. Before I got SteamVR Mixed Reality installed (Windows Mixed Reality installed by itself) I thought I was ready to go. Since WMR installed by itself. Then I fired up DCS and it came up as a regular 2D big screen app inside the WMR portal. And even though I knew something was off, I got VERY excited because the 2D DCS in the big panel in the portal looked INCREDIBLE. No different than my monitor.

 

 

So I took a deep breath and installed the SteamVR's Windows Mixed Reality (search for it in the store). Then I jacked up the SS in SteamVR to 188%. That gives me 2208x2160 resolution. I set DCS' PD at 1.0.

 

 

WOW. HOLY COW. I mean there was *nothing* in the FA18 that I couldn't read. The small numbers on the MFDs were not a problem.

 

 

And I got 70's FPS in downtown Dubai at 300' off the ground. I even did the "Ready on the flight line" instant mission because in the past, that ate up FPS like crazy. Just looking at the other parked Hornets made the FPS drop. Here, it just went to 45, and went back up to 70s and 80s.

 

 

 

I mean COME ON!!!! @imacken, I have to believe something was wrong with your Reverb. There is a CLEAR difference between P5K+ which already has a CLEAR difference between the CV1.

 

 

I didn't change any settings yet. My in game setting is below.

 

 

And the default.vrsetings file had "renderTargetScale" : 2.0

 

 

And everything for motion reprojection was commented out (the default)

 

 

This was in Windows 1809.

 

 

 

 

 

hans interesting post - just want to make sure your .vrsettings are the same as mine - the three I have enabled/added are the following:

"forceHalfRateWithReprojectionMode" : "motionvector",

"motionReprojectionMode" : "auto",

"motionReprojectionIndicatorEnabled" : true,

Yes, it improved. My test mission file with carrier, and planes 5 & 10 miles out are easier to spot. But I'll do an exhaustive review after I get done tweaking my settings. This was basically, plug it in and go slack-jawed with clarity. :D

Do you miss the wide FOV? And what about IPD? I had to keep my og Rift cranked to the max, so I doubt the "software only" sets would work for me.

That system begs for a 2080 Ti...

 

:smilewink:

I would take this with a grain of salt but it looks like the Supers will replace the 2080 and below - not the ti.

"At the top of the GPU heap is the GeForce RTX 2080 SUPER, which is expected to have an MSRP of $799. This is the exact same price as the current GeForce RTX 2080, but the SUPER variant will have more CUDA cores and higher clocks which would make it an even better value."

NVIDIA GeForce RTX SUPER Turing Pricing Allegedly Leaks As Radeon Navi Launch Nears

https://hothardware.com/news/nvidia-geforce-rtx-super-turing-pricing-allegedly-leaks

GeForce RTX 2080 Ti: 4,352 CUDA cores, TU102-300 GPU, 11GB GDDR6 (14Gbps)

GeForce RTX 2080 SUPER: 3,072 CUDA cores, TU104-450 GPU, 8GB GDDR6 (16Gbps)

GeForce RTX 2080: 2,944 CUDA cores, TU104-410 GPU, 8GB GDDR6 (14Gbps)

GeForce RTX 2070 SUPER: 2,560 CUDA cores, TU104-410 GPU, 8GB GDDR6 (14Gbps)

GeForce RTX 2070: 2,304 CUDA cores, TU106-410 GPU, 8GB GDDR6 (14Gbps)

GeForce RTX 2060 SUPER: 2,176 CUDA cores, TU106-410 GPU, 8GB GDDR6 (14Gbps)

GeForce RTX 2060: 1,920 CUDA cores, TU106-200 GPU, 6GB GDDR6 (14Gbps)

Looks like the shop BLT dates have slipped again, most were on 6/21, now only one warehouse showing that, new dates of 7/12...

They don't charge until they ship, so there's really no harm in ordering.

hans interesting post - just want to make sure your .vrsettings are the same as mine - the three I have enabled/added are the following:

 

 

"forceHalfRateWithReprojectionMode" : "motionvector",

"motionReprojectionMode" : "auto",

"motionReprojectionIndicatorEnabled" : true,

I didn't change the file yet.

Do you miss the wide FOV? And what about IPD? I had to keep my og Rift cranked to the max, so I doubt the "software only" sets would work for me.

I *do*. But, the clarity is on a whole new level. And the FOV is better than Rift CV1. So I can live with it. So I had said before I got the Reverb that I hope the visual clarity makes up for lack of FoV.

And that turns out to be the case.

Here's the official confirmation of the Win10 1903 WMR VR renderTargetScale bug that impacts the Reverb, Odyssey and other WMR headsets. Hopefully quiets the 'flat earthers' on this, as it was getting tiresome to being told that it didn't exist, especially when trying to help them.

 

https://steamcommunity.com/app/719950/discussions/0/1644292361960505688/

 

"A number of users have reported issues with blurriness after upgrading to Windows 1903. Unfortunately we didn't see this in insider flighting and in our private testing.

 

We have investigated and the underlying issue here is part of the Windows release, and not contained in the WMR for SteamVR package. We've tracked down the issue and have a fix ready, and are working on getting it released as a Windows update. Doing this means it takes a few weeks as Windows updates ship on a regular schedule.

 

If you have already updated to 1903, please know that we are actively looking into workarounds to address the issues here.

 

If you haven't updated to 1903 just yet, you may want to wait for this to be fixed."

 

You can also discuss the bug and possible workarounds with them here:

 

I'm glad the fix is in the works. I'm just glad i had the backup that I could fall back to. I'll play in the 1809 world until the fix is available and then boot into 1903. But thanks for the earlier heads up, or I wouldn't have gotten my rig to 1803 while waiting for the Reverb.

And to be fair, it's reasonable that someone would not believe everything online (on steam/reddit). I wouldn't take it as a personal affront.

I would take this with a grain of salt but it looks like the Supers will replace the 2080 and below - not the ti.

 

"At the top of the GPU heap is the GeForce RTX 2080 SUPER, which is expected to have an MSRP of $799. This is the exact same price as the current GeForce RTX 2080, but the SUPER variant will have more CUDA cores and higher clocks which would make it an even better value."

 

NVIDIA GeForce RTX SUPER Turing Pricing Allegedly Leaks As Radeon Navi Launch Nears

https://hothardware.com/news/nvidia-geforce-rtx-super-turing-pricing-allegedly-leaks

 

 

GeForce RTX 2080 Ti: 4,352 CUDA cores, TU102-300 GPU, 11GB GDDR6 (14Gbps)

GeForce RTX 2080 SUPER: 3,072 CUDA cores, TU104-450 GPU, 8GB GDDR6 (16Gbps)

GeForce RTX 2080: 2,944 CUDA cores, TU104-410 GPU, 8GB GDDR6 (14Gbps)

GeForce RTX 2070 SUPER: 2,560 CUDA cores, TU104-410 GPU, 8GB GDDR6 (14Gbps)

GeForce RTX 2070: 2,304 CUDA cores, TU106-410 GPU, 8GB GDDR6 (14Gbps)

GeForce RTX 2060 SUPER: 2,176 CUDA cores, TU106-410 GPU, 8GB GDDR6 (14Gbps)

GeForce RTX 2060: 1,920 CUDA cores, TU106-200 GPU, 6GB GDDR6 (14Gbps)

I got mine tonight and in all my other games it looks great but for some reason DCS has me above the menu and above the jet in game ...when I hit recenter it flashes for a bit and I'm right back above everything ....WTF ....Any ideas? ....Should have known if i was going to have an issue it would be in DCS :)

I got mine tonight and in all my other games it looks great but for some reason DCS has me above the menu and above the jet in game ...when I hit recenter it flashes for a bit and I'm right back above everything ....WTF ....Any ideas? ....Should have known if i was going to have an issue it would be in DCS :)

This is in OpenBeta? Maybe do a rebuild/repair? delete the shader/meta folder under SAVED GAMES?

Yep ..I'm in OB ...I'll give that a go and check back in ...

I got mine tonight and in all my other games it looks great but for some reason DCS has me above the menu and above the jet in game ...when I hit recenter it flashes for a bit and I'm right back above everything ....WTF ....Any ideas? ....Should have known if i was going to have an issue it would be in DCS :)

Sounds like this one? Uninstall Open VR Advanced if you have it?

https://forums.eagle.ru/showthread.php?t=243025

Otherwise, that can happen if the headset hasn't done its initialization before DCS starts up. The best order seems to be (1) put on headset, do the 'look left/up/right' thing (2) use a Desktop widget in the Cliff house WMR env and double click a DCS desktop icon from there.

If the headset is still trying to get a fix on its orientation in that start-up mode then it seems to confuse DCS center position when it starts.

I got mine tonight and in all my other games it looks great but for some reason DCS has me above the menu and above the jet in game ...when I hit recenter it flashes for a bit and I'm right back above everything ....WTF ....Any ideas? ....Should have known if i was going to have an issue it would be in DCS :)

Could be related to tracking, sounds similar to what I've experienced. Make sure you're room is well lit, and I also recommend a PCIe USB 3.1 card with SATA power from the PSU for your headset.

Sounds like this one? Uninstall Open VR Advanced if you have it?

 

https://forums.eagle.ru/showthread.php?t=243025

 

Otherwise, that can happen if the headset hasn't done its initialization before DCS starts up. The best order seems to be (1) put on headset, do the 'look left/up/right' thing (2) use a Desktop widget in the Cliff house WMR env and double click a DCS desktop icon from there.

 

If the headset is still trying to get a fix on its orientation in that start-up mode then it seems to confuse DCS center position when it starts.

This was it I had Open VR advanced settings installed ...Thanks!

I am just learning the Huey and the cockpit and flying is fabulous in the Reverb. It's really like you are there at this point.