HP's Reverb VR Pro Headset

[Bob_Bushman]

That's the first I have heard of an inateck card doing this and these have been recommended for years as they where supposedly recommended by Oculus themselves hardware they tested in-house with.

 

Seem the windows 1903 and the Fresco drivers has some issues at least with the S.

No surprise if they cause problem with VR in general.

 

But upgrading to 1903 that then that card has been solidly running my cv1 for two years, that's hmd itself and both sensors, and the S for a bit.

 

Neither of the two current drivers work for the S, the Fresco driver didn't even recognise the S to the pc, the MS drivers recognise but image in the device freeze.

No issue running from motherboard though, I connected the hotas hub to the card now and they work fine.

Edited August 1, 2019 by Bob_Bushman

[Tinkickef]

There are two parameters. "motionReprojectionMode" : "motionvector",

"motionvector" or "Auto". I am using "motionvector" which is on all of the time. "Auto" turns it off when it hits 90 FPS or goes below 45 FPS.

-

-

-

-

// Motion reprojection doubles framerate through motion vector extrapolation

// motionvector = force application to always run at half framerate with motion vector reprojection

// auto = automatically use motion reprojection when the application can not maintain native framerate

"motionReprojectionMode" : "motionvector",

 

 

 

 

That's the chappie I was looking for.

I had that set on my old rig and could not for the life of me remember what word replaced auto.

 

I have been using " force application to always run at half frame rate with motion vector reprojection".

It works ok, but the cockpit can get a little jittery when sat on the ground.

 

Thanks Secoda. :)

[eaglecash867]

EagleCash had suggested a powered USB port for running the Reverb.

I picked up the recommended item https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

 

 

I did this in preparation for when I actually purchase the reverb I am running the SO+ right now.

 

 

The card has the power cable plugged in and a single green led is on

 

The card has the front panel USB like 20pin connector plugged in

The card has the online driver installed for win10

Device manager recognizes the USB ports as "Fresco" or something like that

My Hotas and other items plugged into the card work normally

 

 

WMR says that an incompatible windows driver is installed and will not connect the SO+

 

 

Any Ideas?.... works again when plugged into MB usb port

 

 

Thanks

-Gun

 

That's the exact card I have had in my rig for the last 3 years (recommended by Oculus as having been tested with the CV1 and sensors), and it has been transferred from one 5960X build to my current 8700K build, both with Windows 10 installed. Never had a problem with it. I was thinking that the difference may be that I had the card already installed before the OS even went on the rig, because that was the case when I built the 8700K. But when I had my 5960X, that card was installed after I had been using the rig for a while. I even recently upgraded to Windows 10 1903, with the WMR fix, and it still works like a champ. Sorry, Gun, wish I was more help. Hopefully someone else has had the driver issue and knows how to fix it. This wouldn't be the first time we've all seen a hardware manufacturer that releases a "new and improved" version of something that doesn't work without jumping through a bunch of flaming hoops. :doh:

[HunchyTheHuncher]

There are two parameters. "motionReprojectionMode" : "motionvector",

"motionvector" or "Auto". I am using "motionvector" which is on all of the time. "Auto" turns it off when it hits 90 FPS or goes below 45 FPS.

-

-

-

-

// Motion reprojection doubles framerate through motion vector extrapolation

// motionvector = force application to always run at half framerate with motion vector reprojection

// auto = automatically use motion reprojection when the application can not maintain native framerate

"motionReprojectionMode" : "motionvector",

 

This is what I was doing too, keeping reprojection on all the time with "motionvector" stopped my FPS fluctuating so much and provided smoother gameplay.

 

HOWEVER...the last WMR for SteamVr Beta patch totally messed up reprojection on my system. I now have to turn it off completely as both the "auto" and "motionvector" settings give me severe jittering and reduce framerates down into the low 20s making the game unplayable (I was getting 45 - 60 before).

 

I have tried reinstalling both WMR for Steam VR and Steam VR, but the problem still persists. Would be interested to know if anyone else is experiencing similar issues with latest version of WMR for SteamVR Beta.

[wormeaten]

EagleCash had suggested a powered USB port for running the Reverb.

I picked up the recommended item https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

 

 

I did this in preparation for when I actually purchase the reverb I am running the SO+ right now.

 

 

The card has the power cable plugged in and a single green led is on

 

The card has the front panel USB like 20pin connector plugged in

The card has the online driver installed for win10

Device manager recognizes the USB ports as "Fresco" or something like that

My HOTAS and other items plugged into the card work normally

 

 

WMR says that an incompatible windows driver is installed and will not connect the SO+

 

 

Any Ideas?.... works again when plugged into MB usb port

 

 

Thanks

-Gun

 

That's the exact card I have had in my rig for the last 3 years (recommended by Oculus as having been tested with the CV1 and sensors), and it has been transferred from one 5960X build to my current 8700K build, both with Windows 10 installed. Never had a problem with it. I was thinking that the difference may be that I had the card already installed before the OS even went on the rig, because that was the case when I built the 8700K. But when I had my 5960X, that card was installed after I had been using the rig for a while. I even recently upgraded to Windows 10 1903, with the WMR fix, and it still works like a champ. Sorry, Gun, wish I was more help. Hopefully someone else has had the driver issue and knows how to fix it. This wouldn't be the first time we've all seen a hardware manufacturer that releases a "new and improved" version of something that doesn't work without jumping through a bunch of flaming hoops.

 

 

AS I understand the need for such card, the point is to disburden power usage from MB. If you connect all of your power consumers on just one power source you are losing the point to have such card anyway.

 

Try to connect your HOTAS and everything rest to MB USB and on that USB card only HMD or even oposite. Make this USB card dedicated Power supply for your HMD and let rest of device drain power true MB.

 

 

I'm just guessing but it is logical and didn't notice anyone mention this in that way. Worth to check it out, it is simple chack.

[aceofspades9963]

I think I read changing the gamma setting affected the washed out color appearance. Maybe it's too high. What is it set at?

 

I have it at 1.1 ots only noticable in dcs everywhere else its fine.

[eaglecash867]

AS I understand the need for such card, the point is to disburden power usage from MB. If you connect all of your power consumers on just one power source you are losing the point to have such card anyway.

 

Try to connect your HOTAS and everything rest to MB USB and on that USB card only HMD or even oposite. Make this USB card dedicated Power supply for your HMD and let rest of device drain power true MB.

 

 

I'm just guessing but it is logical and didn't notice anyone mention this in that way. Worth to check it out, it is simple chack.

 

Yup. That's exactly what I do. The USB card is for the HMD only. Then I have an external, self-powered hub for the HOTAS. The external hub provides enough power for the HOTAS, and it makes plugging everything in a lot easier.

[Secoda]

Too many layers of software. :cry: I won't update anything until you get it working again. Mine still works fine. What craziness.

 

This is what I was doing too, keeping reprojection on all the time with "motionvector" stopped my FPS fluctuating so much and provided smoother gameplay.

 

HOWEVER...the last WMR for SteamVr Beta patch totally messed up reprojection on my system. I now have to turn it off completely as both the "auto" and "motionvector" settings give me severe jittering and reduce framerates down into the low 20s making the game unplayable (I was getting 45 - 60 before).

 

I have tried reinstalling both WMR for Steam VR and Steam VR, but the problem still persists. Would be interested to know if anyone else is experiencing similar issues with latest version of WMR for SteamVR Beta.

[Naruto]

Well looks like newer HP Reverbs Pro HMDs only get a 13 month warranty now. I thought it was three years for a Pro version?

 

Edited August 2, 2019 by Naruto

[Secoda]

The one I returned is still out there. This was a direct HP buy. How long do you have for a full refund?

 

[Naruto]

The one I returned is still out there. This was a direct HP buy. How long do you have for a full refund?

 

 

I bought from ShopBLT so no refund unless there is a warranty claim within 30 days. I don't plan on refunding but its curious that mine is only good for 13 months direct from HP.

Edited August 1, 2019 by Naruto

[Naruto]

Going to the spec section now shows only 1 year warranty too.

 

https://store.hp.com/app/pdp/hp-reverb-virtual-reality-headset-professional-edition

[sze5003]

Well looks like newer HP Reverbs Pro HMDs only get a 13 month warranty now. I thought it was three years for a Pro version?

 

https://ibb.co/CsTgdPJ

I bought from ShopBLT so no refund unless there is a warranty claim within 30 days. I don't plan on refunding but its curious that mine is only goof for 13 months direct from HP.

So strange as that's what I read too. That is probably a mistake. Contact support and see what they say about the warranty.

[Harlikwin]

Well looks like newer HP Reverbs Pro HMDs only get a 13 month warranty now. I thought it was three years for a Pro version?

 

https://ibb.co/CsTgdPJ

 

 

Yeah I also noticed this discrepancy.

 

Also, how does one file a warranty claim for those guys that have done it.

 

My set is working fine, but I've had it for 4 whole days so far.

[Harlikwin]

I think I read changing the gamma setting affected the washed out color appearance. Maybe it's too high. What is it set at?

 

I had to change mine siginificantly coming from the rift 1.8 to like 1.4 or 1.3 IIRC.

[Tinkickef]

Too many layers of software. :cry: I won't update anything until you get it working again. Mine still works fine. What craziness.

 

 

I just got the new steam vr update and it was "challenging'. Went back into settings and found out that the set motionvector setting had been struck out again. Removed the slashes and everything is butter smooth.

[wormeaten]

I just got the new steam vr update and it was "challenging'. Went back into settings and found out that the set motionvector setting had been struck out again. Removed the slashes and everything is butter smooth.

Will be good in the future to create a backup setup file before the upgrade. At least for comparison in Notepad ++.

[Gun Jam]

Okay I got it working (again I have the SO+ right now) Im just doing this ahead of time so I wont have to mess with it when the reverb shows up someday.

 

 

Inateck said to use the windows driver with WMR. I simply uninstalled the inateck driver and went to device manager and said update driver. It said the best driver was already being used.

 

 

 

Plugged the SO+ in and it worked fine. Im assuming the reverb will work fine as well.

 

 

Im using the inateck only for the headset and my monitor has USB output so I plugged those into the inateck as well so I can have USB 3 on my monitor which I use rarely for USB items usually cell phone. The front panel USB is also running on the inateck internal connector.

 

 

Everything seems good to go now

 

 

Thanks

[Secoda]

Those guys. Thanks for the work.

 

I just got the new steam vr update and it was "challenging'. Went back into settings and found out that the set motionvector setting had been struck out again. Removed the slashes and everything is butter smooth.

[Naruto]

Contacted HP Support and the Reverb Pro is only a one year warranty via a case I opened for investigation. Those that got three years, consider yourselves lucky or you may want to double check if your warranty is in fact 3 years.

 

 

 

Hello XXX,

 

I confirmed with our product team, the only warranty offered on this device is the 1 year warranty. According to my leads and all the documentation for the system only a 1 year warranty is available, there is no 3 year option.

 

Please let me know if there is anything else I can do for you.

 

 

Thanks

 

HP Technology Services

HP Workstation Support

HP CE Assist

 

 

T +1 800-334-5144 (Commercial/Workstation Support)

T +1 888-472-2737 (HP Support 1/Priority Services)

T +1 888-654-9298 (Sprout Support)

 

HP Inc.

2351 HP Way

Rio Rancho, NM, 87144

United States

"Our aim is to deliver best in class customer service", Share feedback with my Manager :

[Secoda]

The current HP Datasheet on the Reverb Pro now also says one year. That just makes it more appealing at places with the best return/refund policy IMO. I suspect the commercial customers are getting three.

[Naruto]

The current HP Datasheet on the Reverb Pro now also says one year. That just makes it more appealing at places with the best return/refund policy IMO. I suspect the commercial customers are getting three.

 

Looking inside my HMD, it says 1 year warranty too. Oh well.

 

[sze5003]

The current HP Datasheet on the Reverb Pro now also says one year. That just makes it more appealing at places with the best return/refund policy IMO. I suspect the commercial customers are getting three.

It's very rare that the consumer version would get 3 years and the pro model only one year. In the US very few products have a manufacturer warranty more than one year any way. At least that's how it is with most electronics. In Europe it's bit different.

[Naruto]

It's very rare that the consumer version would get 3 years and the pro model only one year. In the US very few products have a manufacturer warranty more than one year any way. At least that's how it is with most electronics. In Europe it's bit different.

 

HP support did not have the Reverb as part of their consumer division. It took the customer service rep a few minutes to figure out the Reverb is part of their commercial division before he found their phone number to transferred me to their customer support.

[sze5003]

HP support did not have the Reverb as part of their consumer division. It took the customer service rep a few minutes to figure out the Reverb is part of their commercial division before he found their phone number to transferred me to their customer support.

Ah in that sense consumer I'm thinking us but in reality it means businesses. Makes more sense now.