HP's Reverb VR Pro Headset

To be honest, all these problems people reporting not just for HP Reverb but for other VR as for example SO+ or Rift S too are similar and they are related more to the DP, HDMI, and USB connector design which is not designed for the constant moving of the cable.

Yup. I'm also questioning at this point why the trend seems to be toward Display Port. Display Port is far less forgiving of any extra resistance in the connections than HDMI is. I can run my Rift CV1 all day long on a 10 foot HDMI extension, but the Reverb's display port won't run at all on a 10 foot extension, and is crappy at best on a 6 foot extension. Kind of strange that DP is being chosen more and more for VR, given its cable length constraints. "Room scale" VR is apparently limited to a 6 foot radius from your computer with DP.

Still trying to figure out how to deal with the "seeing the lens edges" problem. I have the side straps backed all the way off, and I still see lens edges. I found that if I put a towel between the facepad and my face, it FINALLY gets me far enough away from the lenses to not see the edges in the lower portion of my vision. Also, when I can no longer see the lens edges, the focus of everything is improved. Without the extra spacer, everything is still really sharp, but still a half-step out of focus compared to its full potential. The question at this point is how I add more of a permanent spacer pad, without voiding the warranty.

I would definitely try uninstalling and reinstalling SteamVR.

Well I'm getting LOTS of SteamVR crashes. It was all running fine and then for the last few days it's been a massive pain the arse. I'll try a reinstall of SteamVR to see if that helps. I pulled this from the logs if it inspires anyone in any way. There seem to be assorted errors relating to various drivers. It's odd as it's mainly DCS where I encounter the problem. Running other Steam apps seems more stable but still not perfect. Oh well, the woes of the early adopter etc.

 

 

Thu Jun 27 2019 00:12:16.499 - Steam.exe 1.5.15 startup with PID=12848, config=C:\Program Files (x86)\Steam\config, runtime=C:\Program Files (x86)\Steam\steamapps\common\SteamVR

Thu Jun 27 2019 00:12:16.500 - vrclient type=VRApplication_SteamWatchdog

Thu Jun 27 2019 00:12:16.505 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\htc\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.505 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.505 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\null\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.505 - [settings] Load Default Json Settings from F:\steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.506 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.507 - [settings] Load Json Settings from C:\Program Files (x86)\Steam\config\steamvr.vrsettings

Thu Jun 27 2019 00:12:16.508 - [settings] Load Default Json Settings from F:\steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.508 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\htc\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.509 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.509 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\null\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.509 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\settings\default.vrsettings

Thu Jun 27 2019 00:12:16.510 - [settings] Load Json Settings from C:\Program Files (x86)\Steam\config\steamvr.vrsettings

Thu Jun 27 2019 00:12:16.522 - Could not create interface in driver gamepad from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\gamepad\bin\win32\driver_gamepad.dll.

Thu Jun 27 2019 00:12:16.522 - Unable to init watchdog mode for driver gamepad: VRInitError_Init_InterfaceNotFound

Thu Jun 27 2019 00:12:16.525 - Could not create interface in driver holographic from F:\steam\steamapps\common\MixedRealityVRDriver\bin\win32\driver_holographic.dll.

Thu Jun 27 2019 00:12:16.525 - Unable to init watchdog mode for driver holographic: VRInitError_Init_InterfaceNotFound

Thu Jun 27 2019 00:12:16.536 - error VRInitError_Init_LowPowerWatchdogNotSupported when initing driver lighthouse from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\bin\win32\driver_lighthouse.dll.

Thu Jun 27 2019 00:12:16.536 - Unable to init watchdog mode for driver lighthouse: VRInitError_Init_LowPowerWatchdogNotSupported

Thu Jun 27 2019 00:12:16.537 - Could not create interface in driver oculus from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\oculus\bin\win32\driver_oculus.dll.

Thu Jun 27 2019 00:12:16.537 - Unable to init watchdog mode for driver oculus: VRInitError_Init_InterfaceNotFound

Thu Jun 27 2019 00:12:16.539 - Could not create interface in driver oculus_legacy from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\oculus_legacy\bin\win32\driver_oculus_legacy.dll.

Thu Jun 27 2019 00:12:16.539 - Unable to init watchdog mode for driver oculus_legacy: VRInitError_Init_InterfaceNotFound

Thu Jun 27 2019 00:12:16.539 - No drivers were capable of being watchdogs. Failing init.

I would definitely try uninstalling and reinstalling SteamVR.

Tried that last night. I did still experience a a crash but it seems better than before, with none of those driver errors in the log file.

I just registered my Hp Reverb Pro on HP's site by serial number and it appears the Professional models have a 36 month return and exchange. There is also free setup assistance for three months. I think Oculus and Samsung is one year. Of course we may need three years with the Reverb. lol

 

 

HP manufacturer/base warranty

 

Warranty type Manufacturer Warranty

Service type Wty: HP HW Maintenance Offsite Support

Status Active: Covered under Manufacturer warranty, 36 months remaining.

Start Date May 31, 2019

End Date June 29, 2022

Service Level Std Office Hrs Std Office Days

Std Office Hrs Std Office Days

Global Coverage

Standard Material Handling

Standard Parts Logistics

No Usage Limitation

2 Business Days Turn-Around

Customer delivers to RepairCtr

Customer Pickup at RepairCtr

Deliverables Offsite Support & Materials

Hardware Problem Diagnosis

 

 

 

Service type Wty: HP Support for Initial Setup

Status Active: Covered under Manufacturer warranty, 3 months remaining.

Start Date May 31, 2019

End Date September 27, 2019

Service Level Std Office Hrs Std Office Days

NextAvail TechResource Remote

2 Hr Remote Response

Unlimited Named Callers

Deliverables Initial Setup Assistance

How do you register it? I have an account at HP but can't find warranty registration anywhere

Nevermind, found it. I got 2 years with my Reverb Pro though:

"

HP manufacturer/base warranty

Warranty type Manufacturer Warranty

Service type Wty: HP Parts Exchange Support

Status Active: Covered under Manufacturer warranty, 24 months remaining.

Start Date May 24, 2019

End Date June 22, 2021

Service Level NextAvail TechResource Remote

Std Office Hrs Std Office Days

Normal Product Lead Time

HP Ships To Customer Site

Customer delivers to RepairCtr

Deliverables Parts Exchange

Remote Support and Diagnosis

Extend your warranty

 

Service type Wty: HP Support for Initial Setup

Status Active: Covered under Manufacturer warranty, 3 months remaining.

Start Date May 24, 2019

End Date September 20, 2019

Service Level NextAvail TechResource Remote

Std Office Hrs Std Office Days

2 Hr Remote Response

Unlimited Named Callers

Deliverables Initial Setup Assistance "

 

Still trying to figure out how to deal with the "seeing the lens edges" problem. I have the side straps backed all the way off, and I still see lens edges. I found that if I put a towel between the facepad and my face, it FINALLY gets me far enough away from the lenses to not see the edges in the lower portion of my vision. Also, when I can no longer see the lens edges, the focus of everything is improved. Without the extra spacer, everything is still really sharp, but still a half-step out of focus compared to its full potential. The question at this point is how I add more of a permanent spacer pad, without voiding the warranty.

Third part VRCover.

One size fits all in non-adjustable VR headsets only seems to apply to about 70+% of the population. If you are near the fringe of what works with IPD too far outside of their setting, or the distance from the front of your face to the front of your eyes you may see some things cause by misalignment with the lenses. If it is too annoying to use then maybe the Valve Index or Acer Ojo when the come out with adjustable IPD at least will help some of that.

I would contact HP tech support and tell them what you are seeing under their initial setup warranty (you paid for that support). Maybe they have an alternative face pad or other suggestions (but likely nothing - lol). It is still early but I suspect their commercial customers may demand some kind of fix if it makes the unit less usable for a good portion of their customers.

Service type Wty: HP Support for Initial Setup

Status Active: Covered under Manufacturer warranty, 3 months remaining.

Start Date May 31, 2019

End Date September 27, 2019

Service Level Std Office Hrs Std Office Days

NextAvail TechResource Remote

2 Hr Remote Response

Unlimited Named Callers

Deliverables Initial Setup Assistance

 

Still trying to figure out how to deal with the "seeing the lens edges" problem. I have the side straps backed all the way off, and I still see lens edges. I found that if I put a towel between the facepad and my face, it FINALLY gets me far enough away from the lenses to not see the edges in the lower portion of my vision. Also, when I can no longer see the lens edges, the focus of everything is improved. Without the extra spacer, everything is still really sharp, but still a half-step out of focus compared to its full potential. The question at this point is how I add more of a permanent spacer pad, without voiding the warranty.

I noticed that warranties tend to vary by country although i have seen where the EU members get a better warranty than the US sometimes like 1 year for US vs 2 years for EU.

I just checked an it still says 36 months warranty. (who knows what it will say in a few months - lol)

Start Date May 31, 2019

End Date June 29, 2022

How do you register it? I have an account at HP but can't find warranty registration anywhere

Nevermind, found it. I got 2 years with my Reverb Pro though:

Are you using a cable rated for 4k?

Standard HDMI Cable: 1,782 GBit/s

Highspeed HDMI Cable: 8,16 GBit/s

Definitely not trying to insult, but without them changing the plug format, we the consumer pay the price in confusion.

Yup. I'm also questioning at this point why the trend seems to be toward Display Port. Display Port is far less forgiving of any extra resistance in the connections than HDMI is. I can run my Rift CV1 all day long on a 10 foot HDMI extension, but the Reverb's display port won't run at all on a 10 foot extension, and is crappy at best on a 6 foot extension. Kind of strange that DP is being chosen more and more for VR, given its cable length constraints. "Room scale" VR is apparently limited to a 6 foot radius from your computer with DP.

 

Still trying to figure out how to deal with the "seeing the lens edges" problem. I have the side straps backed all the way off, and I still see lens edges. I found that if I put a towel between the facepad and my face, it FINALLY gets me far enough away from the lenses to not see the edges in the lower portion of my vision. Also, when I can no longer see the lens edges, the focus of everything is improved. Without the extra spacer, everything is still really sharp, but still a half-step out of focus compared to its full potential. The question at this point is how I add more of a permanent spacer pad, without voiding the warranty.

The Reverb is hitting the current HDMI standard limitations. There is a lot of data moving really quickly in VR at 4K.

DisplayPort has similar capabilities as HDMI; DisplayPort 1.4 can transmit up to 32.4Gbs bandwidth, much more than HDMI’s 18Gbps limitation. This allows a higher resolution of 8K at 60Hz with 10-bit color HDR or 4K at 120Hz to be viewed.

DisplayPort also supports multi-stream transport technology, which allows multiple independent displays per port. By connecting compatible monitors through a daisy chain or using a Multi-Stream Transport hub, you can use a multiple monitor setup through a single display output. This format makes it an excellent choice for any type of user who works with multiple displays.

The interface is also becoming more popular with PC gaming with DisplayPort support using NVIDIA’s G-Sync and AMD’s FreeSync technology. The sync technologies prevent against screen tearing by aligning the computer’s hardware to the system’s GPU to match with the monitor’s refresh rate.

So here’s my story. I’ve been using the O+ for six months with its twerks. I’ve had ok frames around 40 and no stutters. My biggest problem being the readability of the displays in the Hornet. So, for two days I’ve been testing my new Reverb.

The readability is definitely better than the O+ but...

1. When I put them on in DCS it seems like there are some misalignment as my eyes need to recalibrate. It’s a strange feeling. Initially I figured it had to do with the IPD, but mine is at 64 and I’ve played around and checked the physical alignment in the glasses, that’s spot on. The O+ had some misalignment error that were fixed via a software debugger in dcs. This might be the same.

2. The Reverb gets really hot.

3. I’ve had several instances of flickering both eyes. Also they gone black ones in a while. So I started testing a bit. Some say this is due to the cable and the contact on the headset. Mine turned black when looking left. So I held the head straight and only manipulated the cable- nothing. So, it all came down to the fact that looking left had me looking right at the carrier. This also gives me a significant drop in FPS. Whenever looking at objects it goes down to the 30s, looking up it can go to 90.

My five cents is that the reverb gets to warm, or can’t handle the load. It might be the GPU (2080TI) but I doubt that.

4. Being a O+ driver I didn’t know what screen door effect was, now I do. It looks like the picture is superimposed on a canvas. It might be that you get used to it by time.

That’s my first impression.

HDMI 2.1 supports 4K120 but very few TVs currently have it (high end OLED LG and QLED Samsung). There is also no GPU card that supports HDMI 2.1, although next gen NVIDIA GPUs will likely have it.

Scuttlebutt is the Reverb is getting a make over soon.

So here’s my story. I’ve been using the O+ for six months with its twerks. I’ve had ok frames around 40 and no stutters. My biggest problem being the readability of the displays in the Hornet. So, for two days I’ve been testing my new Reverb.

 

The readability is definitely better than the O+ but...

1. When I put them on in DCS it seems like there are some misalignment as my eyes need to recalibrate. It’s a strange feeling. Initially I figured it had to do with the IPD, but mine is at 64 and I’ve played around and checked the physical alignment in the glasses, that’s spot on. The O+ had some misalignment error that were fixed via a software debugger in dcs. This might be the same.

 

2. The Reverb gets really hot.

 

3. I’ve had several instances of flickering both eyes. Also they gone black ones in a while. So I started testing a bit. Some say this is due to the cable and the contact on the headset. Mine turned black when looking left. So I held the head straight and only manipulated the cable- nothing. So, it all came down to the fact that looking left had me looking right at the carrier. This also gives me a significant drop in FPS. Whenever looking at objects it goes down to the 30s, looking up it can go to 90.

 

My five cents is that the reverb gets to warm, or can’t handle the load. It might be the GPU (2080TI) but I doubt that.

 

4. Being a O+ driver I didn’t know what screen door effect was, now I do. It looks like the picture is superimposed on a canvas. It might be that you get used to it by time.

 

That’s my first impression.

It took me a while to notice the mura effect and I think once you do notice it, it also contributes to the SDE effect, as it's like looking through a slightly grubby window when you look at a single flat coloured surface. When I'm flying I don't notice it at all though.

From the way you describe it I reckon O+ tech with Reverb displays would be pretty awesome.

source?

Scuttlebutt is the Reverb is getting a make over soon.

Something sounds wrong. I just played for two hours and my Reverb didn't even get warm. Also, my IPD is 64 and the view seems about perfect (no haloing or misalignment). There are IPD settings in both DCS VR Settings and in WMR Settings in Windows under Calibration. I have them both set to 64 mm. That is what amazed me the most besides the clarity with the Reverb is the very clear and large sweet spot which is most of the screen compared to my Lenovo Explorer which is crude by comparison.

For DCS the more terrain in the view generally the more the FPS will drop in any VR. Flying low and upside down over trees in the F-18 really is really graphics resource intensive.

With any kind of flicker, black, or blinking or sound issues I would ask HP for a replacement cable to try before sending it in.

Just my two cents. My Reverb is actually performing very well with the exception of me monkeying with the USB plug at the PC one time. I can get a fault with my other USB stuff too if I monkey with the USB hub that connects a lot of stuff together. My 60 lb. dog stepped on it once and gave my Razer keyboard a USB error. lol

So here’s my story. I’ve been using the O+ for six months with its twerks. I’ve had ok frames around 40 and no stutters. My biggest problem being the readability of the displays in the Hornet. So, for two days I’ve been testing my new Reverb.

 

The readability is definitely better than the O+ but...

1. When I put them on in DCS it seems like there are some misalignment as my eyes need to recalibrate. It’s a strange feeling. Initially I figured it had to do with the IPD, but mine is at 64 and I’ve played around and checked the physical alignment in the glasses, that’s spot on. The O+ had some misalignment error that were fixed via a software debugger in dcs. This might be the same.

 

2. The Reverb gets really hot.

 

3. I’ve had several instances of flickering both eyes. Also they gone black ones in a while. So I started testing a bit. Some say this is due to the cable and the contact on the headset. Mine turned black when looking left. So I held the head straight and only manipulated the cable- nothing. So, it all came down to the fact that looking left had me looking right at the carrier. This also gives me a significant drop in FPS. Whenever looking at objects it goes down to the 30s, looking up it can go to 90.

 

My five cents is that the reverb gets to warm, or can’t handle the load. It might be the GPU (2080TI) but I doubt that.

 

4. Being a O+ driver I didn’t know what screen door effect was, now I do. It looks like the picture is superimposed on a canvas. It might be that you get used to it by time.

 

That’s my first impression.

Are you using a cable rated for 4k?

Standard HDMI Cable: 1,782 GBit/s

Highspeed HDMI Cable: 8,16 GBit/s

 

Definitely not trying to insult, but without them changing the plug format, we the consumer pay the price in confusion.

I don't have a problem with my Rift, which has an HDMI interface. The problem is that the Reverb doesn't use HDMI, it uses Display Port. ;)

source?

Well as I said it was scuttlebutt...

A guy over on the Oculus Forums supposedly spoke with HP support on returning his, and he claimed the person he talked to told him they were making changes for a revised version to come out at some point to address the more common issues.

Right. My RTX2080 doesn't support it. Now 4K isn't enough - we want 8K. The three 4K TVs in my house are already nearly obsolete. :D

HDMI Output : Yes x 2 (Native) (HDMI 2.0b)

Display Port : Yes x 2 (Native) (DisplayPort 1.4)

HDMI® Specification 2.1 is the most recent update of the HDMI specification and supports a range of higher video resolutions and refresh rates including 8K60 and 4K120, and resolutions up to 10K

https://www.hdmi.org/manufacturer/hdmi_2_1/index.aspx

HDMI 2.1 supports 4K120 but very few TVs currently have it (high end OLED LG and QLED Samsung). There is also no GPU card that supports HDMI 2.1, although next gen NVIDIA GPUs will likely have it.

There is a revised cable I was told and should receive in the next day or two.

Well as I said it was scuttlebutt...

 

A guy over on the Oculus Forums supposedly spoke with HP support on returning his, and he claimed the person he talked to told him they were making changes for a revised version to come out at some point to address the more common issues.

There is a revised cable I was told and should receive in the next day or two.

Is that for all owners? Or just for those who reported a fault?

Sorry waiting for mine to arrive, wasn't yet aware it is displayport.

Displayport cables are limited to two meters or revert to the next lowest spec.

RBR (Reduced Bit Rate) RBR DisplayPort Cable 6.48 Gbit/s

HBR (High Bit Rate) Standard DisplayPort Cable 10.80 Gbit/s

HBR2 (High Bit Rate 2) Standard DisplayPort Cable 21.60 Gbit/s

HBR3 (High Bit Rate 3) DP8K Cable 32.40 Gbit/s

I don't have a problem with my Rift, which has an HDMI interface. The problem is that the Reverb doesn't use HDMI, it uses Display Port. ;)

Is that for all owners? Or just for those who reported a fault?

I have not heard of them preemptively shipping them out so my guess is only for reported problems. I was looking through reported problems on the HP forum yesterday and there was less than I expected (less than half a dozen problems posted like black screen or flickering and one guy was from outside of the US because he said the local support didn't know anything about the Reverb) but maybe that reflects how few actually got shipped here in the US. :music_whistling:

I know of one other that has a cable coming but from Reddit.

Gaming Accessories

https://h30434.www3.hp.com/t5/Gaming-Accessories/bd-p/GamingAccessories

Is that for all owners? Or just for those who reported a fault?

The cable is (4m headset cable) from HP's specifications. It seems to be a heavy gauge cable but hard to tell without slicing through it. I see no markings on the cable. It's actually two heavy cables stuck together.

Sorry waiting for mine to arrive, wasn't yet aware it is displayport.

 

Displayport cables are limited to two meters or revert to the next lowest spec.

 

 

RBR (Reduced Bit Rate) RBR DisplayPort Cable 6.48 Gbit/s

HBR (High Bit Rate) Standard DisplayPort Cable 10.80 Gbit/s

HBR2 (High Bit Rate 2) Standard DisplayPort Cable 21.60 Gbit/s

HBR3 (High Bit Rate 3) DP8K Cable 32.40 Gbit/s

Makes me wonder if they exceeded published limitations with the original cables. It would only be made worse by adding extensions.

The cable is (4m headset cable) from HP's specifications. It seems to be a heavy gauge cable but hard to tell without slicing through it. I see no markings on the cable. It's actually two heavy cables stuck together.